Data Sources
A data source sends data in from outside the cluster, with a token, a table name, and a transform mapping its fields to table columns. CDNs, log forwarders, and cloud services are all data sources. Most post to the streaming ingest API, but some use another method, such as Mux over Kinesis.
Integration failures fall into three cases sharing one symptom, an empty table: the sender never sent, Hydrolix refused the request, or the data didn't match the transform.
An integration's requests fail with an HTTP error⚓︎
Confirm: 401 means the token is invalid, missing, or expired. 404 means the path, or the table and transform combination, is wrong. A connection refused or a timeout means the endpoint is unreachable from the sender.
The code identifies which layer refused the request, so it narrows the fix before you open the integration's own checklist.
Fix: find your integration under Data Sources and work through its troubleshooting section.
An integration sends data but nothing arrives⚓︎
Confirm: The sender reports no error but the table stays empty. Table health reports an Ingest Latency measured from the epoch, meaning the table has never received data. A recent latency doesn't prove the source is working, since other streams into the same table keep the figure low on their own.
The token, the table name, the transform name, and the sending configuration can each be wrong without the sender reporting a failure. Six integrations share one set of checks; the rest carry their own.
Fix: find your integration under Data Sources and work through its troubleshooting section.