# Problem with ElasticSearch extension

**URL:** <https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479>\
**Category:** Extensions\
**Tags:** elasticsearch, extensions\
**Created:** [November 7, 2023, 10:28am UTC](https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479 "2023-11-07T10:28:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![radek\_jasinski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radek_jasinski/32/10432_2.png) [@radek\_jasinski](https://community.dynatrace.com/u/radek_jasinski)\
**Post date:** [November 7, 2023, 10:28am UTC](https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479/1 "2023-11-07T10:28:37Z")

</div>

Hi,  
I have an ElasticSearch extension installed on one of my environments. Despite the correct configuration, only the CPU and Memory metrics appear. I do not have any log entries indicating errors.

 ![Zrzut ekranu 2023-11-7 o 10.14.53.png](https://global.discourse-cdn.com/dynatrace/original/2X/1/176322c18ccc484af4c1f4031913030b4edbe08c.jpeg)  
&nbsp;&nbsp;  
 ![Zrzut ekranu 2023-11-7 o 10.15.50.png](https://global.discourse-cdn.com/dynatrace/original/3X/e/d/edbcb976281216c2ee9cc789d3c6dadb4abe75c0.jpeg)

Has anyone encountered this problem?

Radek

---

<div class="post-metadata">

**Author:** ![LoucasK](https://avatars.discourse-cdn.com/v4/letter/l/46a35a/32.png) [@LoucasK](https://community.dynatrace.com/u/LoucasK)\
**Post date:** [November 7, 2023, 8:19pm UTC](https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479/2 "2023-11-07T20:19:38Z")

</div>

Hi,

I believe it would be helpful to first verify that the filters and feature sets are configured to allow data to be ingested, and then to look at the logs for the extension. For an ActiveGate deployment this can be found by running “Run ActiveGate diagnostics”, and by running “Run OneAgent diagnostics” for a OneAgent deployment. The extension logs could help to show any issues with the extension execution, and the “diag\_executor” logs will show how many metrics should be ingested every minute.  
Please let us know if this is helpful, and if there is any further support we can provide for this issue.  
Tyler

---

<div class="post-metadata">

**Author:** ![jegron](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/jegron/32/12797_2.png) [@jegron](https://community.dynatrace.com/u/jegron)\
**Post date:** [November 8, 2023, 7:01pm UTC](https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479/3 "2023-11-08T19:01:45Z")

</div>

Hi&nbsp;[@radek\_jasinski](https://community.dynatrace.com/user/16832)&nbsp;! It seems that you are looking at the “technical” extension metrics view. Here, the CPU and RAM metrics are related to the extension’s system usage on the host or ActiveGate.

Do you have metrics or entity in the preset dashboard ?

 ![jegron_0-1699469805856.png](https://global.discourse-cdn.com/dynatrace/original/3X/2/1/217c9d9638a586beae6ec1915f2820e8a33cc6f6.png)

---

<div class="post-metadata">

**Author:** ![radek\_jasinski](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/radek_jasinski/32/10432_2.png) [@radek\_jasinski](https://community.dynatrace.com/u/radek_jasinski)\
**Post date:** [November 9, 2023, 9:45am UTC](https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479/4 "2023-11-09T09:45:15Z")

</div>

Hi&nbsp;[@jegron](https://community.dynatrace.com/user/47129)

I don’t have any metrics available on that cockpit you showed. I also verified the metrics that are available from this plugin and I don’t have a value anywhere.

Radek

---

<div class="post-metadata">

**Author:** ![Mike\_L](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/mike_l/32/11717_2.png) [@Mike\_L](https://community.dynatrace.com/u/Mike_L)\
**Post date:** [November 9, 2023, 9:50am UTC](https://community.dynatrace.com/t/problem-with-elasticsearch-extension/42479/5 "2023-11-09T09:50:58Z")

</div>

Please go ahead and open a support ticket.
