Datadog-controller Helm Chart

Datadog-controller
Analyzed version: 1.0.0

By Delivery Hero

This is a simple [Kubernetes Controller](https://kubernetes.io/docs/concepts/architecture/controller/) to allow [Datadog Monitors](https://docs.datadoghq.com/monitors/) to be created, updated or deleted from custom resources in Kubernetes. You will need to set `datadog.client_api_key` and `datadog.client_app_key` when installing the chart. These keys can be found at https://app.datadoghq.eu/account/settings#api or https://app.datadoghq.com/account/settings#api Here's an example `DatadogMonitor` resource: ```yaml apiVersion: datadoghq.com/v1beta1 kind: DatadogMonitor metadata: name: apm-error-rate-example spec: name: my-service error rate query: "avg(last_5m):sum:trace.http.request.errors{env:stg,service:my-service} / sum:trace.http.request.hits{env:stg,service:my-service} > 1" type: "query alert" message: Service my-service has a high error rate on env:stg ```

Prometheus, a CNCF project, is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true.

This chart bootstraps a Prometheus deployment on a Kubernetes cluster using the Helm package manager.

Latest version: 15.5.3
View GitHub

How to Install the Datadog-controller Helm Chart

Add Chart Repository to Helm

helm repo add deliveryhero https://charts.deliveryhero.io/

Install Chart

helm install my-datadog-controller deliveryhero/datadog-controller --version 1.0.0

Does the Datadog-controller Chart Follow Industry Best Practices?

The chart meets the best practices recommended by the industry.

The chart failed to meet 2 of the best practices recommended by the industry.

The chart meets the best practices recommended by the industry. Find the full list of best practices here.

❌ Ensure each container has a configured readiness probe

1 occurrences:

  • metadata.name: release-name-datadog-controller (kind: Deployment)

💡 Missing property object `readinessProbe` - add a properly configured readinessProbe to notify kubelet your Pods are ready for traffic

Learn how to fix the issue here

❌ Ensure each container has a configured liveness probe

1 occurrences:

  • metadata.name: release-name-datadog-controller (kind: Deployment)

💡 Missing property object `livenessProbe` - add a properly configured livenessProbe to catch possible deadlocks

Learn how to fix the issue here

This is some text inside of a div block.
This is some text inside of a div block.

Reveal misconfigurations within minutes

3 Quick Steps to Get Started