Markus Ruecker

Yes we are currently using snappy because GZIP is too heavy on CPU

Hi there, we use Kotlin helper functions to create timers and distributions with a variable number of percentiles. Since we don't know the metrer names id advance I can't see...

>I think registering a MeterFilter every single time you create a meter is a bad idea I fully agree. We don't do this for every meter. However we want to...

>Historically, we have allowed configuring MeterFilters after meters have been registered. Depending on how meters are used, the negative effects of doing this can be minimal. It is ideal to...

Thank you for the detailled explanation. This makes more sense and I see where you are coming from. Our use case is a bit different. When we create a new...

We use various frameworks for our (roughly 150) microservices, mostly Vertx, Micronaut and Ktor. The problem is that a big junk of the business logic is encapsulated in modules that...

I get you point and for most of our meters we use existing MeterFilters that have been created in our framework wrapper before any Meter creation. However sometimes developers want...

We decided to load all MeterFilters via java ServiceLoader when configuring the meter registry in our various frameworks. This allows developers to implement their own individual MeterFilters without messing around...