stackabletech / stackabletech/airflow-operator
Capture worker logs
Open
Nobody has claimed this yet.
type/bug
- Dominant language
- Rust
- Stars
- 32
- Forks
- 6
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
As a user I want to have worker log output persisted by vector.
In contrast to the webserver/scheduler logs, the worker logs are persisted in a per-task-per-run-per-attempt basis here, and as such are not processed by vector.toml:
/stackable/airflow/logs/dag_id\=example_bash_operator/run_id\=manual__2023-08-16T07\:41\:06.903462+00\:00/task_id\=run_after_loop/attempt\=1.log
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the worker log path described in the issue with the existing webserver and scheduler handling in vector.toml. Determine how per-task, per-run, per-attempt worker logs should be processed, and verify that the resulting logs are persisted by Vector without disrupting the existing log handling.
Written by the indexing model from the issue text.
Assessment
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100