# Micrometer registry elastic : no handler found for uri and method POST

**URL:** <https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084>\
**Category:** Elasticsearch\
**Created:** [October 1, 2024, 10:05am UTC](https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084 "2024-10-01T10:05:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hugo\_RIVIERE](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hugo_riviere/32/138000_2.png) [@Hugo\_RIVIERE](https://discuss.elastic.co/u/Hugo_RIVIERE)\
**Post date:** [October 1, 2024, 10:05am UTC](https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084/1 "2024-10-01T10:05:47Z")

</div>

I have a simple Spring Boot application using micrometer-registry-elastic and I can't seem to export metrics any longer.  
I have this error when I run the app :

```auto
ERROR i.m.elastic.ElasticMeterRegistry : failed to send metrics to elastic: {"error":"no handler found for uri [/micrometer-metrics-2024-10/doc/_bulk] and method [POST]"}

```

Tell me if there's anything I can provide to help

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [October 1, 2024, 11:06am UTC](https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084/2 "2024-10-01T11:06:43Z")

</div>

Hi @Hugo_RIVIERE,

Welcome! By `micrometer-registry-elastic` do you mean you're using teh [Micrometer Elastic export implementation](https://docs.micrometer.io/micrometer/reference/implementations/elastic.html) to send your metrics to Elasticsearch?

Micrometer is not a tool that is developed or maintained by Elastic, but that looks like it might be either that your Elasticsearch cluster is unavailable and Micrometer can't send, or a version incompatibility. Can you confirm which versions of Micrometer and Elasticsearch that you're using? Can you also check the health of your cluster?

Hope that helps!

---

<div class="post-metadata">

**Author:** ![Hugo\_RIVIERE](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hugo_riviere/32/138000_2.png) [@Hugo\_RIVIERE](https://discuss.elastic.co/u/Hugo_RIVIERE)\
**Post date:** [October 1, 2024, 11:45am UTC](https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084/3 "2024-10-01T11:45:46Z")

</div>

Thank for your response, I'm using micrometer-registry-elastic:1.1.4 and Elasticsearch online so I suppose it's the latest version.  
And my cluster is fine, I can create indexes and check its previous documents all directly via the interface.  
And the index doesn't exist yet but it's supposed to be created if I understood correctly.

---

<div class="post-metadata">

**Author:** ![Hugo\_RIVIERE](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hugo_riviere/32/138000_2.png) [@Hugo\_RIVIERE](https://discuss.elastic.co/u/Hugo_RIVIERE)\
**Post date:** [October 1, 2024, 12:12pm UTC](https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084/4 "2024-10-01T12:12:25Z")

</div>

And the status of my cluster is green

---

<div class="post-metadata">

**Author:** ![Hugo\_RIVIERE](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hugo_riviere/32/138000_2.png) [@Hugo\_RIVIERE](https://discuss.elastic.co/u/Hugo_RIVIERE)\
**Post date:** [October 1, 2024, 1:06pm UTC](https://discuss.elastic.co/t/micrometer-registry-elastic-no-handler-found-for-uri-and-method-post/368084/5 "2024-10-01T13:06:19Z")

</div>

And when I check the index in the console, it returns

```auto
{
  micrometer-metrics-2024-10": {
    "aliases": {},
    "mappings": {
      "dynamic": "true",
      "_source": {
        "enabled": false
      },
...

```

Maybe it's this "enabled: false" that is causing the issue ?