From 3dc20ff934f731cd93ecb10fb9c04f6bcb38d7dc Mon Sep 17 00:00:00 2001 From: Andy Wilkinson Date: Fri, 19 Jul 2019 10:03:38 +0100 Subject: [PATCH] Recommend third-party tracing/observability solutions Closes gh-17047 --- .../src/main/asciidoc/production-ready-features.adoc | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index 24c1576c42d..9d7cc9b492c 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/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 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`.