# Dec 21st, 2025: \[EN\] Analyzing traces in Discover faster and clearer

**URL:** <https://discuss.elastic.co/t/dec-21st-2025-en-analyzing-traces-in-discover-faster-and-clearer/383615>\
**Category:** Advent Calendar\
**Created:** [December 21, 2025, 8:00am UTC](https://discuss.elastic.co/t/dec-21st-2025-en-analyzing-traces-in-discover-faster-and-clearer/383615 "2025-12-21T08:00:30Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![irene\_blanco](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/irene_blanco/32/144433_2.png) [@irene\_blanco](https://discuss.elastic.co/u/irene_blanco)\
**Post date:** [December 21, 2025, 8:00am UTC](https://discuss.elastic.co/t/dec-21st-2025-en-analyzing-traces-in-discover-faster-and-clearer/383615/1 "2025-12-21T08:00:30Z")

</div>

Este artículo está disponible [en Español](https://discuss.elastic.co/t/383616).

 ![Day 21](https://us1.discourse-cdn.com/elastic/original/3X/f/b/fbec9f7c8af84fe9e671c38a63c2c27aff0aaae0.png)

# Analyzing traces in Discover faster and clearer

Having trouble with slow endpoints and not sure where to start?

Now in Discover, when the Solution View of the space is set to Observability, you can see trace timelines, associated errors, related logs, and metric visualizations for similar spans, all in one place.

This gives you full context of the trace without switching interfaces, making problem investigation much faster.

# Investigating latency patterns

### Start by looking for slow POST transactions

Filter by duration to see only the slowest requests:

```auto
FROM traces-*.otel-* 
| WHERE service.name == "cart" AND http.request.method == "POST"
AND duration > 2000000000

```

### Examine individual spans

Open the slow spans to check attributes such as `status.code` or `span.name` to see which operations contribute most to latency.

![Examine individual spans](https://us1.discourse-cdn.com/elastic/original/3X/9/8/98be064d23696093c071cc6fe33a81490a5e0d8b.gif)

### Narrow down the search

When something catches your attention, adjust your filters or query to focus on specific spans, services, or time ranges:

![Narrow down the search](https://us1.discourse-cdn.com/elastic/original/3X/d/7/d7acb763b80d41ab8417a1c6c5227d44de098ff3.gif)

### Start analyzing

Now that the new results are in, here’s what you can explore right within the flyout:

- Analyze latency patterns
- Check the timeline preview
- Explore the complete timeline
- Review associated errors
- Dive into related logs

 ![Start analyzing](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e86bd5338cccc943d133f2cbab538502d45a1ece.jpeg)

Everything you need for the analysis is accessible without leaving the flyout, keeping your context intact.

#### Analyze latency patterns

Use the latency distribution curve to understand whether this span is faster or slower compared to other similar spans. You can also click to open all similar spans in Discover for a deeper analysis.

 ![Latency chart for similar spans](https://us1.discourse-cdn.com/elastic/original/3X/b/5/b50bb72aef876e23c3092976ad73af3b8c0b7831.png)

#### Check the timeline preview

The timeline overview helps you quickly spot any errors in the trace. This gives an immediate sense of issues without opening the full trace.

 ![Timeline preview](https://us1.discourse-cdn.com/elastic/original/3X/d/e/de7deb62e1b1e11b8b88ccb2bfbc9a20b33c9d04.png)

#### Explore the complete timeline

Opening the timeline provides full visibility into the trace, allowing you to examine all related spans and errors. This makes it easier to identify which parts of the operation are contributing to performance issues.

![Complete timeline](https://us1.discourse-cdn.com/elastic/original/3X/f/1/f10602b1d1a215ddcb3aca392112520da411ed2f.gif)

#### Review associated errors

Look at the related errors to pinpoint specific failures affecting the trace. You can also click to open these errors in Discover, which helps you understand what went wrong and highlights problematic areas.

 ![Related errors](https://us1.discourse-cdn.com/elastic/original/3X/4/c/4c2060c238ddc140815a5c86ce4a5bc425a77da4.png)

#### Dive into related logs

Related logs give additional context around the trace. You can open these logs in Discover as well, making it easier to connect spans, errors, and logs to understand the observed behavior.

 ![Related logs](https://us1.discourse-cdn.com/elastic/original/3X/1/c/1ca4eb2e9465d62a1f7576338e589266d399d919.png)

With these improvements, investigating traces and performance issues in Discover has never been faster or clearer. You can get full context on your spans, errors, logs, and latency patterns all in one place.

We’re continuing to enhance this experience by adding more contextual information for even better analysis, check out our blog post ["A new era for Elastic Discover: ES|QL, context & multi-tabs"](https://www.elastic.co/search-labs/blog/elastic-discover-context-evolution) to see all the latest Discover improvements and stay tuned for future updates!