Troubleshooting

Open in ChatGPTOpen in Claude

Resolve common issues when setting up Coralogix, sending your first data, and verifying your integration is working correctly.

Note

Just confirming that your data is flowing? See Verify your data. This page is for when something isn't working.

Data not appearing

After setting up an integration, data typically appears in Explore within a few minutes. If you do not see results:

1. Verify your Send-Your-Data API key is correct and active.
2. Confirm the endpoint matches your Coralogix domain.
3. Check that your integration source is generating data.
4. Clear any application, subsystem, or severity filters in Explore and Livetail that might be hiding the data rather than blocking it.
5. Confirm you have not hit a daily quota or a block rule (see Blocked by a rule or quota below).
6. Use Livetail to verify data is arriving in real time.
7. See Troubleshoot data collection for additional steps.

API key errors

If you receive authentication errors when sending data:

• Confirm you are using a Send-Your-Data API key, not an Alerts or Management key.
• Check that the key has not been revoked or rotated. Generate a new key from Data Flow, then API Keys.
• Verify the key matches the team you intend to send data to.

Endpoint mismatch

If data is sent but does not appear in your account:

• Verify the endpoint region matches the domain you selected during signup.
• Check the endpoints reference for the correct URL for your region.

Region	Domain
US1	coralogix.us
US2	cx498.coralogix.com
US3	us3.coralogix.com
EU1	coralogix.com
EU2	eu2.coralogix.com
AP1	coralogix.in
AP2	coralogixsg.com
AP3	cx498-ap3.coralogix.com

Integration not collecting data

If your integration is configured but no data flows:

• For Kubernetes: verify the Helm chart deployed successfully with helm list -A and check pod logs with kubectl logs.
• For AWS: confirm the IAM role or credentials have the required permissions.
• For OpenTelemetry Collector: check the collector logs for exporter errors and verify the endpoint and private_key in your config.

Data is sent but timestamped wrong

Coralogix rejects events timestamped more than 24 hours in the past or future. If your shipper reports success but nothing appears:

• Confirm the host clock is correct and its timezone is set.
• If the timestamp is parsed from the log body, verify the parse produces a valid, recent time.
• Normalize timestamps at the shipper (an OpenTelemetry Transform processor or a parsing rule) when the source format is nonstandard.

Blocked by a rule or quota

If the integration is healthy but data still doesn't land:

• Check Data Flow, then Rules and the TCO Optimizer for a block rule that drops the data.
• Look for a daily quota warning at the top of the app. Once the quota is reached, new data is dropped until it resets.

Test network connectivity

If nothing reaches Coralogix at all, confirm the host can resolve and reach your region's ingress endpoint (find the exact host on the endpoints reference):

nslookup <your-ingress-endpoint>
nc -vz <your-ingress-endpoint> 443

If these fail, allowlist the Coralogix endpoints and IP ranges for your region in your firewall.

Metrics missing or noisy

• Metrics can take slightly longer to appear than logs. Wait a few minutes before digging in.
• If a metric is present but a query is slow or truncated, you may be hitting high cardinality. Use the Metrics usage analyzer to find the labels driving cardinality and reduce them.

Related resources

Troubleshoot data collectionManage API keysIntegrations catalog

Next steps

Once data is flowing, keep the Quick reference handy, or revisit the Features tour to see what to set up next.