Provide a configuration property to specify the order of the ServerHttpObservationFilter

[davidmelia]

Hi,

Migrating from Spring Cloud Sleuth to Spring Boot 3 there used to be a property to override the TraceFilter:

spring:
  sleuth:
    web:
      filter-order: -111

which is quite important for us as we have some filters which we need to run before any observation. I have noticed in Spring Boot 3 the order is hardcoded:

public class WebFluxObservationAutoConfiguration {

...

	@Bean
	@ConditionalOnMissingBean
	@Order(Ordered.HIGHEST_PRECEDENCE + 1)
	public ServerHttpObservationFilter webfluxObservationFilter(ObservationRegistry registry,

}

Is it possible to override ServerHttpObservationFilter order (specifically the reactive version)?

Thanks

[wilkinsona]

we have some filters which we need to run before any observation

Any filters with highest precedence should run before ServerHttpObservationFilter.

Is it possible to override ServerHttpObservationFilter order

There's no property-based support for this at the moment. Without that support you'd have to define your own ServerHttpObservationFilter bean with an appropriate @Order annotation on the @Bean method.

[davidmelia]

Issue I have is ServerHttpObservationFilter is ordered as Ordered.HIGHEST_PRECEDENCE + 1 and I have three other filters. This gives me the only option to use Ordered.HIGHEST_PRECEDENCE which will randomly be ordered. :-(

I can define my own ServerHttpObservationFilter no problem but a property would be cleaner.

Thanks

[mhalbritter]

The property is named management.observations.http.server.filter.order.

[wilkinsona]

We need to consider the servlet side of things as well. The property should either be applied to the auto-configured webMvcObservationFilter or its name should indicate that it's specific to reactive. Probably the former.