apache-exporter-iamguarded

packaged by Chainguard

Chainguard Container for apache-exporter-iamguarded

A Prometheus exporter for Apache HTTP server metrics.

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/apache-exporter-iamguarded:latest

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

Overview

apache-exporter-iamguarded is the IAMGuarded variant of Chainguard's apache-exporter image: a Prometheus exporter that scrapes Apache's mod_status endpoint and serves metrics on port 9117. It is laid out under /opt/iamguarded and runs as the nonroot 1001 user so it drops into the metrics side-car slot of the IAMGuarded application charts.

This exporter is not tied to a single chart. It is the shared Apache metrics side-car for the Apache-based IAMGuarded application charts, including apache, drupal, matomo, moodle, phpmyadmin, and wordpress. It ships as an image only (there is no standalone exporter chart) and is deployed by whichever parent application chart enables metrics.

Helm Chart Installation

The exporter is deployed as a side-car by a parent application chart, not on its own. The example below uses the Moodle chart, but the same metrics.* values apply to any of the Apache-based charts listed above. Charts are delivered through the same OCI registry as your Chainguard images:

cgr.dev/$ORGANIZATION/iamguarded-charts/moodle

Basic Installation

Metrics are disabled by default; enable them at install time. Once authenticated (see below):

helm install moodle oci://cgr.dev/$ORGANIZATION/iamguarded-charts/moodle \
  --set "global.org=$ORGANIZATION" \
  --set "metrics.enabled=true"

Important: Replace $ORGANIZATION with your Chainguard organization name. The default organization in the chart values is chainguard-private, which must be changed to match your organization.

Configuration Requirements

Organization Setting

The global.org value is required and can be set either:

• Via --set flag during installation
• In your existing values.yaml file

Registry Configuration

Images resolve from the Chainguard Registry (cgr.dev) under your organization. Use global.imageRegistry and global.org to point the chart at your organization's images, and set per-image registry/repository/digest when you need to pin an individual image.

The exporter image is configured under the chart's metrics.image key. Example values.yaml pinning the exporter image (this image) alongside the main application image to the Chainguard Registry:

# Main application image (e.g. Moodle)
image:
  registry: cgr.dev
  repository: $ORGANIZATION/moodle-iamguarded
  digest: sha256:... # Pin to a specific digest instead of a tag

# Apache metrics exporter (this image)
metrics:
  enabled: true
  image:
    registry: cgr.dev
    repository: $ORGANIZATION/apache-exporter-iamguarded
    digest: sha256:... # Pin to a specific digest instead of a tag

Replace $ORGANIZATION with your Chainguard organization name.

Authentication

For detailed instructions on configuring authentication and pull credentials for iamguarded images, please refer to our comprehensive guide:

How to Use Chainguard Helm Charts

Best Practices

1. Pin to Digest: While charts follow the same tagging scheme as Chainguard images, always pin to a specific chart digest to prevent unexpected updates:

   helm install moodle oci://cgr.dev/$ORGANIZATION/iamguarded-charts/moodle@sha256:DIGEST \
     --set "global.org=$ORGANIZATION" \
     --set "metrics.enabled=true"

   The digest can be found in the output of helm pull e.g:

   helm pull oci://cgr.dev/$ORGANIZATION/iamguarded-charts/moodle
   Pulled: cgr.dev/ORGANIZATION/iamguarded-charts/moodle:x.y.z
   Digest: sha256:6471bd888adc895c4c8d259fd72ae7d165da585208bf5670228319c8c0872a49

   Digest value for illustrative purposes only.

2. Review Default Values: The chart provides security-minded defaults that are sensible but may not be production-ready for all use cases. Review the chart's values.yaml (run helm show values) for the full range of configuration options.

3. Image Pinning: All IAMGuarded charts pin images to specific digests that have been tested for compatibility, ensuring reliable deployments.

Validation

After deployment with metrics enabled, confirm the side-car is scraping Apache by checking that the exporter's metrics endpoint (default port 9117) reports apache_up 1 along with the standard apache_* metrics. A working Prometheus or Prometheus Operator install is needed to collect them; for Prometheus Operator, set metrics.serviceMonitor.enabled=true.

Documentation and Resources

• apache_exporter upstream project
• Apache dashboard for Grafana

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system 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 development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

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.