-
Notifications
You must be signed in to change notification settings - Fork 471
[Spring Boot integration] Changing the jolokia default path to avoid 404 error #14475
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
base: main
Are you sure you want to change the base?
Conversation
Jolokia in Spring Boot is enabled by Spring-boot-actuator as described in the [reference](https://www.elastic.co/docs/reference/integrations/spring_boot#requirements), and the endpoint should have `/actuator` in front of the current default path. If we keep this default path, it will return 404 and the Elastic Agent's status will be changed to unhealthy. To avoid the confusion, suggest to change the default path value with the valid one
🚀 Benchmarks reportTo see the full report comment with |
Improve the path and host descriptions to avoid the confusion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @insukcho, please update the version
in manifest.yml
and add the corresponding enhancement
entry in the changelog.yml
This version will included the fix changing the jolokia default path to avoid 404 error
Add the change from the [PR](elastic#14475)
@mykola-elastic Thanks for the comment. I changed the version and the change logs. Please check and feel free to modify content if you need to. |
|
fixed the change type Co-authored-by: Ishleen Kaur <[email protected]>
💔 Build Failed
Failed CI StepsHistory
|
Proposed commit message
The Jolokia in Spring Boot is enabled by Spring-boot-actuator as described in the reference, and the endpoint should have
/actuator
in front of the current default path. If we keep this default path, it will return 404 and the Elastic Agent's status will be changed to unhealthy with the error logs below:To avoid the confusion, suggest to change the default path value with the valid one.
Additionally, the current
hosts
description is making confusion:Suggest to fix the example with only host URL, and move the left to the path's description.
Checklist
changelog.yml
file.How to test this PR locally
Reproduced and tested it with the version below:
full pom.xml config
Screenshots
Current default value in UI

Suggested value in UI
