Kubernetes Events and Pod Logs Collection using LogicMonitor Collector
Last updated on 05 September, 2024Using LogicMonitor, you can send Kubernetes logs and events from a monitored Kubernetes cluster to our logs management service- LM Logs. In this article, we will see how to get started with transferring logs and events to LogicMonitor using your LM Container Helm chart.
Enabling Logs and Events Collection
Apply the following configuration using the Helm upgrade command. For more information on Kubernetes events and pod logs collection, see Sending Kubernetes Logs and Events.
1. Enable the following properties to start Pod and Kubernetes Events log collection:
argus:
lm:
lmlogs:
k8sevent:
enable: true
k8spodlog:
enable: trueNote:To view the Argus configuration file values, see the Default values on the Argus repository page.
2. Run the Helm upgrade to apply the configuration.
helm upgrade --install --debug --wait --create-namespace
--namespace=<your chosen namespace defaults to “logicmonitor”> -f
lm-container-configuration.yaml --version <chosen version criteria>
lm-container logicmonitor/lm-containerOptional Configurations
In addition to enabling logs and events collection, you can add optional collector configurations using an agent.conf customizations through LM Container Chart configuration.
For more information, see the Collecting and Forwarding Kubernetes Events.