Skip to main content
NOFire builds system context from what you connect: infrastructure, telemetry, code, and chat. Before a deploy, that context shows what the change touches. When something breaks, the same connections carry the evidence NOFire reasons over.
You add a connection the same way from onboarding and from the Connections tab. Both show the same list below, except the Preview connections at the end, which only the Connections tab lists.

Kubernetes and discovery

Cloud providers

Observability

Metrics

Logs

Traces

Databases

Code

Alerts and chat

Tickets and docs

Agent tools

Preview

Connections marked Preview are coming soon. The Connections tab lists them after the ones you can connect today, with the same Connect button. Select it and no form opens: the dashboard shows the connection’s name 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.

What NOFire asks you for

Most connections ask for the same three things: a name you choose, a read-only credential, and an identifier such as an account ID, project ID, or endpoint URL. Slack and GitHub authenticate through the vendor’s app-install flow instead of a typed credential.
If you connect from behind a firewall, route the connection through Edge instead of exposing the data source to the internet.