Hunters provides a health monitoring indication for data flows defined in the system. This means that each data flow connected to the system using the Ingestion pipeline, is routinely monitored to ensure a continuous flow of data.
.png?sv=2022-11-02&spr=https&st=2025-05-10T07%3A08%3A41Z&se=2025-05-10T07%3A20%3A41Z&sr=c&sp=r&sig=34i62CQOF9jvQPfIP%2B4UioS%2BmgwUuNcAybscOkoSmKA%3D)
When the system identifies an issue with the data transfer, it will notify you about the issue and its origin.
Data flow statuses
Each product and data flow has its own status indication.
Status | Description |
|---|---|
Initializing | The ingestion components are being set up. This can take up to 10 minutes. |
Waiting | Waiting for data to arrive from the data source connected. This could be because data hasn’t been streaming since the connection, or data was already streaming but stopped for some reason. Make sure data is being sent correctly from the source. |
Active | The data source is connected successfully, all resources have been set up and data is flowing. |
Disabled | The user has disabled the data flow. This means no data is being ingested. |
Deprecated | Hunters deprecated the data flow. This means no data is being ingested. |
Error | Something went wrong with the data ingestion and no data is being ingested. See details below. |
Possible errors
When something prevents Hunters from ingesting data from the connected data source, the system can point to the reason and recommend mitigation steps:
| Issue type | About the issue | Next steps |
|---|---|---|
| Configuration issue | Something went wrong with Hunters' ability to reach the data due to a permissions/authentication issue. | Open the data source set up page and click Test Connection to confirm that the details provided in the connection process, such as API key, bucket name, etc., are still valid. |
| Internal issue | Something went wrong. We are aware and on the case. | Reach out to Hunters support to learn more about the issue. |
| Vendor issue | Something went wrong with the connected vendor service. | Reach out to the vendor's support to learn what went wrong. |
Monitor data flow health
You can monitor the health and status of your data flows using 3 channels:
❗Note
The following scenarios will not be alerted on:
Customer integration completely stops shipping data to Hunters. This applies for both integrations that ship data sparsely (once a day, every X hours) and for integrations which ship data frequently (every X (milli)seconds).
Sudden drop in data volume from an integration (i.e. data goes from 1GB/sec to 10MB/sec)
Latency issues. If there's a significant delay in data arriving to the platform it could indicate potential issues with the data source, data pipelines, or other components in the data flow process.
Data quality issues. Data containing missing values, unexpected data types, or data that falls outside specified ranges.
Vendor rate limiting issues Hunters might encounter when trying to ingest data.