From aba1590b384c51fca7d40fd618df313a35f31952 Mon Sep 17 00:00:00 2001 From: buildmaster Date: Mon, 2 Jan 2017 10:08:24 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- spring-cloud-sleuth.html | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/spring-cloud-sleuth.html b/spring-cloud-sleuth.html index 28b9eed83..088881c04 100644 --- a/spring-cloud-sleuth.html +++ b/spring-cloud-sleuth.html @@ -471,6 +471,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
  • HTTP
  • Example
  • Custom SA tag in Zipkin
  • +
  • Custom service name
  • Span Data as Messages @@ -2021,6 +2022,21 @@ Remember not to add both peer.service tag and the SA t +
    +

    Custom service name

    +
    +

    By default Sleuth assumes that when you send a span to Zipkin, you want the span’s service name + to be equal to spring.application.name value. That’s not always the case though. There + are situations in which you want to explicitly provide a different service name for all spans coming + from your application. To achieve that it’s enough to just pass the following property + to your application to override that value (example for foo service name):

    +
    +
    +
    +
    spring.zipkin.service.name: foo
    +
    +
    +