connor_flynn
04/15/2022, 2:09 PMDEAULT_ARGS
to look as follows....
DEFAULT_ARGS = {
"owner": "airflow",
"depends_on_past": False,
"email": ['<mailto:connor@gmail.com|connor@gmail.com>'],
"email_on_failure": True,
"email_on_retry": False,
"catchup": False,
"retries": 1,
"retry_delay": timedelta(minutes=5),
"concurrency": 1,
}
I have tried to make these changes in the meltano.py
file under the path meltano-project/*orchestrate/dags/*
(As the code that automatically defines our meltano DAGs is in the file meltano.py
not airflow.cfg
) .
However after making these changes to the meltano.py
file, invoking meltano scheduler and manually trigger a DAG (which failed) I did not receive any emails to the address I defined (<mailto:connor@gmail.com|connor@gmail.com>
) !
If anyone has any guides or solutions to Airflow email alerting with meltano projects that would be greatly appricated!connor_flynn
04/15/2022, 5:55 PMairflow.cfg
file (under the path .meltano/run/airflow/
) but it appears to be removed at random periods and can only be regenerated by running meltano invoke airflow webserver -D
(and only after killing the current webserver's PID).
Is there a reason why the airflow.cfg
would be automatically removed after a certain time period?pat_nadolny
04/19/2022, 10:13 PMconnor_flynn
05/10/2022, 1:18 PMairflow.cfg
... We are having issues with our Airflow scheduler.
When running meltano invoke airflow scheduler -D
(in order to start the airflow scheduler in the background). Despite producing no errors (seen in screenshot) the Airflow Ui shows the "scheduler has no heartbeat".
I am trying to figure out how meltano creates the airflow.cfg
and how it would be removed with no pattern and how file this could effect the scheduler issues...If you have any suggestion that would be greatly appreciated!connor_flynn
05/10/2022, 1:18 PM