[
https://issues.apache.org/jira/browse/SLING-11192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508792#comment-17508792
]
Robert Munteanu commented on SLING-11192:
-----------------------------------------
[~joerghoh] - yes, that is of course a valid approach. I was only wondering
whether this is a problem that occurs multiple times and some metrics are
inherently slow to calculate. But for now the sample size is 1 :-)
> Calculating metrics takes too long
> ----------------------------------
>
> Key: SLING-11192
> URL: https://issues.apache.org/jira/browse/SLING-11192
> Project: Sling
> Issue Type: Improvement
> Components: Event
> Affects Versions: Event 4.2.24
> Reporter: Joerg Hoh
> Priority: Major
>
> we use the prometheus exporter to export Sling Metrics / Dropwizard metrics,
> and we often see messages like this:
> {noformat}
> 10.03.2022 08:50:15.333 [...] *WARN* [qtp568481508-1779]
> io.prometheus.client.dropwizard.DropwizardExports Gauge has been blacklisted
> for 300000 ms due timeout: Generated from Dropwizard metric import
> (metric=sling_event.jobs.cancelled.count,
> type=org.apache.sling.event.impl.jobs.stats.GaugeSupport$2)
> {noformat}
> This means that calculating the metric took too long. We should make sure
> that the calculation is done asnychronously and just pre-computed values are
> returned.
> For at least these values the handling needs to be improved:
> * sling_event.jobs.active.count
> * sling_event.jobs.averageProcessingTime
> * sling_event.jobs.averageWaitingTime
> * sling_event.jobs.cancelled.count
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
