ForkGroqGroqpublished Aug 13, 2025seen 5d

groq/opentelemetry-collector-contrib

forked from open-telemetry/opentelemetry-collector-contrib

Open original ↗

Captured source

source ↗
GH
GitHub/github.com/groq/opentelemetry-collector-contrib
groq/opentelemetry-collector-contrib repository metadata
Source ↗
published Aug 13, 2025seen 5dcaptured 14hhttp 200method plain

groq/opentelemetry-collector-contrib

Language: Go

License: Apache-2.0

Stars: 0

Forks: 0

Open issues: 5

Created: 2025-08-13T16:50:52Z

Pushed: 2026-03-31T16:19:28Z

Default branch: main

Fork: yes

Parent repository: open-telemetry/opentelemetry-collector-contrib

Archived: no

README: ---

Getting Started • Getting Involved • Getting In Touch

Vision • Observability • Security •

---

OpenTelemetry Collector Contrib

This is a repository for OpenTelemetry Collector components that are not suitable for the core repository of the collector.

The official distributions, core and contrib, are available as part of the opentelemetry-collector-releases repository. Some of the components in this repository are part of the "core" distribution, such as the Jaeger and Prometheus components, but most of the components here are only available as part of the "contrib" distribution. Users of the OpenTelemetry Collector are also encouraged to build their own custom distributions with the OpenTelemetry Collector Builder, using the components they need from the core repository, the contrib repository, and possibly third-party or internal repositories.

Each component has its own support levels, as defined in the following sections. For each signal that a component supports, there's a stability level, setting the right expectations. It is possible then that a component will be Stable for traces but Alpha for metrics and Development for logs.

Stability levels

Stability level for components in this repository follow the definitions from the OpenTelemetry Collector repository.

Gated features

Some features are hidden behind feature gates before they are part of the main code path for the component. Note that the feature gates themselves might be at different lifecycle stages.

Support

Each component is supported either by the community of OpenTelemetry Collector Contrib maintainers, as defined by the GitHub group @open-telemetry/collector-contrib-maintainer, or by specific vendors. See the individual README files for information about the specific components.

The OpenTelemetry Collector Contrib maintainers may at any time downgrade specific components if they are deemed unmaintained or if they pose a risk to the repository and/or binary distribution.

Even though the OpenTelemetry Collector Contrib maintainers are ultimately responsible for the components hosted here, actual support will likely be provided by individual contributors, typically a code owner for the specific component.

Contributing

See [CONTRIBUTING.md](CONTRIBUTING.md).

Maintainers

For more information about the maintainer role, see the community repository.

Approvers

For more information about the approver role, see the community repository.

Triagers

For more information about the triager role, see the community repository.

Emeritus Maintainers

For more information about the emeritus role, see the community repository.

Emeritus Approvers

For more information about the emeritus role, see the community repository.

Emeritus Triagers

Excerpt shown — open the source for the full document.

Notability

notability 1.0/10

Routine fork of observability repo