Prometheus integration not scraping summary metrics

[Alphayeeeet]

Everything is literally mentioned in the discussion post, but no one cared about it and therefore there are no answers.

For confirmed bugs, please report:

• Version: 8.12.2
• Operating System: RHEL 8
• Discuss Forum URL: https://discuss.elastic.co/t/prometheus-integration-not-scraping-summary-metrics/352083
• Steps to Reproduce: Let Prometheus integration scrape an enpoint with summary metrics.

[pierrehilbert]

@bturquet could someone have a look here please?

[bturquet]

@lalit-satapathy This request is for you as it as about Prometheus, thank you !

[lalit-satapathy]

Refer old beats issue: https://github.com/elastic/beats/issues/37376

@ishleenk17, Can you summarise what needs to happen here and if it is ready to be taken next?

[ishleenk17]

@Alphayeeeet : I am looking into it. Will get back to you soon!

[ishleenk17]

Hello,

I tried out with a service having summary metrics as below:

I see them getting indexed in the ES:

For getting the summary metrics, please ensure the use_types and rate counters are enabled (these are enabled by default)

Please let me know if this helps.

[Alphayeeeet]

@ishleenk17 Thank you for the reply.

I have the following prometheus metric:

...which I do net get in the event:

Maybe it has something to do with the mappings? My events are just ingested as numbers. Still there are no separate values for each quantile (which should be available in my opinion, maybe configurable if it's optional)

My agent config is the following:

[ishleenk17]

Still there are no separate values for each quantile (which should be available in my opinion, maybe configurable if it's optional)

We don't give direct values of quantiles. Although, if you would want to check the values you can see from the ".value" field of the metric and then by opening the event you can see the quantile it corresponds to

[Alphayeeeet]

Still there are no separate values for each quantile (which should be available in my opinion, maybe configurable if it's optional)

We don't give direct values of quantiles. Although, if you would want to check the values you can see from the ".value" field of the metric and then by opening the event you can see the quantile it corresponds to

@ishleenk17 This should be a basic feature in my opinion, that I can decide, which quantile metric to use (all of them should be present in the event). Still I do not even get the '.value' field as stated out above in my screenshots. There are no metrics of '*_blobstorefile...' present in my event. With this funcionality, the integration is not useable for our usecases...

[ishleenk17]

@Alphayeeeet : Please share the stack and integration version you are using ?

[Alphayeeeet]

@ishleenk17 As stated out above, the stack version including the agents is 8.12.2.

Integration version: Tried with Prometheus Input v0.4.0 Also tried with Prometheus v1.15.0

Im happy to fully use the Prometheus Integration if it is fixed there.

[Alphayeeeet]

Is it possible to open a separate feature request for a configurable option to include the quantile values as distinct fields?

[ishleenk17]

Is it possible to open a separate feature request for a configurable option to include the quantile values as distinct fields?

Yes, we can open a ticket. Although, I would first revisit the decision of showing these quantile values as part of a single field. I will keep you posted on this thread.

[Alphayeeeet]

@ishleenk17 Are there any updates by now?