Aiden acts as an intelligent layer on top of your Grafana observability stack, transforming it from a data visualization tool into a proactive operations platform. Instead of manually writing PromQL queries or navigating dashboards, you can ask questions in plain English like "Show me CPU usage trends for the payment service over the last 24 hours" or "What error logs correlate with the latency spike at 3 PM yesterday?" Aiden automatically queries your Grafana datasources (Prometheus, Loki), analyzes the data, and provides actionable insights—reducing investigation time from hours to minutes.

Aiden currently integrates with Prometheus (for metrics) and Loki (for logs), the two most widely used datasources in Grafana deployments. This means Aiden can help you correlate metrics and logs across your entire observability stack, perform root cause analysis, analyze firing alerts, and investigate performance issues—all through natural language queries. Additional datasource support is planned for future updates.

No. Aiden is designed to work seamlessly with your existing Grafana infrastructure—no rip-and-replace required. You simply connect Aiden to your Grafana instance using an API token, and it immediately starts enhancing your observability workflows. Your dashboards, alerts, and existing configurations remain unchanged. Aiden complements Grafana by adding AI-powered querying, automated root cause analysis, and intelligent alert triage on top of your current setup.

Aiden accelerates incident resolution in three key ways:

1. Intelligent Alert Triage: Automatically enriches alerts with relevant context, potential root causes, and recommended next steps—eliminating manual investigation overhead.
2. Natural Language Investigation: Query logs and metrics across services without writing complex PromQL or LogQL queries, enabling faster correlation and diagnosis.
3. Automated Root Cause Analysis: Aiden proactively analyzes metrics, logs, and firing alerts to identify the source of issues, often before they escalate—reducing MTTR from hours to minutes.

Organizations using Aiden report MTTR reductions of up to 80% compared to manual Grafana workflows.

Aiden requires a Grafana API token with Editor permissions to query datasources and access the Explore feature. We recommend creating a dedicated service account specifically for Aiden with the minimum required permissions. For security best practices:

• Use a service account token rather than a personal access token
• Regularly rotate API keys (every 60-90 days)
• Enable audit logging in Grafana to monitor Aiden's activities
• Restrict token scope to only the datasources Aiden needs to access

Detailed setup instructions and security guidelines are available in our integration documentation.