Skip to main content
Your production system, explained in Slack. NOFire helps you understand what’s happening, why it’s happening, and what might go wrong next — all in plain language.

Automatic Alert Analysis

Spot early signs of trouble and understand root causes when alerts fire

Interactive Production Queries

Ask questions about deployments, changes, architecture, and system behavior

Automatic Alert Analysis

When alerts fire in your channels, NOFire automatically explains what’s happening and why. Instead of jumping between dashboards, you get a clear explanation of the root cause, what triggered it, and the impact on your system — all in the alert thread. What You Get:
🔴 Checkout API latency spike caused by Redis connection pool exhaustion (14:23-14:31)

Findings:
1. Redis pool maxed at 14:23:17, 500 conns sustained > 30s, checkout-api blocked
2. API p99 latency 850ms → 4.2s, /checkout endpoint impacted 1.2K requests
3. Deploy v2.3.1 at 14:20 increased pool usage 3x without pool size adjustment

NOFire analyzes your system’s behavior across metrics, logs, and traces to explain what changed, why it changed, and what the impact is.

Interactive Investigations

Tag @NOFire AI to ask questions about incidents using data from your connected observability sources. This works both in alert threads and when starting new conversations. Follow-Up Questions: Continue asking in the same thread by @mentioning the bot:
@NOFire AI what about the database connections?
@NOFire AI show me the same timeframe for the API gateway
Always @mention @NOFire AI when asking questions, even in threads. NOFire maintains context from previous messages.

What You Can Ask

  • What changed in the last hour?
  • Show me recent deployments
  • What was deployed before the incident?
  • Who deployed to production today?
  • What’s the architecture of the checkout flow?
  • What services depend on the payment API?
  • Show me the dependency graph
  • How does traffic flow through the system?
  • Why are error rates spiking?
  • What’s causing the latency increase?
  • Explain this alert
  • What’s the root cause of the outage?
  • What metrics are available for this service?
  • Are we missing any instrumentation?
  • What logs exist for the checkout service?
  • Show me trace coverage

When to Use Each Mode

Automatic Alert Analysis - Best for:
  • Understanding what triggered an alert
  • Spotting early signs of problems
  • Getting immediate root cause explanations
Interactive Production Queries - Best for:
  • Understanding recent changes and deployments
  • Exploring system architecture and dependencies
  • Investigating before problems become incidents
  • Checking what observability coverage exists

Access & Privacy

  • NOFire only reads messages where it’s @mentioned or invited to channels
  • Each user must link their Slack account to NOFire (see installation guide)
  • All queries respect your NOFire workspace permissions

Next Steps