Capture worker logs

Open
#318 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

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.

Description

type/bug

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
Dominant language
Rust
Stars
32
Forks
6
Avg merge
1d 6h
Merged PRs (30d)
12

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/airflow-operator

All issues in stackabletech/airflow-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.