Supported Regions
Pick the region that matches your Coralogix team login domain.| Data center | Regions |
|---|---|
| US | us1, us2, us3 |
| Europe | eu1, eu2 |
| Asia Pacific | ap1, ap2, ap3 |
Prerequisites
- A Coralogix account with access to the team you want to investigate.
- An API key with the read permissions for the observability data CloudThinker should reach.
- The region of your Coralogix team.
Use an API key with the least permissions needed for read-only investigation. CloudThinker’s setup verification only reads data — it never mutates Coralogix resources.
Setup
Open Coralogix
Sign in to your Coralogix account. Your login URL follows the format
https://<team>.app.<region>.coralogix.com — the <region> segment is your region.Create an API Key
Go to Settings → Users and Teams → API Keys and click Add key:
- Name:
cloudthinker - Type: pick Team Key — it’s shared and stays valid even if the creating user’s access expires, unlike a Personal Key, which is tied to an individual and meant for testing
- Permissions: grant the read permissions for the data CloudThinker should access
Connection Details
| Field | Description | Example |
|---|---|---|
| CORALOGIX_API_KEY | Coralogix API key | — |
| CORALOGIX_REGION | Region from your team login domain | us2 |
CloudThinker derives the Coralogix API endpoint from the region, so no manual URL configuration is required.
Required Permissions
Grant the API key the read permissions for the observability data CloudThinker investigates — logs, metrics, traces, incidents, alerts, connectors, parsing rules, presets, and dashboards.Agent Capabilities
Once connected, agents have read access to your Coralogix observability data.| Capability | Description |
|---|---|
| Discovery | Summarize account health — active incidents, connector count, disabled parsing rules, and metric no-match handling |
| Incident Triage | List and inspect active incidents and their context |
| Logs | Search and analyze logs over a time window |
| Metrics | Query metrics and inspect the metric catalog |
| Traces | Inspect distributed traces |
| Pipeline Health | Review connectors, parsing rules, and presets for misconfiguration |
| Alerts & Dashboards | Inspect alert definitions and dashboards |
Verify the Connection
Example Prompts
For large or noisy catalogs, scope requests with short time windows and a known metric or log query so the agent returns focused results.
Troubleshooting
401 or 403 Unauthorized
401 or 403 Unauthorized
404 Not Found
404 Not Found
The API key belongs to a different Coralogix region. Check your team login domain and update CORALOGIX_REGION to match.
No metrics found
No metrics found
The metric catalog has no matching metric, or the account has no metric data. Treat it as an empty result, then try a known metric name or continue with incidents and logs.
Discovery shows degraded status
Discovery shows degraded status
One or more Coralogix list calls returned an error. Check the API key permissions and region, then rerun discovery.
Large or noisy output
Large or noisy output
Unbounded catalog or query usage returns too much data. Scope requests with short time windows and specific queries so results stay focused.
Security Best Practices
- Least-privilege key - Grant only the read permissions CloudThinker needs
- Read-only investigation - Keep mutating permissions off the key unless a write workflow requires them
- Correct region - Match the API key’s region to avoid cross-region failures
- Key rotation - Rotate the API key regularly
- Revoke when unused - Remove the API key in Coralogix if you stop using the connection
Related
Datadog Connection
Log search, metrics, and monitoring
Better Stack Connection
Uptime, incidents, and log search