Re: [prometheus-users] max latency value (golang client)

2021-01-30 Thread Julius Volz
Getting that one value out from the summary is only possible in a somewhat cumbersome way: you could call the Write() method on the metric to dump the summary into a protobuf object: https://godoc.org/github.com/prometheus/client_golang/prometheus#Metric. Then you can read desired field out of the

Re: [prometheus-users] max latency value (golang client)

2021-01-29 Thread Rafal Skolasinski
Hi Julius, I think having max latency over the max-age window is good. That’s what I believe we had before in the Java app. Is possible to easily get the value from summary that corresponds to quantile=1 and expose it as separate gauge? I would like to avoid trouble of reinventing the wheel

Re: [prometheus-users] max latency value (golang client)

2021-01-29 Thread Julius Volz
Hi Rafal, That would still be the way to do it. Note that in the Go client library at least, the summaries are computed over a max-age window within which the observations are relevant or the summary output: https://github.com/prometheus/client_golang/blob/b8fcd28885584356c562e9ecad42cbec45f4ce96/

[prometheus-users] max latency value (golang client)

2021-01-29 Thread Rafal Skolasinski
Hi Everyone, Some time ago we moved one of our applications from Java (instrumented with micrometer library) to Go and used prometheus/golang_client to instrument it. Our old application was in addition to summary quantiles also reporting max latency that was registered. Recently users have