Spring Cloud Gateway + Actuator + Micrometer Tracing - not creating a new trace id on each new request

[nathandeamer]

Spring Cloud Gateway: 2022.0.4
Spring Boot: 3.1.4
Micrometer Tracing: 1.1.6

Every request to /actuator/health is re-using the same trace id despite being separate calls.

How to reproduce:

> docker-compose up
> watch -n 5 curl http://localhost:8080/actuator/health`
> View traces: http://localhost:16686/search

demo.zip

[nathandeamer]

Looks like once actuator gets called, trace ids stop changing for every subsequent request (to actuator or other endpoint)

watch -n 5 curl curl localhost:8080/anything/resources
wait 5-10 seconds
watch -n 30 curl localhost:8080/actuator/health

[jonatan-ivanov]

Could you please try to check what happens if you downgrade to 1.1.4 or upgrade to 1.2.0-RC1?

[chemicL]

The demo project resolves 1.1.5 of micrometer-tracing. Only micrometer-tracing-bridge-brave gets resolved to 1.1.6. I believe that is the reason for the bug. Please validate after you include:

implementation platform('io.micrometer:micrometer-tracing-bom:1.1.6')

[nathandeamer]

When micrometer-tracing and micrometer-tracing-bridge-brave both get resolved to 1.1.6 the problem is fixed.

However, I couldn't get implementation platform('io.micrometer:micrometer-tracing-bom:1.1.6') to pull in the correct dependency versions (not sure why, theory is the io.spring.dependency-management plugin is taking priority?)

Instead I imported it this way:

dependencyManagement {
	imports {
		mavenBom 'io.micrometer:micrometer-tracing-bom:1.1.6'
	}
}

dependencies {
	...
	implementation 'io.micrometer:micrometer-tracing-bridge-brave'
	...
}

Result:

./gradlew dependencies --configuration compileClasspath | grep micrometer
+--- io.micrometer:micrometer-tracing-bridge-brave -> 1.1.6
|    +--- io.micrometer:micrometer-tracing:1.1.6
|    |    +--- io.micrometer:micrometer-observation:1.11.5 (*)
|    |    +--- io.micrometer:context-propagation:1.0.6
          |    |    \--- io.micrometer:micrometer-observation:1.10.11 -> 1.11.5 (*)

[nathandeamer]

Could you please try to check what happens if you downgrade to 1.1.4 or upgrade to 1.2.0-RC1?

1.1.4 and 1.2.0-RC1 both resolve the problem too

dependencyManagement {
	imports {
		mavenBom 'io.micrometer:micrometer-tracing-bom:[1.1.4|1.2.0-RC1]' 
	}
}

[nathandeamer]

Overriding the versions provided by io.spring.dependency-management plugin would also work:

ext {
	set('micrometer-tracing.version', "1.1.6")
	set('micrometer-tracing-bridge-brave.version', "1.1.6")

}

Looks like the upcoming Spring Boot 3.15 release this week will upgrade micrometer-tracing to 1.1.6
spring-projects/spring-boot#37694

[jonatan-ivanov]

When micrometer-tracing and micrometer-tracing-bridge-brave both get resolved to 1.1.6 the problem is fixed.

That's great to hear!
3.1.5 should be released on Thursday (in two days: 2023-10-19). You can try out 3.1.5-SNAPSHOT early if you want to check what happens.

With this, let me close the issue, thank you all for looking into this!