[GitHub] [airflow] nkumar15 edited a comment on issue #9486: ECSOperator failed to display logs from Cloudwatch after providing log configurations

[GitBox <gi...@apache.org>]

nkumar15 edited a comment on issue #9486:
URL: https://github.com/apache/airflow/issues/9486#issuecomment-808065297


   Thanks @amirhmk for your response.
   Not sure what I am doing wrong.
   
   in cloud watch I see log entries
   log group as /ecs/hello-world
   logstream as /ecs/hello-world/<unique uuid value>
   
   in ecs fargate
   my task name and container name are both hello-world
   and container log configuration is
   
   awslogs-group = /ecs/hello-world
   awslogs-region =ap-southeast-1
   awslogs-stream-prefix = ecs
   
   
   and in airflowecsoperator
    task_id="hello-world"
   awslogs_group="/ecs/hello-world"
   
   I tried with 
   
   awslogs_stream_prefix="/ecs/hello-world"                      -->existing prefix which I can see in cloudwatch
   awslogs_stream_prefix="/hello-world/hello-world"         --> task-name/containername
   
   but in both cases its not working with error
   botocore.errorfactory.ResourceNotFoundException: An error occurred (ResourceNotFoundException) when calling the GetLogEvents operation: The specified log stream does not exist.
   
   Sorry, I understand I am asking too specific here, however just hoping in case anybody can help.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org