Ingest troubleshooting

Start by locating the stage that failed. A request rejected immediately is different from an accepted request that has not reached the warehouse.

Request is unauthorized#

Check that the secret, JWT, API key, or client certificate belongs to the intended project and client. Confirm the client is enabled and the token is sent in the supported header or TLS context.

Request is forbidden#

Authentication may have succeeded while authorization failed. Check:

• the model is in the client's allowed set;
• the Analytics/API key capability is correct;
• the source IP is inside an allowed CIDR;
• identity-binding values agree;
• the certificate is signed by the selected Client CA.

Payload is invalid#

Confirm that schema is the model key and data is an array of objects. Compare every required field and type with the model or generated OpenAPI document.

For NDJSON, inspect the reported line and ensure the request does not mix schema keys.

WebSocket does not stay connected#

Implement ping/pong handling, use text messages, respect the maximum message size, and reconnect with backoff. A 429 upgrade response indicates a connection limit.

Syslog does not appear#

1. Verify UDP/TCP/TLS mode and the endpoint shown in the client.
2. Confirm firewall and source-network behavior.
3. For TLS, inspect the server and client certificate chain.
4. Start discovery and send one representative message.
5. Compare observed hostname, expected hostname, source IP, and routing rules.
6. Remember that UDP has no acknowledgement.

Accepted but not stored#

Inspect the destination detail and statistics. Check warehouse reachability, credential validity, schema provisioning permissions, and adapter-specific database/index settings.

A new resource is briefly not found#

Runtime configuration uses a periodically refreshed local snapshot. Retry a newly created client or Analytics API after a short delay before escalating.