root
/
spring-boot
mirror of https://github.com/spring-projects/spring-boot.git
1
0
Fork 0
Code Issues Actions Packages Projects Releases Wiki Activity

Recommend third-party tracing/observability solutions 

Closes gh-17047
This commit is contained in:
Andy Wilkinson 2019-07-19 10:03:38 +01:00
parent 08afbe286c
commit 3dc20ff934
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -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 configuration. For convenience, Spring Boot offers an `InMemoryHttpTraceRepository` that stores traces
for the last 100 request-response exchanges, by default. `InMemoryHttpTraceRepository` is limited 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. compared to other tracing solutions and we recommend using it only for development environments.
For production environments, consider creating your own alternative `HttpTraceRepository` implementation. For production environments, use of a production-ready tracing or observability solution, such as
You can view the `httptrace` endpoint and obtain information about the request-response exchanges. 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`.