3 Answers
- Newest
- Most votes
- Most comments
5
You may try this:
- Use Environment Variables Instead of airflow.cfg MWAA prefers environment variables for config overrides. Try setting:
AIRFLOW__METRICS__METRICS_BLOCK_LIST=^.*$
AIRFLOW__METRICS__METRICS_USE_PATTERN_MATCH=true
Add these as custom environment variables in the MWAA console. 2. Double-Check MWAA Version Compatibility Some metrics settings are only supported in Airflow 2.3+. Confirm your MWAA environment is running a compatible version. 3. Restart the Environment After applying config changes, restart the MWAA environment to ensure they take effect. 4. Verify with CloudWatch Logs Check the MWAA logs in CloudWatch to confirm whether metrics are still being emitted. Sometimes metrics are cached or delayed.
0
Hi, thank you for the answer
- where can i set environment variables explicitly? afaik the environment config (e.g. in the porlta) is converted to environment variables. Thats what i am doing.
- Version 2.10, so this should be fine
- Restart was done
- Metrics are still there
So in general you say the config itself should be fine?
answered a year ago
Relevant content
asked 4 years ago
asked 5 years ago
- AWS OFFICIALUpdated 7 months ago
