[
https://issues.apache.org/jira/browse/HDDS-14814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sravani Revuri updated HDDS-14814:
----------------------------------
Description:
Tracing for Freon randomkeys is currently fragmented and has the following
issues:
* Instead of a single trace for a command execution, multiple traces are being
created. Therefore breaking the parent-child hierarchy.
* The root span doesnt contain command name as it appears for ozone sh
commands.
*Proposed Changes:*
Proper handling of spans is required to ensure a chain of spans is created for
the same trace:
* If a trace is already active, the function call should join it as a span
(child).
* If no trace is active, it should start the initial trace (parent).
was:
Tracing for Freon is currently fragmented and has the following issues:
* Instead of a single trace for a command execution, multiple traces are being
created. Therefore breaking the parent-child hierarchy.
* The root span doesnt contain command name as it appears for ozone sh
commands.
*Proposed Changes:*
Proper handling of spans is required to ensure a chain of spans is created for
the same trace:
* If a trace is already active, the function call should join it as a span
(child).
* If no trace is active, it should start the initial trace (parent).
> Unify Fragmented Traces for Freon randomkeys Command
> ----------------------------------------------------
>
> Key: HDDS-14814
> URL: https://issues.apache.org/jira/browse/HDDS-14814
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sravani Revuri
> Assignee: Sravani Revuri
> Priority: Major
>
> Tracing for Freon randomkeys is currently fragmented and has the following
> issues:
> * Instead of a single trace for a command execution, multiple traces are
> being created. Therefore breaking the parent-child hierarchy.
> * The root span doesnt contain command name as it appears for ozone sh
> commands.
> *Proposed Changes:*
> Proper handling of spans is required to ensure a chain of spans is created
> for the same trace:
> * If a trace is already active, the function call should join it as a span
> (child).
> * If no trace is active, it should start the initial trace (parent).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
