Logentries should not overload task definition

[k2nr]

Currently Lognetreis plugin 2 things

• Add rsyslog configuration on host to send rsyslog logs to Logentries
• Overwrite all task definitions' log configurations so that docker containers send logs to localhost:514 (rsyslogd)

This way, container logs do not go to CloudWatch Logs but Logentries directly. Since we use this plugin, we can't add new logging features based on CloudWatch Logs e.g. bcn logs [something]

So I propose to rewrite logentries plugin as follows

• all logs go to CloudWatch Logs (this is the default behavior of Barcelona)
• Logentries plugin adds a Lambda function that get logs from CloudWatch Logs and send them to Logentries

[k2nr]

• plugin stores Logentries API key
• The lambda function creates a log set for each heritage if not exist
• The lambda function creates a log for each service if not exist
• The lambda function get log token on first cold start

[k2nr]

Firelens has been released https://aws.amazon.com/jp/about-aws/whats-new/2019/11/aws-launches-firelens-log-router-for-amazon-ecs-and-aws-fargate/ This is basically Amazon-manged fluentd solution. Instead of writing log forwarder based on CloudWatch Logs, we can just stream logs into Firelens and let users decide destinations.