[
https://issues.apache.org/jira/browse/HBASE-26363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Dimiduk resolved HBASE-26363.
----------------------------------
Fix Version/s: 3.0.0-alpha-2
2.5.0
Release Note: <!-- markdown -->Each HBase process can have its own
`service.name`, a value that can be completely customized by the operator. See
the comment and examples in conf/hbase-env.sh.
Resolution: Fixed
> OpenTelemetry configuration support for per-process service names
> -----------------------------------------------------------------
>
> Key: HBASE-26363
> URL: https://issues.apache.org/jira/browse/HBASE-26363
> Project: HBase
> Issue Type: Improvement
> Components: tracing
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Major
> Fix For: 2.5.0, 3.0.0-alpha-2
>
>
> Our configuration should support setting a different {{service.name}} for
> each identifiable HBase process/component. This will make it easier to
> distinguish between, say, master, region server, when visualizing a trace. As
> a first pass, I'm guessing that most of the command targets of {{bin/hbase}}
> should be represented by the configuration.
> For examples of how this might be implemented, see how we support per-process
> GC arguments, or how its done in this [Hadoop
> PR|https://github.com/apache/hadoop/pull/3445/files#diff-a6a286a42078a3fc5eed5bd1bf23163b3574a8f2246d7d8d2f81436b7603f1c2R436].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
