/
DirectorySecurity AdvisoriesPricing
Sign in
Directory
splunk-otel-collector-fips logoFIPS

splunk-otel-collector-fips

Last changed

Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for REPO_NAME

Splunk OpenTelemetry Collector is a distribution of the OpenTelemetry Collector. It provides a unified way to receive, process, and export metric, trace, and log data for Splunk Observability Cloud

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/REPO_NAME:latest

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

Compatibility Notes

splunk-otel-collector-fips is built using this guide https://github.com/signalfx/splunk-otel-collector/blob/main/cmd/otelcol/fips/Dockerfile as reference to ensure compatiblity with projects running this version of the application as a docker image, with the following differences:

  • Like all other Chainguard Images, splunk-otel-collector-fips features a stripped down, minimal design
  • This base image comes with apk and BusyBox and reports as being a Chainguard image.
  • It has few-to-zero CVEs
  • It does not run as the root user

Most importantly, the splunk-otel-collector-fips image contains the OpenSSL FIPS Provider Module (CMVP #4282).

About FIPS Images

FIPS (short for Federal Information Processing Standards) are standards developed by the National Institute of Standards and Technology (NIST) in accordance with the Federal Information Security Management Act (FISMA) and approved by the Secretary of Commerce. FIPS compliance ensures that cryptographic security services within applications meet strict security and integrity standards, and are implemented and configured correctly.

Chainguard offers a variety of language-specific FIPS Images configured out of the box for FIPS development in a given language. We also offer a number base FIPS images for specific applications, such as PostgreSQL, Elasticsearch, and nginx.

Be aware that if you run apk add to install a package onto a Chainguard FIPS Image, there's no guarantee that these packages will function properly; they may throw errors if the package has certain dependencies that aren't available in the image. Additionally, even if they do function properly there's no guarantee that added packages will use FIPS-validated cryptography.

Please refer to Chainguard's FIPS Commitment for more information.

Getting Started

Splunk OpenTelemetry Collector is a distribution of the OpenTelemetry Collector. It provides a unified way to receive, process, and export metric, trace, and log data for Splunk Observability Cloud. Here is an example setup of the collector to ingest metrics from a Redis server.

Requirements

  1. Configuration for the OpenTelemetry Collector deployed with a configMap
  2. Configuration for the Redis server deployed with a configMap

The following is an example otel-collector.yaml configuration file:

apiVersion: v1
kind: ConfigMap
metadata:
  name: otel-config
  namespace: splunk
data:
  otel-collector-config.yaml: |
    receivers:
      redis:
        endpoint: "localhost:6379"
        collection_interval: 10s
        password: $REDIS_PASSWORD
        metrics:
          redis.role:
            enabled: true
          redis.cmd.calls:
            enabled: true
    extensions:
      health_check:
        endpoint: 0.0.0.0:13133
      zpages:
        endpoint: 0.0.0.0:55679
    processors:
      batch:
    exporters:
      signalfx:
        access_token: "token"
        realm: "us0"
      debug:
        verbosity: detailed
    service:
      telemetry:
        metrics:
          address: ":8888"
      pipelines:
        metrics/sfx:
          receivers: [redis]
          processors: [batch]
          exporters: [signalfx]
        metrics/logging:
          receivers: [redis]
          processors: [batch]
          exporters: [debug]

More information can be found in the Otel collector examples folder.

To test out this image, deploy an otel-collector pod in a Kubernetes cluster:

apiVersion: v1
kind: Pod
metadata:
  name: redis-otel-pod
  namespace: splunk
spec:
  serviceAccount: default
  containers:
    - name: redis-db
      image: redis:latest
      command: ["redis-server", "/etc/redis/redis.conf"]
      ports:
        - containerPort: 6379
        - containerPort: 6329
      volumeMounts:
        - name: redis-config
          mountPath: /etc/redis/redis.conf
          subPath: redis.conf

    - name: otelcollector
      image: ${local.parsed.registry}/${local.parsed.repo}:${local.parsed.pseudo_tag}
      args:
        - "--config=/etc/otel-collector-config.yaml"
        - "--set=service.telemetry.logs.level=debug"
      env:
        - name: SPLUNK_ACCESS_TOKEN
          value: "token"
        - name: SPLUNK_REALM
          value: "us0"
        - name: REDIS_PASSWORD
          value: "changeme"
      ports:
        - containerPort: 8088
          name: otel-http
        - containerPort: 8888
          name: otel-grpc
      volumeMounts:
        - name: otel-config
          mountPath: /etc/otel-collector-config.yaml
          subPath: otel-collector-config.yaml

  volumes:
    - name: otel-config
      configMap:
        name: otel-config
    - name: redis-config
      configMap:
        name: otel-config

Ensure that the container is up and running and ensure that the metric counts have been ingested by the collector

kubectl -n splunk logs redis-otel-pod -c otelcollector 2>&1 | \
  grep "Metrics" | head -n 1 | jq -R 'split(",") | \
  map(select(contains("\"metrics\":"))) | map(split(": ")[1] | tonumber) | .[0] > 10'

The test above is to validate that metrics, in the case from a redis container are been collected by the otel collector service.

Documentation and Resources

  1. https://github.com/signalfx/splunk-otel-collector - Main project repository
  2. https://github.com/signalfx/splunk-otel-collector/tree/main/examples - Deployment scenarios
  3. https://github.com/signalfx/splunk-otel-collector-chart - Helm chart
  4. https://docs.splunk.com/observability/en/gdi/opentelemetry/opentelemetry.html

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:

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.

Licenses

Chainguard container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:

  • AFL-2.1

  • Apache-2.0

  • BSD-1-Clause

  • BSD-2-Clause

  • BSD-3-Clause

  • BSD-4-Clause-UC

  • CC-PDDC

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

This is a FIPS validated image for FedRAMP compliance.

This image is STIG hardened and scanned against the DISA General Purpose Operating System SRG with reports available.

Learn more about STIGsGet started with STIGs

Related images
splunk-otel-collector logo
splunk-otel-collector

Category
FIPS
STIG

Safe Source for Open Sourceâ„¢
Contact us
© 2025 Chainguard. All Rights Reserved.
Private PolicyTerms of Use

Product

Chainguard ContainersChainguard LibrariesChainguard VMsIntegrationsPricing