Automated Kubernetes logging

You can use automated logging to route Kubernetes data through Chronosphere Telemetry Pipeline. Automated logging pulls logs from services running inside the Kubernetes cluster where you deployed a Core Instance, then sends those logs to one or more destinations.

Enable automated logging

To enable automated logging in Telemetry Pipeline:

1. Sign in to the Telemetry Pipeline web interface (opens in a new tab).
2. Go to Core Instances, then click the name of the Core Instance where you'd like to set up automated logging.
3. Next to Kubernetes Namespaces, click the  icon, then click Automate logging.
4. In the dialog that appears, select one of the available destinations to determine where your logs will be sent.
5. Configure the settings for your chosen destination plugin, then click Save.

Modify automated logging settings

After you've set up automated logging, you can add additional destinations to your Core Instance or adjust the settings for any existing destinations. To modify automated logging settings in Telemetry Pipeline:

1. Sign in to the Telemetry Pipeline web interface (opens in a new tab).
2. Go to Core Instances, then click the name of the Core Instance whose automated logging settings you'd like to modify.
3. Under Kubernetes Namespaces, click any item in the Destinations list. This opens the pipeline builder.
4. Use the pipeline builder to modify your Kubernetes sources, destination plugins, or processing rules.

Disable automated logging

To disable automated logging in Telemetry Pipeline:

1. Sign in to the Telemetry Pipeline web interface (opens in a new tab).
2. Go to Core Instances, then click the name of the Core Instance where you'd like to disable automated logging.
3. Next to Kubernetes Namespaces, click Disable .