Collector troubleshooting

No observation received

Check collector statistics and credential alignment.

• Confirm the application executed the wrapped path.
• Validate all three keys belong to the intended workspace environment and integration.
• Check the ingest endpoint and stats() counters.
• Call flush() during a controlled local test.

Rejected batches

Inspect validation and authentication failures.

Do not retry malformed or unauthorized batches unchanged. Correct an invalid envelope, expired or rotated token, mismatched Source key, or unknown Integration key first.

Queue health

Review sent, queued, failed, and dropped batch counts.

Use collector statistics to compare queued, sent, failed, and dropped work. Persistent growth indicates unreachable ingestion or insufficient flushing; dropped work indicates the bounded queue reached capacity.