You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the scheduler container, we host multiple Airflow subprocesses, namely the scheduler, the DAG processor, and the triggerer. We need to generate per-subprocess metrics so we know when/if some processeses start others.
Acceptance Criteria
For each sub-process, generate CPU and memory metrics.
This should be as automated as possible, so any time we create multiple sub-processes in a single container, it is easy or no-effort to generate metrics for all sub-processes.
Hi @shubham22, hope you don't mind me tagging you, I saw you suggested this change here. Is there a prediction on when something like this would be implemented?
My team is looking for a workaround to have better monitoring on Task-level and DAG-level metrics like CPU/Memory for debugging purposes in MWAA, and we wouldn't have to go down that route if there were any plans to pick this up in the near future.
Overview
In the scheduler container, we host multiple Airflow subprocesses, namely the scheduler, the DAG processor, and the triggerer. We need to generate per-subprocess metrics so we know when/if some processeses start others.
Acceptance Criteria
Additional Info
Context on this: #59 (comment)
The text was updated successfully, but these errors were encountered: