Skip to main content
Connecting Honeycomb to NOFire AI lets NOFire query your traces, metrics, and logs during root-cause analysis. NOFire queries Honeycomb in parallel with other connected backends. You do not need separate configuration for each investigation. To connect, authenticate with a Honeycomb API Key scoped to the environments you want NOFire to query.

Prerequisites

  • A Honeycomb account, and permission to create an API key on the team.
  • The API endpoint for your region.
  • The dataset you want NOFire AI to query by default, if you want to set one.

Step 1: Create a Honeycomb API key

Create an API key in Honeycomb

  1. Sign in to Honeycomb and navigate to Team Settings → API Keys.
  2. Click Create API Key.
  3. Set the key type to Configuration and grant the following permissions:
    • Query data: required for NOFire to run trace and metrics queries
    • Run queries: required for structured query execution
  4. Scope the key to the environment you want NOFire to access. Or leave it unscoped for team-wide access.
  5. Copy the key now. You cannot view it again after you leave this page.
Use a dedicated key named nofire so you can rotate or revoke it independently of other integrations.

Step 2: Add Honeycomb connection to NOFire AI

What NOFire queries

During root-cause analysis, NOFire queries Honeycomb for: NOFire evaluates Honeycomb data alongside metrics, logs, and traces from other connected backends. It correlates signals across sources before reaching a conclusion.

Test the connection

  1. Open the Connections dashboard and make sure that the Honeycomb connection status is READY. A connection that stays in an error state did not authenticate.
  2. Ask NOFire a question that needs traces, for example “show me the slowest traces for the checkout service in the last hour”. An answer that cites Honeycomb data confirms the connection works end to end.

Troubleshooting

The key type must be Configuration, and the key must hold the Query data and Run queries permissions.
The key is scoped to a different environment than the dataset you entered.