Open Taxuspt opened 5 years ago
After some more debugging, it seems that the EventManager
is never getting an after_update
event from DagRun
.
Were you able to fix it? I am facing the same issue.
Were you able to fix it? I am facing the same issue.
I spent quite some time looking for a fix without success. I think the problem comes from Flask and not from Airflow or airflow-metrics.
@Taxuspt Actually I moved back to the integrated airflow metrics (version 1.10.5) which covers most if not all of the metrics of this project. https://airflow.apache.org/metrics.html
I have the same issue.
I am also facing the same issue. did you able to fix it ?
@hatched-DavidMichon Hey, I've also ran into the same issue in this thread, so tried the integrated airflow metrics ~> Datadog instead, but am noticing that many of the metrics are missing there as well (primarily dag metrics). I have the datadog agent deployed in my cluster via helm and have configured my airflow.cfg per the docs. I noticed that if I have my "statsd_on = True", my webserver and scheduler start crashing. If I set to "False" and point my statsd host to the Datadog agent, I'll get a lot of metrics showing up in Datadog, but they'll disappear after a few minutes. I'm running airflow on k8s using k8s executer and k8s pod operator. I'm curious what your config looked like and if you're using Datadog? Thanks!
This patch is awesome and I now have Airflow running on Astronomer Cloud with datadog instrumentation. It works great!
Unfortunately I have the same issue here: the airflow.dag.duration
metric isn't collected. I'll let you know if I find a workaround.
I have set up
airflow-metrics
according to the documentation but I'm not receiving all the metrics on datadog.For reference, this is the list of metrics that datadog is receiving:
I have the following block on my
airflow.cfg
I tested it with both Local and Celery executors.
Here is a portion of the scheduler log when I manually schedule a dag
Any tips? Thanks