Skip to main content
Connect your Coralogix account to enable CloudThinker agents to search logs, query metrics and traces, triage incidents, and inspect data pipeline health across your observability stack. Coralogix authenticates with an API key scoped to a region. CloudThinker resolves the right Coralogix endpoint from the region, so the same setup works across all US, EU, and AP data centers.

Supported Regions

Pick the region that matches your Coralogix team login domain.
Data centerRegions
USus1, us2, us3
Europeeu1, eu2
Asia Pacificap1, 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

1

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.
2

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
Copy the key immediately — it may not be shown again.
3

Add Connection in CloudThinker

Navigate to Connections → Coralogix and enter:
  • API Key: the key you just created
  • Region: the region from your login URL (e.g. eu2)
Click Connect. CloudThinker verifies the credentials and shows a Connected status.
Copy the API key immediately after creation. You’ll need to create a new key if it’s lost.

Connection Details

FieldDescriptionExample
CORALOGIX_API_KEYCoralogix API key
CORALOGIX_REGIONRegion from your team login domainus2
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.
Follow least privilege: a read-only key is enough for investigation. Keep mutating permissions off the key CloudThinker uses unless a write workflow specifically requires them.

Agent Capabilities

Once connected, agents have read access to your Coralogix observability data.
CapabilityDescription
DiscoverySummarize account health — active incidents, connector count, disabled parsing rules, and metric no-match handling
Incident TriageList and inspect active incidents and their context
LogsSearch and analyze logs over a time window
MetricsQuery metrics and inspect the metric catalog
TracesInspect distributed traces
Pipeline HealthReview connectors, parsing rules, and presets for misconfiguration
Alerts & DashboardsInspect alert definitions and dashboards

Verify the Connection

@alex run Coralogix discovery and summarize active incidents, connector count, disabled parsing rule count, and whether metric no-match handling is healthy

Example Prompts

@alex triage active Coralogix incidents and #flag anything affecting production
@alex search Coralogix logs for 5xx errors in the api-gateway over the last hour
@alex check Coralogix pipeline health and list any disabled parsing rules
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

The API key is missing, expired, or lacks the required permissions. Create a new Coralogix API key with the needed read permissions and reconnect.
The API key belongs to a different Coralogix region. Check your team login domain and update CORALOGIX_REGION to match.
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.
One or more Coralogix list calls returned an error. Check the API key permissions and region, then rerun discovery.
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

https://mintcdn.com/cloudthinker/aLd-ttc-SCW-aFky/images/icons/datadog.svg?fit=max&auto=format&n=aLd-ttc-SCW-aFky&q=85&s=e8382167f2a1eb1e00971b5f4d703d48

Datadog Connection

Log search, metrics, and monitoring
https://mintcdn.com/cloudthinker/uIxpc0ZqZtveGXWt/images/icons/betterstack.svg?fit=max&auto=format&n=uIxpc0ZqZtveGXWt&q=85&s=61b580a94f2f0b8abd07eb7f494739c2

Better Stack Connection

Uptime, incidents, and log search