Skip to content

Observability & incidents

Connect a Coralogix team with a read-only Team API key, plus optional just-in-time write elevation.

Coralogix connects with up to two Team API keys: a read key Dave uses on its own, and an optional elevation key Dave uses only for writes you approve. Dave queries logs, traces and metrics and reads alerts, dashboards and SLOs with the official cx CLI, and looks up Coralogix’s documentation through Coralogix’s docs MCP server.

  1. Find your region from your Coralogix team URL — for example myteam.app.eu2.coralogix.com is EU2, myteam.coralogix.com is EU1 and myteam.app.cx498.coralogix.com is US2.

  2. In Coralogix, open Settings → API Keys and create the read key — and, if you want Dave to make changes, the elevation key — as described under Permissions. Coralogix shows each key once.

  3. In Dave, go to Integrations → Add integration → Coralogix.

  4. Pick the Region and paste the read key into Read API key. Keys are stored encrypted and never shown again.

  5. Set a Label — see labels.

  6. Optionally paste the elevation key into Elevation API key — see Just-in-time elevation.

  7. Choose Connect Coralogix. You do not need to stay on the page.

Coralogix keys carry exactly the permissions you give them, and a key cannot ask for fewer on a single call. So Dave uses two keys rather than one powerful key.

Instead of ticking boxes by hand, you can expand Or generate this key with a command under each key field in the Dave connect form. It shows a ready-to-copy script with your region and label filled in. It asks for a Coralogix API key that can create Team API keys (TEAM-CUSTOM-API-KEYS:MANAGE, part of Platform Admin), creates the key with exactly the permissions below, and prints it — paste the value from the output into Dave. The admin key stays in your terminal; Dave never sees it.

To create the keys by hand instead, follow the steps below.

  1. In Settings → API Keys, choose Create a new team key and select Team Key.
  2. Leave Role Presets empty and open Advanced.
  3. Tick only these permissions. Each sits under the group shown; type a few words of it into the search box to find it.
Group Permission
DATAQUERYING ☐ Query frequent-search logs
☐ Query Monitoring and Compliance logs
☐ Query frequent-search spans
☐ Query Monitoring and Compliance spans
☐ Query metrics
☐ Query data from the S3 archive
ALERTS ☐ View Flow alert settings
☐ View log-based alert settings
☐ View Trace Alerts settings
☐ View metric alert configuration
☐ Read Suppression-Rules settings
INCIDENTS ☐ View events in triggered alerts
DASHBOARDS ☐ View Public Custom Dashboards
SLO ☐ View SLO settings
APM ☐ View Service Catalog data
☐ View Service Map
PARSINGRULES ☐ View parsing rules
TCOPOLICIES ☐ View existing log TCO policies
☐ View existing tracing TCO policies
☐ View metrics TCO policies
NOTIFICATIONCENTER ☐ View the existing connectors…
☐ View the existing presets…
☐ View the existing routers…

Do not tick a group’s All box — most groups mix read and write permissions. Anything starting with Manage, Create, Define, Snooze or Acknowledge is a write.

Tick read permissions only. Setup checks one write permission (deleting alerts) and fails if the read key has it, but it cannot check the others — a read key with any other write permission would let Dave make that change without asking for approval.

Optional. Create a second team key in the same team the same way: tick everything from the read key, then add only the writes you want Dave to be able to make.

Dave can change (group) Also tick
Alerts (ALERTS) ☐ Manage Flow alert settings
☐ Manage log-based alert settings
☐ Manage Trace Alerts settings
☐ Define and modify settings for metric alerts
☐ Snooze or unsnooze an Alert
Suppression rules (ALERTS) ☐ Manage Suppression-Rules settings
Dashboards (DASHBOARDS) ☐ Manage Public Custom Dashboard
SLOs (SLO) ☐ Manage SLO settings
Service catalog (APM) ☐ Manage Service Catalog services
Parsing rules (PARSINGRULES) ☐ Create, modify, or remove parsing rules
TCO policies (TCOPOLICIES) ☐ View and modify existing log TCO policies…
☐ View and modify existing tracing TCO policies…
☐ Manage metrics TCO policies
Notification routing (NOTIFICATIONCENTER) ☐ Create and edit connectors…
☐ Create and edit presets…
☐ Create and edit routers…

Never add API key, user, role or group permissions. Use a different key from the read key, in the same Coralogix team.

Labels follow Coralogix’s permissions list, which also gives each one’s permission code.

Revoking the read key in Coralogix cuts Dave off; revoking the elevation key disables elevation.

Disconnect in Dave stops Dave using both keys immediately, but does not revoke them in Coralogix. The same goes for cancelling an unfinished setup.

To replace either key, or to add or remove elevation, disconnect and connect again.

Dave stores the elevation key encrypted and the agent never sees it: each write you approve — creating or muting an alert, editing a dashboard, changing a parsing rule — is sent through Dave as a one-shot grant for exactly the API calls shown. Leave the field blank to keep the team read-only.

  • GovCloud and custom or private-link endpoints are not supported.
  • Coralogix rejects the API key — check the region and that the key is an active Team API key, then connect again.
  • The API key can change your Coralogix account — the read key has write permissions. Create one with only read permissions.
  • Coralogix rejects the elevation key — check it is active, belongs to the same team as the read key, and was not pasted into the wrong field.