Alex Boten
Alex Boten
Unclear why these ended up here, removing them.
The security SIG is looking to ensure that security tooling is setup consistently across the organization. As a result, we're asking maintainers to ensure the following tools are enabled in...
Follow up to #4741, does the same but for metric signal. Fixes #4371 ~Will rebase once 4741 is merged~
This allows the configuration of other attributes than service.name. I'm using a personal fork of go-jsonschema to test out that the implementation would work for otel-config's use-case Fixes #4828
The Resource model only supports a ServiceName attribute. https://github.com/open-telemetry/opentelemetry-go-contrib/blob/044e09ac8bfe0d5a60510778017bec57413243d9/config/generated_config.go#L19-L22 This should be updated to support additional attributes as pointed out by @pellared here: https://github.com/open-telemetry/opentelemetry-go-contrib/pull/4824#discussion_r1457142001
The security SIG is looking to ensure that security tooling is setup consistently across the organization. As a result, we're asking maintainers to ensure the following tools are enabled in...
The security SIG is looking to ensure that security tooling is setup consistently across the organization. As a result, we're asking maintainers to ensure the following tools are enabled in...
The spec for OTLP exporter recommends supporting both protobufs over grpc and json over http for exporting telemetry via the OTLP exporter https://github.com/open-telemetry/opentelemetry-specification/pull/699/files **Describe the solution you'd like** Currently, the...
The security SIG is looking to ensure that security tooling is setup consistently across the organization. As a result, we're asking maintainers to ensure the following tools are enabled in...
Currently the go modules under the `collector` directory are not published, this should be fixed to ensure any downstream users of these modules can use them.