Actuator prometheus endpoint spring stopped working after upgrading to 1.13 about micrometer

[shakuzen]

I've added a Frameworks section to the Migration Guide, including a sub-section for Spring Boot. Could folks who ran into this issue give us feedback on if those sections in the guide would have sufficiently explained the issue faced here? @rohan-changejar @joethehoff @IlyaLisov

[IlyaLisov]

@shakuzen It is good explained and I found this really helpful. I think that sometimes some devs upgrading dependencies with minor/patch changes without any thoughts, so it could lead to such issues if there are no info in release notes
Thank you again! You helped me

[shakuzen]

What version of Spring Boot are you using? Typically, if you're using Spring Boot, you should allow its dependency management to manage the versions of dependencies unless you have a reason to override it. I believe Spring Boot 3.3.0 (scheduled to be released next week) will manage Micrometer dependencies to version 1.13.0.

[rohan-changejar]

What version of Spring Boot are you using? Typically, if you're using Spring Boot, you should allow its dependency management to manage the versions of dependencies unless you have a reason to override it. I believe Spring Boot 3.3.0 (scheduled to be released next week) will manage Micrometer dependencies to version 1.13.0.

We are using this version of spring id 'org.springframework.boot' version '3.2.5', do you see any correlation of this issue with this version?

If it is related, would propose adding this as a warning on the migration guide.

Let me know if I could be of any help here

[checketts]

@rohan-changejar If you can provide a link to code that reproduces the issue, that could be useful. Just a simple minimal product is fine.

Often when I try to create one, the underlying bug is revealed

[joethehoff]

Same problem on my side using spring-boot 3.2.5
After upgrading to 1.13 there were no output at localhost:9005/actuator/prometheus anymore.
This are the management-props of application.properties

management:
  endpoint:
    health.enabled: true
    prometheus.enabled: true
  endpoints:
    enabled-by-default: false
    web.exposure.include: info, prometheus, health
  server:
    address: 0.0.0.0
    port: 9005

In sourecode we just use static Metrics-methods like this:

Metrics.counter("xxxx").increment();

[rohan-changejar]

@rohan-changejar If you can provide a link to code that reproduces the issue, that could be useful. Just a simple minimal product is fine.

Often when I try to create one, the underlying bug is revealed

Created a project demonstrating this issue, Github link.
You can use the main branch to reproduce the issue.
If you want to see the feature working on the previous version
please refer the branch [workingVersion](https://github.com/rohan-changejar/demo-micrometer-bug/tree/workingVersion)

on 1.12.6

on 1.13.0

[ttddyy]

@rohan-changejar Have you read the "1.13 Migration Guide".
Also, this comment explains the background: #5093 (comment)

If you change the dependency from micrometer-registry-prometheus to micrometer-registry-prometheus-simpleclient, your sample works.

This is essentially a duplicate of #5093

[jonatan-ivanov]

I would recommend letting Boot to set the version for libraries it has auto-configuration for (e.g. Micrometer). If you really want to migrate to Micrometer 1.13 with Bot 3.2 (btw 3.3 is coming next week with Micrometer 1.13 support), check Tadaya's comment, you need to change the name of the dependency when you change the version.

[jonatan-ivanov]

Duplicate of #5093