Products
Grafana Cloud
Monitor, analyze, and act faster with AI-powered observability.
LGTM+ Stack
Key Capabilities
Observability Solutions
Open Source
Community resources
Dashboard templates
Try out and share prebuilt visualizations
Prometheus exporters
Get your metrics into Prometheus quickly
end-to-end solutions
Opinionated solutions that help you get there easier and faster
monitor infrastructure
Out-of-the-box KPIs, dashboards, and alerts for observability
visualize any data
Instantly connect all your data sources to Grafana
Learn
Community and events
Resources
Help build the future of open source observability software Open positions
Check out the open source projects we support Downloads
Grafana Cloud
Monitor, analyze, and act faster with AI-powered observability.
Observability Solutions
The actually useful free plan
10k series Prometheus metrics
50GB logs, 50GB traces, 50GB profiles
500VUh k6 testing
20+ Enterprise data source plugins
100+ pre-built solutions
3 active AI users
end-to-end solutions
Opinionated solutions that help you get there easier and faster
visualize any data
Instantly connect all your data sources to Grafana
| Capability | Description |
|---|---|
| Custom metrics | Application-specific KPIs as Prometheus metrics |
| Custom spans | Trace data for your application operations |
| Enriched attributes | Context on traces (user ID, order value, feature flags) |
| Richer dashboards | Your custom data in standard Grafana dashboards |
| Level 3 | Level 4 |
|---|---|
| “This request was slow” | “This $500 order from a VIP customer was slow” |
| Generic trace data | Application-enriched traces |
| Infrastructure metrics | Custom application metrics |
Same tools, richer data. You still use Grafana alerting, SLOs, and dashboards. The difference is the data: custom metrics you defined, traces enriched with application context.
So what does Level 4 actually give you? Three things.
First, custom metrics. Application KPIs exposed as Prometheus metrics. Orders per hour, conversion rates, revenue in the last 15 minutes. Numbers that matter to your application, not just to infrastructure operations.
Second, custom spans. You add tracing to the specific operations that matter: checkout flow, payment processing, inventory checks. Now you can see exactly how long your application logic takes.
Third, enriched attributes. You add application context to your traces: user tier, order value, feature flags. This changes everything.
Instead of “this request was slow,” you can say “this 500 dollar order from a VIP customer was slow.” Now stakeholders understand the impact. Now you can prioritize based on revenue, not just latency.