This page is not yet available in Spanish. We are working on its translation. If you have any questions or feedback about our current translation project, feel free to reach out to us!
Follow the instructions below to install and configure this check for an Agent running on a Kubernetes cluster. See also the Autodiscovery Integration Templates for guidance on applying these instructions.
Installation
Agent versions >=7.26.0 or >=6.26.0
To use an integration from integrations-extra with the Docker Agent, Datadog recommends building the Agent with the integration installed. Use the following Dockerfile to build an updated version of the Agent that includes the gatekeeper integration from integrations-extras:
FROM gcr.io/datadoghq/agent:latest
RUN agent integration install -r -t datadog-gatekeeper==<INTEGRATION_VERSION>
Agent versions <7.26.0 or <6.26.0
To install the gatekeeper check on your Kubernetes cluster:
Edit the gatekeeper/conf.yaml file, in the /confd folder that you added to the Agent pod to start collecting your gatekeeper performance data. See the sample gatekeeper/conf.yaml for all available configuration options.
The distribution of Mutator ingestion durations Shown as second
gatekeeper.mutators (gauge)
The current number of Mutator objects
gatekeeper.mutator.conflicting.count (gauge)
The current number of conflicting Mutator objects
Events
Gatekeeper does not include any events.
Service Checks
gatekeeper.prometheus.health Returns CRITICAL if the agent fails to connect to the Prometheus metrics endpoint, otherwise OK. Statuses: ok, critical
gatekeeper.health Returns CRITICAL if the agent fails to connect to the gatekeeper health endpoint, OK if it returns 200, WARNING otherwise. Statuses: ok, warning, critical