Skip to main content
Connect a Coralogix team to let CloudThinker agents triage open incidents, search logs and traces, query metrics, inspect alerts and dashboards, and check your data pipeline for disabled parsing rules or misconfigured connectors. The connection uses Coralogix’s hosted MCP server, signed in with one API key for one region. You pick the region and CloudThinker routes to the matching Coralogix endpoint, so there’s no URL to type.

​
Prerequisites

  • A Coralogix team with the data you want agents to read.
  • Permission to create API keys for that team.
  • Your team’s region, which you read from your login address (see the region table).

​
Setup

1

Find your region

Sign in to Coralogix and match the address bar to the region table. Some regions don’t put their name in the address: acme.coralogix.com is EU1 and acme.app.cx498.coralogix.com is US2.
2

Create an API key

Go to Settings → API Keys and create a new key:
  • Name: cloudthinker
  • Type: Team key. A personal key is tied to one user and stops working when their access ends.
  • Permissions: read access to the data agents should reach (see Required permissions)
Copy the key right away. You’ll need a new key if you lose it.
3

Add the connection in CloudThinker

Open More → Workspace settings → Connections, stay on the Builtin Connections tab, and select Coralogix. Fill in:
  • CORALOGIX_API_KEY: the key you created
  • CORALOGIX_REGION: pick your region from the list, for example EU2 (eu2.coralogix.com). The default is US2 (us2.coralogix.com), so change it if your team lives elsewhere.
Click Connect.Success state: Coralogix shows Connected. Run the verify prompt below to confirm the key and region match.
A key only works in the region it was created in. A wrong region shows up as 404 Not Found, which looks like missing data. Check the login address before you debug anything else.

​
Connection details

Find your login address in the left column, then pick the option on the right: To reach another team or region, add it as a separate connection with its own key.

​
Required permissions

Grant the key read access to the data agents should investigate: Leave write permissions off the key unless you want agents to change Coralogix resources, such as enabling a parsing rule. A read-only key covers every investigation on this page.

​
Agent capabilities

Agents never change anything during discovery, triage, or health checks. A change only happens when you ask for it in the conversation and name the resource and the change, and it goes through Approvals. Agents cap samples at 10 items by default so large catalogs don’t flood the answer.

​
Verify the connection

Expect counts for incidents, connectors, parsing rules, and presets, plus a short sample of each. “No metrics matched” in the metric check is normal: discovery probes with a name that doesn’t exist. If the summary says degraded, the agent lists which checks failed: incidents, connectors, parsing rules, presets, or metrics. A failed check usually means the key lacks read permission for that data. If every check fails, check the key and the region first.

​
Example prompts

Give a service name and a short time window. Narrow queries come back faster and stay readable.

​
Troubleshooting

The key is missing, expired, or revoked. Create a new team key, edit the connection, and paste it into CORALOGIX_API_KEY.
The key belongs to a different region. Check your login address and change CORALOGIX_REGION to match.
The key lacks read permission for that data. Add it in Coralogix, then rerun the request. No need to reconnect if the key itself didn’t change.
No metric matches that name, or the team sends no metrics. The agent treats it as an empty result. Try a metric name you know exists, or continue with incidents and logs.
Coralogix is rate limiting or in maintenance. Wait a minute, narrow the request, and ask again.

​
Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Team key, read access first: add write permissions only for changes you want agents to be able to propose.
  • One key per connection: create a key used only by CloudThinker so you can revoke it without breaking other tools.

Root cause analysis

See how Resolve uses logs and traces to find what broke.

Approvals

Control which Coralogix changes wait for a person.