Add MVC and JMX endpoints to retrieve audit events
Add MVC and JMX specific endpoints that allow audit events to be retrieved. See gh-6579
This commit is contained in:
committed by
Phillip Webb
parent
a6d18f714f
commit
2f1e4f0c02
@@ -961,6 +961,10 @@ content into your application; rather pick only the properties that you need.
|
||||
endpoints.actuator.enabled=true # Enable the endpoint.
|
||||
endpoints.actuator.path= # Endpoint URL path.
|
||||
endpoints.actuator.sensitive=false # Enable security on the endpoint.
|
||||
endpoints.auditevents.enabled= # Enable the endpoint.
|
||||
endpoints.auditevents.id= # Endpoint identifier.
|
||||
endpoints.auditevents.path= # Endpoint path.
|
||||
endpoints.auditevents.sensitive= # Mark if the endpoint exposes sensitive information.
|
||||
endpoints.autoconfig.enabled= # Enable the endpoint.
|
||||
endpoints.autoconfig.id= # Endpoint identifier.
|
||||
endpoints.autoconfig.path= # Endpoint path.
|
||||
|
||||
@@ -73,6 +73,10 @@ The following technology agnostic endpoints are available:
|
||||
HATEOAS to be on the classpath.
|
||||
|true
|
||||
|
||||
|`auditevents`
|
||||
|Exposes audit events information for the current application.
|
||||
|true
|
||||
|
||||
|`autoconfig`
|
||||
|Displays an auto-configuration report showing all auto-configuration candidates and the
|
||||
reason why they '`were`' or '`were not`' applied.
|
||||
|
||||
Reference in New Issue
Block a user