Browse Source

Recommend third-party tracing/observability solutions

Closes gh-17047
pull/17587/head
Andy Wilkinson 7 years ago
parent
commit
3dc20ff934
  1. 8
      spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

8
spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@ -2230,8 +2230,12 @@ HTTP Tracing can be enabled by providing a bean of type `HttpTraceRepository` in @@ -2230,8 +2230,12 @@ HTTP Tracing can be enabled by providing a bean of type `HttpTraceRepository` in
configuration. For convenience, Spring Boot offers an `InMemoryHttpTraceRepository` that stores traces
for the last 100 request-response exchanges, by default. `InMemoryHttpTraceRepository` is limited
compared to other tracing solutions and we recommend using it only for development environments.
For production environments, consider creating your own alternative `HttpTraceRepository` implementation.
You can view the `httptrace` endpoint and obtain information about the request-response exchanges.
For production environments, use of a production-ready tracing or observability solution, such as
Zipkin or Spring Cloud Sleuth, is recommended. Alternatively, create your own `HttpTraceRepository`
that meets your needs.
The `httptrace` endpoint can be used to obtain information about the request-response exchanges that
are stored in the `HttpTraceRepository`.

Loading…
Cancel
Save