# Kibana has\_historical\_agent\_data timeout

**URL:** <https://discuss.elastic.co/t/kibana-has-historical-agent-data-timeout/379723>\
**Category:** Kibana\
**Created:** [July 2, 2025, 8:06pm UTC](https://discuss.elastic.co/t/kibana-has-historical-agent-data-timeout/379723 "2025-07-02T20:06:14Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![davjl](https://avatars.discourse-cdn.com/v4/letter/d/bc8723/32.png) [@davjl](https://discuss.elastic.co/u/davjl)\
**Post date:** [July 2, 2025, 8:06pm UTC](https://discuss.elastic.co/t/kibana-has-historical-agent-data-timeout/379723/1 "2025-07-02T20:06:14Z")

</div>

Hello team.

I'm experiencing an issue with applications observability (APM). When I select this section with a filter for the **last 15 minutes** , in some cases, it only displays the following error.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/b/8/b80fa1a448047f9be07c725958631b72907c04a4.png)

I turned on InspectEsQueries, and it showed me the following errors.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/8/18d5d11c6503cec118cefab92f489b8c90f77c30.png)

I tried testing with the Search Profiler, but it always returned a timeout.

I have a cluster on kubernetes with 3 hot nodes and 1 warm node:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/7/f/7fed6586b528ef9687c85a0cc8b8a23b9383730f.png)

For the datastream "traces-apm-default," it has 2 primary shards and 1 replica in the hot phase, with a maximum primary shard size of 25 GB in ILM. It spends 40 minutes in the hot phase before moving to the warm phase with 0 replicas and remains in the warm phase for 3 days. I have 3 or 4 indices per day.

For the moment, I am using Elasticsearch 9.0.0 only for traces, with the default templates.

Can you help me?