by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 14:39
    marcingrzejszczak commented #1491
  • 14:37
    spring-issuemaster unlabeled #1491
  • 14:37
    spring-issuemaster labeled #1491
  • 14:37
    robotmrv commented #1491
  • 14:22
    spring-issuemaster labeled #1673
  • 14:22
    spring-issuemaster commented #1673
  • 14:09
    spencergibb labeled #1491
  • 14:09
    spencergibb unlabeled #1491
  • 14:09
    spencergibb commented #1491
  • 14:05
    spencergibb assigned #656
  • Jul 03 18:32
    Happy-Neko commented #1672
  • Jul 03 17:33
    CircleCI failed: spring-cloud build (#6261) in https://github.com/spring-cloud/spring-cloud-sleuth
  • Jul 03 17:28

    marcingrzejszczak on reactor_improvements_yet_again

    WIP (compare)

  • Jul 03 16:22
    spring-issuemaster labeled #1672
  • Jul 03 16:22
    Happy-Neko commented #1672
  • Jul 03 06:27
    spring-issuemaster labeled #1677
  • Jul 03 06:23
    kprasad99 opened #1677
  • Jul 01 07:43
    davidmelia commented #1627
  • Jul 01 07:43
    davidmelia commented #1627
  • Jun 30 18:35
    codecov[bot] commented #1676
Adrian Cole
@adriancole
@uckyk looks like context leak (same trace ID stuck on a thread)
so depending on what's used and what is in the classpath might explain
Ucky.Kit
@uckyk
image.png
Adrian Cole
@adriancole
ok that is sadly a dead end version
Ucky.Kit
@uckyk
Because the project is relatively old, the introduced version of spring cloud is relatively low
Adrian Cole
@adriancole
even 2.0 2.1 aren't maintained anymore
this version used a way for "scoping" which was not try/finally in nature
and so had a higher chance of leaks vs the 2.x line which use brave's CurrentTraceContext api
Ucky.Kit
@uckyk
I have observed that the 2. X version basically uses the wave related POM
Adrian Cole
@adriancole
yeah the custom tracing api from 1.x is no longer around
Ucky.Kit
@uckyk

So the current solution is that I upgrade the access version better, right?

Because there are fewer context leaks in higher versions

Adrian Cole
@adriancole
it is a completely different api which was designed to make less leaks
there are still some leak problems in sleuth mostly in reactor
but for webmvc normal should be none
there's always chance for leak
main thing is less chance, the try/finally api makes it easy to see when people make leaky stuff
ex ever see something should be used in try/finally and carelessly doesn't close
if api isn't meant to be try/finally it is very hard to see where leak occurs
this is the technical reason why 2.x should be less leaks and generally is
Ucky.Kit
@uckyk
OK, I'll try to upgrade version 2. X and see if there are similar problems. Thank you very much!
Adrian Cole
@adriancole
sure 2.2.3 is out now, so try (it works with spring boot 2.2 and 2.3)
Ucky.Kit
@uckyk
got it,
thx!!!
Adrian Cole
@adriancole
np!
Marcin Grzejszczak
@marcingrzejszczak
with 1.3.x we had our own tracer implementation, in 2.x we've migrated to Brave and lots of bugs was fixed since then so absolutely we advise to migrate to the latest stable version
Veera93
@Veera93
Hi All,
I am relatively new to sleuth framework.. I have an usecase where traceId needs to be sent back in the response header. I was hoping to achieve the same using annotations or configuration. When I had searched they were achieved by adding filters (also found few old threads where they had mentioned that sending traceId in the response header has been removed due to potential security concern). In the latest implementation are there any configuration/annotations for the same or I would have to write a trace filter? Any help on this is appreciated
Adrian Cole
@adriancole
@Veera93 still the same
the tracing system does not mutate the response at the moment, so it can't write response headers
Saisurya Kattamuri
@saisuryakat
Hi
What's the difference between spring.sleuth.remote-fields vs spring.sleuth.baggage.remote-fields
In the sleuth properties appendix its given with baggage. whereas in the documentation without
https://cloud.spring.io/spring-cloud-sleuth/reference/html/appendix.html
image.png
Which of these is correct
the link you are pointing to is the version 3 docs
ah I see what you are saying
thanks. can you do a pull request to fix this?
Saisurya Kattamuri
@saisuryakat
Sure, I can
but I'm having trouble making baggage fields work
Is there any sample repo present for reference
image.png
I'm confused esp whether to just define the headers in application.yml and set the values in controller or to config brave(as shown in brave docs)
Adrian Cole
@adriancole
if you are doing what the properties can do, just use the properties
brave is used for other things even spring 2.5
sleuth has things built-in so easier to use properties than javaconfig for the same result
I'm changing example project for you hold a sec
Saisurya Kattamuri
@saisuryakat
Okay
Adrian Cole
@adriancole
Saisurya Kattamuri
@saisuryakat
Thanks
Adrian Cole
@adriancole
just tested so :thumbsup:
Saisurya Kattamuri
@saisuryakat
Adrian Cole
@adriancole
:bow: