[
https://issues.apache.org/jira/browse/SOLR-15564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrzej Bialecki updated SOLR-15564:
------------------------------------
Attachment: SOLR-15564.patch
> Improve filtering expressions in /admin/metrics
> -----------------------------------------------
>
> Key: SOLR-15564
> URL: https://issues.apache.org/jira/browse/SOLR-15564
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Priority: Major
> Attachments: SOLR-15564.patch
>
>
> There are currently several ways to filter what metrics should be returned by
> /admin/metrics but they have one important limitation: all types of filtering
> criteria (group, type, prefix, regex, key) use implicit OR, so it's only ever
> possible to broaden the filters but not to narrow them down.
> This issue came up while I was reviewing the default Prometheus exporter
> config and I noticed that it pulls ALL metrics. This is extremely wasteful
> and puts unnecessary load on the nodes, especially since only some of the
> metrics are then used, either by the exporter itself or by the default
> dashboard. In addition to that, the exporter needs to build an object tree
> from all these metrics in order to apply the export rules, which leads to
> excessive memory / cpu consumption in the reporter process.
> We should come up with a way to make these filters more expressive so that
> it's possible e.g. to select only some metrics from a particular registry.
> The simplest way to implement this would be to extend the syntax of the
> {{key}} parameter to support regex expressions in the parts of the key that
> specify the metric name and the property name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
