Works in:
- NOFire MCP Server and your IDE integration
- NOFire Dashboard (chat interface)
- NOFire Slack App (@mention the bot)
Time Windows
NOFire always operates in a time window. If you don’t specify one, it defaults to the last 1 hour. How to specify time:- Relative: “in the last 30 minutes”, “last 2 hours”, “since yesterday”
- Absolute: “between 2pm and 3pm today”, “from 9:00 AM to 11:00 AM”
- Specific moment: “around 3:24 pm ET on April 10”
Prevent Issues
Catch problems before they become incidents.Deployment Safety
Alert Coverage
Instrumentation Gaps
Configuration Validation
Quick Insights
Fast access to metrics, logs, and traces for immediate understanding.Performance & Resources
Logs & Errors
Service Health
Root Cause Analysis
Understand why things broke and what triggered issues.Service Failures
Change Impact
Configuration Issues
Optimize Costs
Reduce observability spend without losing visibility.Cost Analysis
Reduce Waste
Retention & Sampling
Analysis Tools
Spans & Traces
For performance bottlenecks and distributed system debugging.Events & Changes
For change detection and deployments.Tips for Better Prompts
-
Be specific about time ranges
- “in the last 30 minutes”
- “between 2pm and 3pm today”
-
Name services naturally
- “checkout-api” or “checkout api”
- “recommendation service”
-
Ask follow-ups in the same thread
- NOFire maintains context from previous messages
-
Include symptoms when investigating
- “why are error rates spiking in payment-service?”
- “what’s causing slow responses in the API?”
-
Use specific trace/error IDs when available
- “explain trace e97f261d4fccfdbfb19be22e5174ab5e”
- “show me logs for pod frontend-xyz123”