Vincent

Hi @anneadb, in your logs example you are reading logs from the log group `airflow-my_env_name-Task` but in your DAG you specify `ecs-airflow` as log group. Did you check if in...

> 2024-05-31T06:06:13.230Z [2024-05-31T06:06:13.230+0000] {{ecs.py:573}} INFO - Starting ECS Task Log Fetcher > 2024-05-31T06:06:43.271Z [2024-05-31T06:06:43.271+0000] {{base.py:73}} INFO - Using connection ID 'aws_12345678910' for task execution. I see. I can see that...

Hey @anneadb, I cannot reproduce the issue. When I run the same DAG as the one in the description, I get the logs in real time in my cloudwatch log...

``` [2024-06-03, 21:20:21 UTC] {ecs.py:638} INFO - ECS Task started: {'tasks': [{'attachments': [{'id': '0fbe5b10-140f-4f0e-a784-d2926a536039', 'type': 'ElasticNetworkInterface', 'status': 'PRECREATED', 'details': [{'name': 'subnetId', 'value': 'subnet-03fe35179d25a0036'}]}], 'attributes': [{'name': 'ecs.cpu-architecture', 'value': 'x86_64'}], 'availabilityZone': 'us-east-1b',...

I am using Breeze so I guess I have the default configuration. But it should not even matter because I am looking at logs inside the log group I specified...

> This is good. However, isn't it good idea to capture the utilization metrics of the entire pod (including sidecar containers) instead of just the base container? It seems very...

> Very cool! Left some comments. > > Also is it possible to unit test this? The only way I could find to unit test it is to check we...

> > Very cool! Left some comments. > > Also is it possible to unit test this? > > The only way I could find to unit test it is...

Any more concerns/comments?

@Taragolis