You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2021/06/03 15:25:00 UTC
[jira] [Resolved] (SOLR-15392) Improve Tracing operation names and
tags
[ https://issues.apache.org/jira/browse/SOLR-15392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley resolved SOLR-15392.
---------------------------------
Fix Version/s: main (9.0)
Resolution: Fixed
> Improve Tracing operation names and tags
> ----------------------------------------
>
> Key: SOLR-15392
> URL: https://issues.apache.org/jira/browse/SOLR-15392
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Assignee: David Smiley
> Priority: Major
> Fix For: main (9.0)
>
> Time Spent: 8h 20m
> Remaining Estimate: 0h
>
> The distributed tracing span "operation name" should be a low cardinality value, ideally not including host names or data set names or similar. Ideally it starts with a verb then has something else about what the verb is applied to. Examples:
> * {{get:/{core}/select}}
> * {{post:/{collection}/update}}
> * {{list:/admin/collections}}
> * {{create:/admin/cores}}
> The following [span tags|https://opentracing.io/specification/conventions/] could be populated:
> * {{db.type}} : "solr"
> * {{db.user}} : current authenticated user
> * {{db.instance}} : collection or core (whichever the request is addressed to)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org