Asaf Mesika

Seems that Summary is defined in the OT spec as can be seen [here](https://opentelemetry.io/docs/reference/specification/metrics/datamodel/#summary-legacy) and [here](https://opentelemetry.io/docs/reference/specification/metrics/datamodel/#point-kinds). Given that, is it possible to contribute code to support it?

> I think in general it makes a lot of sense. But here is the counter example (seen in the wild): the query phase take a very long time, following...

This is great works towards supplying observability of search requests, specifically per shard (once done). I was wondering what is the state of this issue?

> @asafm @tjiuming please review @lhotari Done. I suggested several changes.

> > > Can we enable conditional compression that only compresses payloads above a certain size? > > > > > > Yes, that is supported in GzipHandler. > >...

I don't understand something. You're using an internal class from the JDK - it's internal - you're not supposed to use it as is no? How is the JDK itself...

>And, for the CPU usage we have our own calculation formula, which is not exactly the same as OperatingSystemMXBean#getCpuLoad. Can you please explain why it is different? I do see...

Ok, I did some reading and this is what I found: 1. Usage calculation in `OperatingSystemMXBean` which delegates to `OperatingSystemImp` gives you the percentage of usage of CPU relative to...

Please note that I haven't found any other open source that uses `jdk.internal.platform.Metrics` - I tried searching using TabNine code search and also GitHub search.

>However, LB also requires other signals such as dict_memory_usage_in_percent_cgroup, network_usage_in_percent_cgroup, which require separate limits for their percentage computation. Can you please expand on that? I don't any method providing usage...