> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useorgx.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Observability

> Correlate OrgX API requests, retries, and event consumption.

Capture these values for every API call:

* HTTP method and path;
* response status;
* `X-Request-ID` or `X-Correlation-ID`;
* your `Idempotency-Key` for a mutation;
* returned resource and event IDs;
* latency measured by your client.

Do not log authorization headers, receipt bodies containing sensitive data, or
provider credentials.

## Mutation tracing

Use the same idempotency key for retries of one logical operation. Record the
returned `duplicate` field so your telemetry distinguishes a new write from a
safe replay.

## Event consumers

Record the last successfully processed cursor and each stable event ID. Advance
the cursor only after downstream processing succeeds, and tolerate repeated
events after a reconnect.

Include the request ID, endpoint, timestamp, and resource ID when contacting
OrgX Support.