Last changed
Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.
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.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
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:
splunk-otel-collector-fips
features a stripped down, minimal designMost importantly, the splunk-otel-collector-fips
image contains the OpenSSL FIPS Provider Module (CMVP #4282).
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.
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.
The following is an example otel-collector.yaml
configuration file:
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:
Ensure that the container is up and running and ensure that the metric counts have been ingested by the collector
The test above is to validate that metrics, in the case from a redis container are been collected by the otel collector service.
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.
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.
Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.
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.
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 agreementThis 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