Tracing and the monitor

Find the same UAT request the dashboard just made.

Every JSON response includes meta.request_id. Send that value with any support request. Client systems may also send X-ARISE-Trace-CorrelationId (1–128 characters, [A-Za-z0-9._:-]); the API stores it as client_correlation_id when valid and ignores it when not.

Monitor

The read-only monitor is a separate IAP-gated surface at https://monitor.modulate-api.es.flute.com. It is not this docs site and not the data API.

Use it to confirm:

• The request reached the API
• Status, duration, endpoint, and origin
• Both correlation identifiers
• Rate-limit headers recorded on the event
• Whether telemetry is fresh or delayed

The monitor cannot mint tokens, edit limits, switch organizations, or open the main application — it is display-only for approved principals. Access is IAP, not the docs password and not the API bearer token.

If telemetry is delayed, treat missing counts as unknown, not zero.