prometheus-json-exporter-fips

Chainguard Container for prometheus-json-exporter-fips

FIPS-compliant Wolfi-based Prometheus JSON Exporter image for scraping remote JSON by JSONPath.

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/prometheus-json-exporter-fips: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 prometheus-json-exporter-fips image is comparable to prometheuscommunity/json-exporter, with the following differences:

• Built on Wolfi with a minimal footprint and fewer CVEs
• Does not run as root by default

FIPS Support

Chainguard's prometheus-json-exporter-fips container image ships with a validated redistribution of the OpenSSL FIPS provider module. For more on FIPS support in Chainguard container images, consult the guide on FIPS-enabled Chainguard Containers on Chainguard Academy.

Getting Started

The Prometheus JSON Exporter can be deployed using the official Helm chart from the prometheus-community repository.

First, add the Helm repository:

helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
helm repo update

Create a values.yaml file with the Chainguard FIPS image:

cat > values.yaml <<EOF
image:
  repository: cgr.dev/ORGANIZATION/prometheus-json-exporter-fips
  tag: latest

EOF

Replace ORGANIZATION with your Chainguard organization name, then install the chart:

helm install prometheus-json-exporter prometheus-community/prometheus-json-exporter -f values.yaml

Once deployed, the exporter exposes metrics at /metrics and can scrape JSON endpoints via the /probe endpoint:

kubectl port-forward svc/prometheus-json-exporter 7979:7979 &
curl http://localhost:7979/metrics

To scrape a remote JSON endpoint:

curl 'http://localhost:7979/probe?module=default&target=http://example.com/api/metrics.json'

Configuration

Configure Prometheus to scrape targets through the JSON exporter by adding the following to your Prometheus configuration:

scrape_configs:
  - job_name: 'json_exporter'
    metrics_path: /probe
    params:
      module: [default]
    static_configs:
      - targets:
        - http://example.com/api/metrics.json
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: prometheus-json-exporter:7979

For a complete list of Helm chart configuration options:

helm show values prometheus-community/prometheus-json-exporter

Documentation and Resources

• Prometheus JSON Exporter GitHub Repository
• FIPS-enabled Chainguard Containers
• Chainguard Academy

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.