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

ASF GitHub Bot updated HDDS-17581:
----------------------------------
    Labels: pull-request-available  (was: )

> Add TracingUtil span helpers and span-kind aware tracing proxies
> ----------------------------------------------------------------
>
>                 Key: HDDS-17581
>                 URL: https://issues.apache.org/jira/browse/HDDS-17581
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Sravani Revuri
>            Assignee: rajesh
>            Priority: Major
>              Labels: pull-request-available
>
> h3. Problem
> The OM, SCM and datanode tracing work (HDDS-17586, HDDS-17593, HDDS-17594) 
> will wrap internal service components in tracing proxies and add attributes 
> and errors to spans. The current \{{hdds-common}} tracing utilities don't 
> support this:
> * Proxies can't wrap components created at service startup.
> * Proxy spans are always CLIENT and are named after the interface, not the 
> implementation class.
> * Failed spans get only an ERROR status, without the exception or message.
> * There are no shared helpers for span attributes, events and exceptions, and 
> no test helper to assert on spans.
> h3. Proposal
> Extend \{{TracingUtil}} and \{{TraceAllMethod}} with:
> * A tracing proxy that can be created at startup, takes a span kind, and 
> names spans \{{<implementation class>.<method>}}.
> * Separate INTERNAL and CLIENT proxy helpers. Existing RPC client proxies 
> keep CLIENT spans.
> * Standard exception recording on proxy spans, \{{executeInSpan}} and the 
> protocol message dispatcher.
> * Null-safe helpers for span attributes, events and exceptions, plus a test 
> span collector.
> Only \{{hdds-common}} changes; no new service spans. No proto, RPC, 
> configuration or storage changes.
> This blocks HDDS-17586, HDDS-17593 and HDDS-17594.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to