---
title: "Logs | Grafana Cloud documentation"
description: "Explore logs for a service using the embedded Logs Drilldown view."
---

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

# Logs

The Logs tab embeds the Grafana Logs Drilldown app, pre-filtered to the selected service. It provides full log exploration capabilities without leaving the service context.

## Pre-applied filters

The Logs tab automatically filters by:

- `service_namespace`: the service’s namespace
- `service_name`: the service’s name

These filters are derived from the service’s OTel resource attributes.

## Explore logs

The Logs Drilldown provides:

- **Log levels**: filter by severity (error, warning, info, debug).
- **Fields**: filter by structured log fields.
- **Line filter**: search for specific strings or patterns in log content.
- **Patterns**: automatically detected log patterns for grouping similar entries.

### Sub-tabs

Expand table

| Tab      | Description                                                 |
|----------|-------------------------------------------------------------|
| Logs     | The raw log entries matching your filters.                  |
| Labels   | Available label values for the filtered logs.               |
| Fields   | Structured fields extracted from log entries.               |
| Patterns | Automatically detected patterns grouping similar log lines. |

## Log volume

The **Log volume** panel shows the rate of log entries over time, helping identify spikes in logging activity that may correlate with issues.

## Open in Logs Drilldown

Click **Logs Drilldown** in the top right to open the full Logs Drilldown app with the current filters preserved. For complete Logs Drilldown documentation, refer to [Explore Logs](/docs/grafana-cloud/visualizations/simplified-exploration/logs/).

## Next steps

- Correlate log spikes with [Traces](/docs/grafana-cloud/observe-and-act/monitor-applications/application-observability-kg/service-detail/traces/) to find the requests that generated errors.
- Check [Service overview](/docs/grafana-cloud/observe-and-act/monitor-applications/application-observability-kg/service-detail/service-overview/) to see if log volume correlates with latency or error ratio changes.