After you complete the easy deployment process in Kubernetes Monitoring, you can further customize your configuration using the Helm chart. For example, you may want to collect more data, add more destinations, or need guidance on authentication settings.
The Application Observability feature encompasses receiving data via various receivers, processing that data, and delivering it to the specified destinations. This example shows the settings to collect telemetry data from an application.
Gather metrics about the Kubernetes Cluster and deliver them to a metrics destination. This includes using services and tools such as Node Exporter, kube-state-metrics, kubelet, and cadvisor.
Gather logs from the Nodes in your Kubernetes Cluster. This is useful when you create your own Kubernetes Cluster with kubeadm, because kubelet runs as a systemd service on Linux. This example shows gathering logs from the journald services.
Specify single or multiple destinations, whether a local service deployed on the same cluster, or a remote SaaS service. Use proxy URLs and TLS settings to send data to external services.
Use annotations to automatically discovered and gather metrics from Kubernetes Pods and Services. You can use these annotations to further customize by job, instance, path, port number or name, scheme, and scrape interval.
Enable Kubernetes Monitoring to work correctly on OpenShift Clusters.
Processing and labeling
After data collection during the processing phase, you can enable additional processing for telemetry data, refine the metrics you want to keep, and relabel or add labels.
For examples of labels and annotations during the discovery phase, refer to Discovery.
Private image registry
To support environments that are air gapped or should be excluded from using public image registries, override the container image registries for every subchart and use a private image registry.
Enable metric scraping to use a Write-Ahead Log (WAL) to store metrics in case of a scrape failure. Enable log gathering to use a volume to store log file positions. This provides a starting point for reading logs after a restart.