Queries AWS CloudWatch metrics through Grafana CloudWatch datasources — discovering namespaces, metrics, dimensions, and running metric queries. Use when the user asks about AWS resources such as EC2, ECS, RDS, Lambda, or Container Insights, or mentions CloudWatch or AWS.
Analyzes performance issues — CPU, memory, request latency, throughput, and error rates — and identifies bottlenecks by correlating metrics, logs, and traces. Use when the user asks about performance, slow services, bottlenecks, or resource constraints.
Analyzes distributed traces in Tempo with TraceQL — errors, latency, and call paths between services. Use when the user asks about traces, spans, request flows, service dependencies, or latency across services.
Investigates firing alerts and incidents and drives root cause analysis across metrics, logs, and traces, prioritizing the alert's runbook. Use when the user mentions alerts, incidents, firing notifications, outages, or asks to find the root cause of a problem.
Analyzes continuous profiling data — CPU, memory, goroutines, block and mutex contention — from Grafana Pyroscope datasources to find the hottest code paths and leak suspects. Use when the user asks about flame graphs, CPU or memory hot spots, profiling, or which functions consume the most resources.
Renders PromQL, LogQL, and TraceQL results as interactive graphs, gauges, tables, and log or trace panels directly in the chat. Use when composing answers whose queries benefit from a visualization.
Writes efficient PromQL for Prometheus/Mimir metrics and LogQL for Loki logs, including label discovery for unfamiliar clusters. Use when the user asks for queries, graph data, metric analysis, or log searches, or before building panel or alert queries.
★not rated 41▲
+1 yesterdayA57 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: