When converting Micrometer data to Otlp, the max value in Timer will be lost in the default configuration.

[songmiao-hhh]

I have Redis latency statistics recorded by Lettuce in Spring Boot, and latency statistics are Micrometer data. When I try to send the latency statistics to my otlp collector , I found that the max data in the Micrometer Timer was lost after the latency statistics were converted to Otlp data.
My configuration is as follows：
otel.resource.attributes=service.name=otlpTest management.otlp.metrics.export.url=http://localhost:8000/v1/metrics management.otlp.metrics.export.aggregationTemporality="delta" management.metrics.distribution.percentiles-histogram.lettuce.command.completion=true
Spring Boot version : 3.4.3

[wilkinsona]

Exporting Micrometer's meters in OTLP format is handled by Micrometer's OtlpMeterRegistry and Spring Boot isn't really involved. As such, I think it's likely that this is a Micrometer issue rather than a Spring Boot issue. To help us or the Micrometer team determine the cause, please provide a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

[BenEfrati]

The only way is to register a gauge for max.
Check this change in OtlpMetricConverter
BenEfrati/micrometer@1796553
BenEfrati/micrometer@bdb0cb6

micrometer-metrics/micrometer#3144 (comment)

[wilkinsona]

Thanks very much, @BenEfrati. I'll close this one in favor of the existing Micrometer issue.