[
https://issues.apache.org/jira/browse/SOLR-17115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17816483#comment-17816483
]
David Smiley commented on SOLR-17115:
-------------------------------------
It'd be nice if there was a config similar to log4j2.xml where we could toggle
spans. I've thought it'd be an interesting hack to have our spans consult a
log4j level at some naming convention (wouldn't be class name) purely for the
sake of making a filtering decision, not to actually log a span via log4j.
This would have an advantage of existing config and dynamic/live toggle.
> OTEL: Option to skip certain spans from being exported
> ------------------------------------------------------
>
> Key: SOLR-17115
> URL: https://issues.apache.org/jira/browse/SOLR-17115
> Project: Solr
> Issue Type: Improvement
> Components: tracing
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Priority: Major
>
> Certain trace spans such as {{get:/admin/info/system}} and
> {{get:/admin/info/health}} are very frequent and not always helpful to have
> in Jaeger trace store. There is no native way to filter spans in OTEL Java
> SDK. This issue is to add a new ENV that will allow users to filter by span
> name. E.g.
> {code}
> SOLR_TRACE_SKIP_SPANS="get:/admin/info/health,get:/admin/info/system"
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
