Overview
Overview⚓︎
Resource pools let you dedicate compute and storage resources to specific workloads in Hydrolix. They isolate ingest, merge, or query traffic so you can:
- Reserve capacity for priority users or dashboards
- Run heavy ingest pipelines without starving queries
- Scale services independently instead of over-provisioning one pool
Pools define CPU, memory, storage, and replica counts for a group of pods. You can create pools manually, through the UI or API, or let Hydrolix create them automatically when you configure sources.
Supported services⚓︎
The following services support pools:
- Intake:
intake-head - Kafka:
kafka-peer - Kinesis:
kinesis-peer,kinesis-kcl-peer - SIEM:
akamai-siem-peer - Merge:
merge-peer - Query:
query-peer
Send data to ingest pools⚓︎
Every ingest pool gets its own URL path. Configure clients to send data directly to a specific pool endpoint instead of the default ingest endpoint.
| Endpoint | Description |
|---|---|
https://{myhost}.hydrolix.live/ingest/event |
Default intake-head pool |
https://{myhost}.hydrolix.live/pool/{pool_name}/ingest/event |
Custom ingest pool |
For example, a custom pool called custom-pool-stream-head accepts events at:
| Custom Pool Endpoint | |
|---|---|
To route traffic to a pool without changing client endpoints, use dynamic ingest routing with HTTP headers or query parameters instead.