Coralogix
Stream audit logs to Coralogix for full-stack observability.
Prerequisites
- A Coralogix account with a Send-Your-Data API key (found under Settings → Send Your Data in the Coralogix dashboard).
- Know which Coralogix region/domain your account is hosted on.
- Network egress allowed to
ingress.<your-domain>on port 443.
Configuration fields
| Field | Required | Description |
|---|---|---|
| Send-Your-Data API Key | Yes | Your Coralogix ingestion API key. |
| Domain | Yes | Your Coralogix region. Available options: |
us1.coralogix.com (US1) | ||
us2.coralogix.com (US2) | ||
eu1.coralogix.com (EU1) | ||
eu2.coralogix.com (EU2) | ||
ap1.coralogix.com (AP1) | ||
ap2.coralogix.com (AP2) | ||
ap3.coralogix.com (AP3) | ||
| Application Name | No | Application name in Coralogix. Defaults to mcp-s. |
| Subsystem Name | No | Subsystem name in Coralogix. Defaults to audit-logs. |
| Anonymous Mode | No | Toggle to send only statistical data (see Anonymous Mode). |
How it works
Logs are sent to https://ingress.<domain>/logs/v1/singles as JSON with severity level 3 (info). The API key is passed as a Bearer token in the Authorization header.
Tips
- Use Application Name and Subsystem Name to organize logs in the Coralogix dashboard.
- Set up Coralogix alerts on audit log actions for real-time notifications.
- The request timeout is 5 seconds — ensure low-latency connectivity to your chosen region.
Troubleshooting
- Verify the API key, and that the correct domain and region are selected.
- Requests time out after 5 seconds. Ensure the region is reachable with low latency.
If no logs appear at all, confirm the provider credentials and URL are correct and that outbound egress is allowed. See Log Settings for shared guidance.
Related
- Log Settings: retention, content options, and Anonymous Mode
- Logs: view and search the logs themselves