Spring Data MongoDB leverages observability features (such as command listeners and connection pool hooks) to report metrics. While this is useful, it does not utilize the tracing API to create spans.

In our implementation, we should focus on generating spans at the operation level. This approach integrates into a holistic view of the operation flow. For example, tracing from an HTTP call to a backend service, which then invokes a microservice that interacts with the MongoDB driver, provides significantly more context for understanding application behavior than standalone gauges or metric reports.

Note: Default metrics can be disabled in the configuration to avoid duplication between observability and tracing.

management.metrics.mongo.command.enabled=false management.metrics.mongo.connectionpool.enabled=false