-
Notifications
You must be signed in to change notification settings - Fork 40.8k
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
Spring Actuator AuditEvents Defaults to enabled, however seems to conflict with new Access.java constraints #43366
Comments
I don't think this is related to Line 65 in 91778e9
This is reading the value of the Given the above, it would appear that Please check your application's environment and correct the value of |
We have removed all references to I do agree with the snippet provided and quintuple checking our configurations now. However since I've removed all references to it in our application files, I wouldn't expect it to be being configured. |
The property isn't set by default so I believe you must have missed an occurrence where it's being set to a non-boolean value. It could be coming from a system property or an environment variable, for example, not just from application configuration files. If you debug your application with a breakpoint on line 65 of |
Happy to say you put us on the right path. Turns out our env vars had conflicting names with the underlying spring properties, thus were overruling. Naivety on my part. Appreciate the direction! |
Good to hear that you figured it out. Thanks for letting us know. Boot could be more helpful here by handling the
I've opened #43378 to track this. |
Explictly we are only using the health and info actuator endpoints. See the below config for relevant configuration:
However since updating to Spring Boot 3.4.0 and using the new endpoint Access syntax, when attempting to run in our deployed environment we have found the following startup issue.
This appears to be associated with the default being:
management.auditevents.enabled=true
We don't necessarily have a need for auditevents, though it seems to be a bug as it's trying to use the Access.java value of
none
and expecting a booleanThe text was updated successfully, but these errors were encountered: