You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/07 20:57:00 UTC

[jira] [Updated] (HBASE-27182) Rework tracing configuration

     [ https://issues.apache.org/jira/browse/HBASE-27182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell updated HBASE-27182:
----------------------------------------
    Fix Version/s: 2.5.0
                   3.0.0-alpha-4
           Status: Patch Available  (was: Open)

> Rework tracing configuration
> ----------------------------
>
>                 Key: HBASE-27182
>                 URL: https://issues.apache.org/jira/browse/HBASE-27182
>             Project: HBase
>          Issue Type: Task
>          Components: scripts
>    Affects Versions: 3.0.0-alpha-3, 2.5.0, 2.6.0
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>             Fix For: 2.5.0, 3.0.0-alpha-4
>
>
> I'd like to make some adjustments to how we manage tracing configuration in `conf/hbase-env.sh`. I'd like to take advantage of the fact that OpenTelemetry can read its configuration from environment variables and make use of this where possible, only falling back to passing properties into the process launch configuration when it's necessary. I think this will DRY up tracing configuration and make it easier to manage in a container environment.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)