Chainguard Container for metricbeat

Metricbeat fetches a set of metrics on a predefined interval from the operating system and services such as Apache web server, Redis, and more and ships them to Elasticsearch or Logstash.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/metricbeat:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The Chainguard Metricbeat Image is comparable to the official Metricbeat Image from Docker Hub. However, the Chainguard image does not run as the root user and contains only the minimum set of tools and dependencies needed to function. This means it doesn't include things like a package manager.

Getting Started

1. Metricbeat requires kube-state-metrics to be installed. Please refer to the following manifests provided by the upstream maintainers to deploy.

2. There are no actively supported helm charts for deploying metricbeat upstream. The most recent are present here and were archived in 2023. Manifest based deployments are offered as an alternative by the upstream maintainers here.

Note: Ensure to override the image properties to use the Chainguard provided image for metricbeat.

Note: You configure Metricbeat to write to a specific output by setting options in the Outputs section of the metricbeat.yml config file (Reference). In the manifests provided above, it can be done here.

Note: Make sure to change the image in the daemonset the Chainguard metricbeat Image.

3. The above manifests will bring metricbeat up in kube-system namespace. And you will be able to see metricbeat output in *.ndjson file in /usr/share/metricbeat/output directory in metricbeat pod.

Documentation and Resources

• Metricbeat official docs

What are Chainguard Containers?

Chainguard Containers are minimal container images that are secure by default.

In many cases, the Chainguard Containers tagged as :latest contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a -dev variant.

Although the -dev container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.

Learn More

To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.

In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.