GitHub user eanikindfi added a comment to the discussion: Invalid metric values for completed tasks task.cpu_usage_percent/task.mem_usage_percent
Thank you guys for quick answers! So right now we have 2 ways for solving it basically: - Go to `open-telemetry` solution rather than `statsd`; - Fulfill our monitorings with additional rules to compare live metrics from Airflow with an actual state of the task/dag. Questions: - @potiuk, Do you have a successful test-cases of this problem with `open-telemetry`? We have small knowledge of this component, so it would be awesome if you share your experience before we go there blindly. How `Airflow >> open-telemetry` stack works with mentioned metrics?; - Is it possible to "mark" status of the `statsd` solution as not preferable in the documentation of Airflow? Based on this discussion. - @potiuk @ferruzzi, If we try to compare resource-usage and states — any suggestions what metric we can use to check the actual state of the task? GitHub link: https://github.com/apache/airflow/discussions/43460#discussioncomment-11094677 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
