[
https://issues.apache.org/jira/browse/SOLR-18326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101106#comment-18101106
]
David Smiley commented on SOLR-18326:
-------------------------------------
One of my objectives here was to not calculate an expensive metric. A
conversation with Claude on this front revealed that the proposed OTLP
filtering here (and the existing prometheus side we _already_ have) does *not*
accomplish that goal. In another issue we'll have the ability to completely
disable metrics which is helpful but the all-or-nothing choice is unfortunate.
Also, OTEL View isn't for this issue; it's apparently a global/universal filter
(would be applied at startup and not changed), not specific to exporters like
OTLP. Using Views would filter deeper and thus apply to both Prometheus
exporting and OTLP as well. Not a bad thing but limited utility. Again, won't
avoid expensive gauge computation.
So I think this issue, explicitly discussing OTLP, *if* pursued, is scoped to
the more narrow benefit of reducing communicating data that isn't needed (via
OTLP). If this is pursued, perhaps it should be scoped down to just be a
metric name filter, leaving attribute level concerns to the recipient side.
The initial plan, attached, is more complex.
> OTEL OTLP filtering for metrics
> -------------------------------
>
> Key: SOLR-18326
> URL: https://issues.apache.org/jira/browse/SOLR-18326
> Project: Solr
> Issue Type: New Feature
> Components: metrics
> Reporter: David Smiley
> Priority: Major
> Attachments: SOLR-18326-OTLP-metrics-filter.md
>
>
> We have no metrics filtering capability for pushing metrics via OTLP. We do
> for Prometheus scraping (pull). Given the vast amount of metrics Solr
> offers, plus some call expensive handlers (e.g. that measure index size),
> this is a big problem for practical / scalable use of OTLP push.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
