Rename trace to httptrace
Closes gh-11806
This commit is contained in:
@@ -1206,6 +1206,10 @@ content into your application. Rather, pick only the properties that you need.
|
||||
management.endpoint.heapdump.cache.time-to-live=0ms # Maximum time that a response can be cached.
|
||||
management.endpoint.heapdump.enabled= # Whether to enable the heapdump endpoint.
|
||||
|
||||
# HTTP TRACE ENDPOINT ({sc-spring-boot-actuator}/web/trace/HttpTraceEndpoint.{sc-ext}[HttpTraceEndpoint])
|
||||
management.endpoint.httptrace.cache.time-to-live=0ms # Maximum time that a response can be cached.
|
||||
management.endpoint.httptrace.enabled= # Whether to enable the HTTP trace endpoint.
|
||||
|
||||
# INFO ENDPOINT ({sc-spring-boot-actuator}/info/InfoEndpoint.{sc-ext}[InfoEndpoint])
|
||||
info= # Arbitrary properties to add to the info endpoint.
|
||||
management.endpoint.info.cache.time-to-live=0ms # Maximum time that a response can be cached.
|
||||
@@ -1250,10 +1254,6 @@ content into your application. Rather, pick only the properties that you need.
|
||||
management.endpoint.threaddump.cache.time-to-live=0ms # Maximum time that a response can be cached.
|
||||
management.endpoint.threaddump.enabled= # Whether to enable the threaddump endpoint.
|
||||
|
||||
# TRACE ENDPOINT ({sc-spring-boot-actuator}/web/trace/HttpTraceEndpoint.{sc-ext}[HttpTraceEndpoint])
|
||||
management.endpoint.trace.cache.time-to-live=0ms # Maximum time that a response can be cached.
|
||||
management.endpoint.trace.enabled= # Whether to enable the trace endpoint.
|
||||
|
||||
# JOLOKIA ENDPOINT ({sc-spring-boot-actuator-autoconfigure}/jolokia/JolokiaProperties.{sc-ext}[JolokiaProperties])
|
||||
management.endpoint.jolokia.config.*= # Jolokia settings. See the Jolokia manual for details.
|
||||
management.endpoint.jolokia.enabled=true # Whether to enable Jolokia.
|
||||
@@ -1281,6 +1281,10 @@ content into your application. Rather, pick only the properties that you need.
|
||||
management.health.status.http-mapping= # Mapping of health statuses to HTTP status codes. By default, registered health statuses map to sensible defaults (for example, UP maps to 200).
|
||||
management.health.status.order=DOWN, OUT_OF_SERVICE, UP, UNKNOWN # Comma-separated list of health statuses in order of severity.
|
||||
|
||||
# HTTP TRACING ({sc-spring-boot-actuator-autoconfigure}/web/trace/HttpTraceProperties.{sc-ext}[HttpTraceProperties])
|
||||
management.httptrace.enabled=true # Whether to enable HTTP request-response tracing.
|
||||
management.httptrace.include=request-headers,response-headers,cookies,errors # Items to be included in the trace.
|
||||
|
||||
# INFO CONTRIBUTORS ({sc-spring-boot-actuator-autoconfigure}/info/InfoContributorProperties.{sc-ext}[InfoContributorProperties])
|
||||
management.info.build.enabled=true # Whether to enable build info.
|
||||
management.info.defaults.enabled=true # Whether to enable default info contributors.
|
||||
@@ -1375,10 +1379,6 @@ content into your application. Rather, pick only the properties that you need.
|
||||
management.metrics.web.server.record-request-percentiles=false # Whether instrumented requests record percentiles histogram buckets by default.
|
||||
management.metrics.web.server.requests-metric-name=http.server.requests # Name of the metric for received requests.
|
||||
|
||||
# TRACING ({sc-spring-boot-actuator-autoconfigure}/web/trace/TraceProperties.{sc-ext}[TraceProperties])
|
||||
management.trace.enabled=true # Whether to enable HTTP request-response tracing.
|
||||
management.trace.include=request-headers,response-headers,cookies,errors # Items to be included in the trace.
|
||||
|
||||
|
||||
# ----------------------------------------
|
||||
# DEVTOOLS PROPERTIES
|
||||
|
||||
@@ -96,6 +96,11 @@ classes and the reasons why they did or did not match.
|
||||
|Shows application health information.
|
||||
|Yes
|
||||
|
||||
|`httptrace`
|
||||
|Displays HTTP trace information (by default, the last 100 HTTP request-response
|
||||
exchanges).
|
||||
|Yes
|
||||
|
||||
|`info`
|
||||
|Displays arbitrary application info.
|
||||
|Yes
|
||||
@@ -133,10 +138,6 @@ store. Not available when using Spring Session's support for reactive web applic
|
||||
|Performs a thread dump.
|
||||
|Yes
|
||||
|
||||
|`trace`
|
||||
|Displays HTTP trace information (by default, the last 100 HTTP requests).
|
||||
|Yes
|
||||
|
||||
|===
|
||||
|
||||
If your application is a web application (Spring MVC, Spring WebFlux, or Jersey), you can
|
||||
@@ -243,6 +244,10 @@ endpoints:
|
||||
|N/A
|
||||
|No
|
||||
|
||||
|`httptrace`
|
||||
|Yes
|
||||
|No
|
||||
|
||||
|`info`
|
||||
|Yes
|
||||
|Yes
|
||||
@@ -291,10 +296,6 @@ endpoints:
|
||||
|Yes
|
||||
|No
|
||||
|
||||
|`trace`
|
||||
|Yes
|
||||
|No
|
||||
|
||||
|===
|
||||
|
||||
To change which endpoints are exposed, use the following technology-specific `expose` and
|
||||
@@ -1309,22 +1310,22 @@ implementing `ApplicationEventPublisherAware`).
|
||||
|
||||
|
||||
|
||||
[[production-ready-tracing]]
|
||||
== Tracing
|
||||
Tracing is automatically enabled for all HTTP requests. You can view the `trace` endpoint
|
||||
and obtain basic information about the last 100 requests.
|
||||
[[production-ready-http-tracing]]
|
||||
== HTTP Tracing
|
||||
Tracing is automatically enabled for all HTTP requests. You can view the `httptrace`
|
||||
endpoint and obtain basic information about the last 100 request-response exchanges.
|
||||
|
||||
|
||||
|
||||
[[production-ready-custom-tracing]]
|
||||
=== Custom tracing
|
||||
[[production-ready-http-tracing-custom]]
|
||||
=== Custom HTTP tracing
|
||||
To customize the items that are included in each trace, use the
|
||||
`management.trace.include` configuration property.
|
||||
`management.httptrace.include` configuration property.
|
||||
|
||||
By default, an `InMemoryTraceRepository` that stores the last 100 events is used. If you
|
||||
need to expand the capacity, you can define your own instance of the
|
||||
`InMemoryTraceRepository` bean. You can also create your own alternative
|
||||
`TraceRepository` implementation.
|
||||
By default, an `InMemoryHttpTraceRepository` that stores traces for the last 100
|
||||
request-response exchanges is used. If you need to expand the capacity, you can define
|
||||
your own instance of the `InMemoryHttpTraceRepository` bean. You can also create your own
|
||||
alternative `HttpTraceRepository` implementation.
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user