You add a connection the same way from onboarding and from Connections. Both show the same list below, except the Preview connections at the end, which only Connections lists.
Kubernetes and discovery
| Connection | What it adds | What you provide |
|---|---|---|
 | Cluster inventory and deploy state | Edge agent token, one helm install command |
| A dependency map built from DNS traffic between services | An Enable DNSTap toggle, plus the CoreDNS configuration edit in DNSTap Configuration |
Cloud providers
| Connection | What it adds | What you provide |
|---|---|---|
 | AWS resource inventory across the account | Region, IAM Role ARN, External ID |
 | Azure resource inventory across the subscription | Subscription ID, Tenant ID, Client ID, Client secret |
 | GCP resource inventory across the project | Project ID, Regions, Service Account JSON |
 | DNS, CDN, WAF, and R2 configuration for the account’s zones | Cloudflare Account ID, API Token, Zone IDs (Optional) |
Observability
| Connection | What it adds | What you provide |
|---|---|---|
 | Metrics, logs, and traces from the connected Grafana stack | URL, Service Account Token, then the datasources NOFire finds |
 | Metrics, logs, traces, and dashboards from Datadog | Site API URL, API Key, Application Key |
 | High-cardinality events for metrics, logs, and traces | API Endpoint, Team API Key, Default Dataset (Optional) |
 | Logs and traces from Coralogix | Region, Team Hostname, API Key, Logs/Traces capability checkboxes |
Metrics
| Connection | What it adds | What you provide |
|---|---|---|
 | Metrics and cluster resource discovery | Cluster Name, URL |
Logs
| Connection | What it adds | What you provide |
|---|---|---|
 | Log aggregation from the connected Loki stack | URL |
 | Log search across the connected Elasticsearch cluster | URL, Token |
 | Log search across the connected OpenSearch domain | URL, Token |
 | AWS logs and metrics | Region, IAM Role ARN, External ID |
| GCP logs | Project ID, Service Account JSON |
Traces
| Connection | What it adds | What you provide |
|---|---|---|
 | Distributed traces from the connected Tempo stack | URL |
Databases
| Connection | What it adds | What you provide |
|---|---|---|
 | Database health and query activity from MongoDB Atlas | Public Key, Private Key |
 | Table state and pg_stat_* activity from a read-only role | A connection string, or Host, Database, User, Password |
Code
Alerts and chat
| Connection | What it adds | What you provide |
|---|---|---|
 | Alert groups and incident history | URL, Service Account Token, Grafana URL |
 | Incidents declared from an investigation or from Slack | Name, API key |
 | Alerts and chat updates in the channels you choose | Workspace authorization through Slack OAuth |
Tickets and docs
| Connection | What it adds | What you provide |
|---|---|---|
 | Issues, projects, and teams from Linear | MCP Server URL |
 | Tickets and docs from Jira and Confluence | MCP Server URL |
Agent tools
| Connection | What it adds | What you provide |
|---|---|---|
 | Any read-only HTTP API, turned into an agent tool | Base URL, an auth type and its credential, Endpoints (JSON) |
 | Read-only kubectl, aws, git, gcloud, helm, terraform, and bash commands, run from chat | No credentials, a toggle per tool |
Preview
Connections marked Preview are coming soon. Connections lists them after the ones you can connect today, with the same Connect button. Select it and no form opens. The dashboard shows the name of the connection with is coming soon, for example New Relic is coming soon, and We noted your interest and will email you when it’s ready. On a deployment that does not send product analytics, the second line reads Tell your NOFire contact if you need it sooner. instead.| Connection | What it adds |
|---|---|
 | Metrics, logs, traces, and alerts, queried with NRQL |
 | Metrics, logs, and traces from VictoriaMetrics, VictoriaLogs, and VictoriaTraces |
 | Metrics, logs, traces, and problems, queried with DQL |
 | Metrics, logs, and traces, queried with PromQL |
| Metrics, logs, and alerts from Azure Monitor, queried with KQL |
 | Errors, events, and traces from the services you run |
 | Logs, metrics, and traces from your Logz.io accounts |
 | Application metrics and health events from AppDynamics |
 | Metrics, traces, and alerts from ServiceNow Cloud Observability |
 | Logs, metrics, and alerts, searched with SPL |
 | Log and metric search across your Sumo Logic account |
 | Traces and metrics from any OpenTelemetry-compatible backend |
 | Incidents and on-call schedules, so an investigation knows who is responding |
 | Alerts and on-call schedules from Opsgenie |
 | Investigation updates in Teams, and investigations started from a channel |
 | Deploys and code changes, linked to the systems they touch |
| Incidents and change requests, surfaced during an investigation |
 | Alerts and on-call from Jira Service Management. Tickets come through Atlassian (MCP) |