[
https://issues.apache.org/jira/browse/IMPALA-13237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013453#comment-18013453
]
ASF subversion and git services commented on IMPALA-13237:
----------------------------------------------------------
Commit 2ad6f818a5a3f8bdc0f19be29760cc22f9f4c18a in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2ad6f818a ]
IMPALA-13237: [Patch 5] - Implement OpenTelemetry Traces for Select Queries
Tracking
Adds representation of Impala select queries using OpenTelemetry
traces.
Each Impala query is represented as its own individual OpenTelemetry
trace. The one exception is retried queries which will have an
individual trace for each attempt. These traces consist of a root span
and several child spans. Each child span has the root as its parent.
No child span has another child span as its parent. Each child span
represents one high-level query lifecycle stage. Each child span also
has span attributes that further describe the state of the query.
Child spans:
1. Init
2. Submitted
3. Planning
4. Admission Control
5. Query Execution
6. Close
Each child span contains a mix of universal attributes (available on
all spans) and query phase specific attributes. For example, the
"ErrorMsg" attribute, present on all child spans, is the error
message (if any) at the end of that particular query phase. One
example of a child span specific attribute is "QueryType" on the
Planning span. Since query type is first determined during query
planning, the "QueryType" attribute is present on the Planning span
and has a value of "QUERY" (since only selects are supported).
Since queries can run for lengthy periods of time, the Init span
communicates the beginning of a query along with global query
attributes. For example, span attributes include query id, session
id, sql, user, etc.
Once the query has closed, the root span is closed.
Testing accomplished with new custom cluster tests.
Generated-by: Github Copilot (GPT-4.1, Claude Sonnet 3.7)
Change-Id: Ie40b5cd33274df13f3005bf7a704299ebfff8a5b
Reviewed-on: http://gerrit.cloudera.org:8080/22924
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Send Query Lifecycle Traces to OTel
> -----------------------------------
>
> Key: IMPALA-13237
> URL: https://issues.apache.org/jira/browse/IMPALA-13237
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend, Frontend
> Reporter: Jason Fehr
> Assignee: Jason Fehr
> Priority: Critical
> Labels: observability
>
> Throughout the lifecycle of a query, several events happen. Implement OTel
> traces where each span is one step in the query lifecycle.
> These traces will be send to OTel systems using the OTel SDK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
