jmx-exporter-iamguarded

Chainguard Container for jmx-exporter-iamguarded

jmx-exporter-iamguarded image is a Prometheus metrics exporter for JMX (Java Management Extensions), enabling monitoring and observability for Java applications used by IAMguarded helm charts.

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/jmx-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

JMX Exporter IAMGuarded is a Prometheus metrics exporter for JMX (Java Management Extensions), designed to export metrics from Java applications. This security-enhanced variant is used as a metrics sidecar component in IAMGuarded Helm charts for Java-based applications that expose JMX metrics.

JMX Exporter runs as an HTTP server and exposes Java runtime and application metrics in Prometheus format, enabling monitoring and observability for Java applications deployed in Kubernetes.

Helm Chart Usage

The JMX Exporter IAMGuarded image does not have its own dedicated Helm chart. Instead, it is deployed as a metrics sidecar container in IAMGuarded Helm charts for Java applications that expose JMX metrics.

Kafka IAMGuarded Chart

The most common usage is with the Kafka IAMGuarded Helm chart, delivered through the same OCI registry as your Chainguard images:

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

Installation with JMX Metrics Enabled

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

Important: Replace $ORGANIZATION with your Chainguard organization name. JMX metrics are typically disabled by default and must be explicitly enabled.

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

For users who mirror images to custom repositories, configure the JMX Exporter image in your values.yaml:

metrics:
  jmx:
    enabled: true
    image:
      registry: myregistry.example.com
      repository: mirrored/jmx-exporter-iamguarded
      digest: sha256:... # Use specific digest instead of tag

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: When using custom registries, always pin to specific image digests for reliable deployments.

2. Enable Metrics Explicitly: JMX metrics collection is typically opt-in. Review the chart's values.yaml to enable and configure the metrics endpoint.

3. Configure JMX Rules: The exporter uses configuration files to define which JMX metrics to expose. Consult the chart's documentation for customizing JMX scraping rules.

Validation

After deployment with JMX metrics enabled, validate the exporter by checking that metrics are exposed on the configured port (typically 5556). You can verify metrics collection by:

1. Port-forwarding to the metrics pod:

   kubectl port-forward <pod-name> 5556:5556

2. Accessing the metrics endpoint:

   curl http://localhost:5556/metrics

3. Confirming Prometheus is scraping the JMX metrics (if Prometheus integration is configured).

Other Compatible Charts

While Kafka is the primary use case, this image can be used with any IAMGuarded Helm chart for Java applications that support JMX metrics collection. Consult individual chart documentation for specific configuration requirements.

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.