Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jvm metrics lost (2.5.+) #30802

Closed
Darkvater opened this issue Apr 27, 2022 · 4 comments
Closed

jvm metrics lost (2.5.+) #30802

Darkvater opened this issue Apr 27, 2022 · 4 comments
Labels
status: invalid An issue that we don't feel is valid

Comments

@Darkvater
Copy link

Darkvater commented Apr 27, 2022

Description

Upgrading from spring-boot 2.3.4 to 2.5(.4) removed all the jvm, and other metrics from /actuator/metrics only leaving hikari/tomcat.

This is a similar issue to #26630 blaming spring-boot-starter-data-jpa.

This could be the case, however if spring-boot-starter-security is additionally added to the project with adding @EnableWebSecurity (and an empty WebSecurityConfigurer) the jvm metrics are back.

Behaviour is the same also in the latest 2.5.13 version.

Question/Bug:

How do I get the jvm- metrics working with spring-boot-starter-data-jpa (if it is still a contributing factor) and without spring-boot-starter-security?

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Apr 27, 2022
@Darkvater Darkvater changed the title jvm metrics lost (2.5+) jvm metrics lost (2.5.+) Apr 27, 2022
@wilkinsona
Copy link
Member

This sounds like it could be due to some eager initialization (as was the case with #26630) but I can't say for certain without knowing more about the problem. If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

@wilkinsona wilkinsona added the status: waiting-for-feedback We need additional information before we can continue label Apr 27, 2022
@Darkvater
Copy link
Author

Give me a bit of time. Created a skeleton project, and of course it is working in all scenarios (2.5.4 with spring-data-jpa, with spring-data-jpa, spring-security, and without either) so this is annoying. Now I have to start trimming down the real-life project to find out where the issue actually lies... back in a day or two

@spring-projects-issues spring-projects-issues added status: feedback-provided Feedback has been provided and removed status: waiting-for-feedback We need additional information before we can continue labels Apr 27, 2022
@bclozel bclozel added status: waiting-for-feedback We need additional information before we can continue and removed status: feedback-provided Feedback has been provided labels Apr 27, 2022
@Darkvater
Copy link
Author

I am sad/happy to report that the fact the metrics are gone is due to some oracle-aq queue functionality we are using. It's something crap built internally and it's impossible to puzzle out exactly which insane configuration there causes this issue.
Good for spring-boot, it is working otherwise :)

@wilkinsona
Copy link
Member

Thanks for letting us know.

@wilkinsona wilkinsona added status: invalid An issue that we don't feel is valid and removed status: waiting-for-feedback We need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

4 participants