KUBERNETES ANNOTATIONS SERIES

Enabled log collection so you can search, analyze, and monitor all the logs from your cluster.

Learned how Autodiscovery enables you to automatically monitor your containerized workloads, wherever in the cluster they are running.Deployed kube-state-metrics to gain additional visibility into cluster-level status.

KUBERNETES ANNOTATIONS SERIES

Deployed the Datadog Agent to collect all the metrics highlighted in Part 2 of this series.

After following along with this post, you will have:

In this post we’ll show you how you can get more comprehensive visibility into your cluster by collecting all your telemetry data in one place and tracking it over time. If you’ve read Part 3 of this series, you’ve learned how you can use different Kubernetes commands and add-ons to spot-check the health and resource usage of KubernetesĬluster objects. It now uses “main” instead for new repos, and GitHub is advising users to wait for upcoming changes that will allow us to safely rename the “master” branch in our existing repositories. Editor’s note: Several URLs in this post contain the term “master.” Datadog does not use this term, but GitHub historically used “master” as the default name for the main branch of a repository.

Kubernetes annotations