Configure Lettuce with MicrometerTracing instead of MicrometerCommandLatencyRecorder when micrometer-tracing is available

[dungdm93]

Auto-configure lettuce tracing which available since lettuce 6.3

[wilkinsona]

Thanks for the PR.

The proposed change relates to #46456 and may not be quite right as @mp911de proposed switching from MicrometerCommandLatencyRecorder to MicrometerTracing rather than adding the latter alongside the former. In #46456 (comment), I wanted to check if we'd lose anything by always making the switch when ObservationRegistry is on the classpath.

@mp911de, can you please advise?

[mp911de]

This PR doesn't remove MicrometerCommandLatencyRecorder (which in fact should be done to avoid duplicate metrics for the general case) as per #46456 (comment). Other than that, this is the appropriate change.

[dungdm93]

@wilkinsona MicrometerCommandLatencyRecorder is for metrics, and MicrometerTracing is for tracing.

You can see more docs here

[mp911de]

MicrometerTracing uses the Observation API that is provided by Micrometer to achieve both, metrics and spans.

[wilkinsona]

Thanks, @mp911de.

@dungdm93, would you like to update your proposal accordingly? Instead of introducing a new LettuceTracingAutoConfiguration, the existing LettuceMetricsAutoConfiguration should be updated instead. It should be renamed to LettuceObservationAutoConfiguration and its content updated to match your proposed LettuceTracingAutoConfiguration.

[snicoll]

@dungdm93 how is it going? Let us know if you have time to amend the PR as described above. Thanks!