Container logging configuration

By default all logs that are published to ECS are pushed to Cloudwatch and are kept for 7 days. This includes native docker logs and customer logs if they are written to stdout/stderr. Logs that are written to the file system within a container are not registered by any root360 solution. In this case the customer has to take care of rotating them himself.

Cloudwatch access will be provided by root360 in the form of AWS Console login credentials (usually called devops user). 

Advanced Logging Kibana

On request root360 provides other log setups that might suit customer needs better than the default setup.

Elasticsearch + Kibana

As a platform solution root360 provides an Elasticsearch + Kibana logging setup (additional fees apply). In order to ship the logs to Elasticsearch we use Filebeat, which will run on all container instances.

We consider the Filebeat-container as a customer container. It is therefore counted as a service within your cluster. The configuration of Filebeat is done via ENV variables that the customer can define if he wishes to.

The Elasticsearch cluster will only be available within the dedicated VPC of the container environment. Outside access is only possible through an SSH tunnel.

See Advanced Logging Kibana (root360)

General Definitions

The following definitions apply to all root360 platform solutions. In case your solution is not listed above you have a custom solution and some of the following might not apply.

Standard Logs

The following logs are aggregated by default:

• native docker logs

Customer Logs

Customer Logs are not collected by default unless they are written to stdout/stderr. This is valid for all root360 docker platform logging solutions.

Data retention

All log files that are under control of root360 through any of the above steps are stored for 7 days per container execution. After this retention period, the log files are deleted.

In case you need longer retention we will need the confirmation that you save customer data in consent with your customers according to GDPR (DSGVO). 

Related tutorials

Related components