Enable Logging for Baffle Manager and Baffle Shield Containers

This document demonstrates how to use stdout (standard output) to enable logging for Baffle Manager and Baffle Shield containers.

Prerequisites

You must have deployed Baffle Manager and Baffle Shield in an orchestrated container environment.

Enabling Logging for Containers

This section walks through the process of enabling logging for a container deployment.

All log containers are located in /var/log/containers. This path can be specified as an event collection point for your logging solution. 

The Baffle Manager deployment consists of the following containers:

  • baffle-manager
  • baffle-web
  • baffle-nginx
  • baffle-mongodb

The Baffle Shield container will be the name specified in the Baffle Shield application properties file.

To enable logging in a container environment, do the following:

  1. Log in to your container environment and use the following command to verify the running pods.
    kubectl get pods
  2. Use the following command to retrieve logs for the baffle-manager-container.
    kubectl logs -f baffle-manager-...
  3. To retrieve logs for other containers, specify the container name and use the logs -f parameter.
    kubectl logs -f <container-name>...

Fluentd Log Collection for AWS deployments

Baffle Manager and Baffle Shield deployments with Amazon Elastic Kubernetes Service and/or Amazon Elastic Container Service can configure Fluentd to collect event logs from containers.

For more information, see the following Amazon AWS documentation.

In the fluentd.yaml file section for logging, you can specify the path /var/log/containers/* as shown in the following example.

fluentd_yaml-file.png

 

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.