apache / apache/datafusion-ballista

Support trace id for each query

Open
#85 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Rust
Stars
2.1k
Forks
320
Avg merge
1d 11h
Merged PRs (30d)
86

Description

**Is your feature request related to a problem or challenge? Please describe what you are trying to do.**
As a distributed query engine, many sql query will submit to the scheduler, and the scheduler or executor server will log some message for each query.

But from current status, we can't find out the logs corresponding to the specified query, we should search all the log and find the useful information for our query.

If we have the trace id or the query id, we can log the trace id or query in the `log event format`, just like
`[time trace id code paht] : log info`.

From above format, we can find out all of query log for the specified query.

@andygrove @alamb

Do you have other ideas?

**Describe the solution you'd like**
A clear and concise description of what you want to happen.

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how queries are submitted to the scheduler and executor servers and where their log events are emitted. Define how a trace ID or query ID should flow through that path, then verify that the log event format lets operators find all logs for one query.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, sql
Domain
distributed-systems, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.