---
title: "What problems does Level 2 solve? | Grafana Labs"
description: "Understanding service visibility"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## The key question

> **“Which service is the problem?”**

At Level 2, you shift from looking at servers to looking at services. Same underlying infrastructure, but a completely different lens.

[Level 2 lens shift showing the transition from infrastructure view (servers with CPU/memory) to service view (service map with dependencies)](/docs/learning-hub/intro-to-grafana-cloud/images/level-2-lens-shift.svg "Level 2 lens shift showing the transition from infrastructure view (servers with CPU/memory) to service view (service map with dependencies)")

## Problems you can solve at Level 2

| Problem                                   | How Level 2 helps                                        |
|-------------------------------------------|----------------------------------------------------------|
| “Users report slowness, where do I look?” | Service-level RED metrics show which service is degraded |
| “What services do we even have?”          | Service Inventory auto-discovers from traces             |
| “How do our services connect?”            | Service graph visualizes dependencies                    |
| “What’s normal for this service?”         | Baseline metrics establish healthy behavior              |

## What you get

- **RED metrics**: Rate, Errors, Duration for every service
- **Service Inventory**: Auto-discovered list of all services
- **Service Graph**: Visual map of service dependencies
- **Consistent triage**: Same metrics, same view, every service

> **The mental shift:** Stop asking “which server?” Start asking “which service?” This lens is much more useful when users are complaining.