Robert Pająk

Results 153 issues of Robert Pająk

I do not see any easy way how to find out which env vars are supported (e.g. `OTEL_RESOURCE_ATTRIBUTES`). Maybe we could maintain a list of it? Moreover, I feel that...

help wanted
documentation

How about adding an example of using OTel Go in a CRUD application? Do you think it would be good to put something like this somewhere under `https://github.com/open-telemetry/opentelemetry-go*` (existing repo,...

enhancement
help wanted
pkg:example

Since `0.42.0` the default `config.yaml` path used in the contrib container image changed from `/etc/otelcol/config.yaml` to `/etc/otelcol-contrib/config.yaml`. As far as I understand it was done here: https://github.com/open-telemetry/opentelemetry-collector-releases/pull/43 While I have...

documentation
good first issue

From the [OTel spec](https://github.com/open-telemetry/opentelemetry-specification/blob/5fb819c72e34cb21fe1ce5acba1dc93c2216ecb1/specification/resource/sdk.md#specifying-resource-information-via-an-environment-variable): > The OTEL_RESOURCE_ATTRIBUTES environment variable will contain of a list of key value pairs, and these are expected to be represented in a format matching to...

bug
pkg:OpenTelemetry

Ideally, the SDK should try the name of the entry assembly first and only if that fails fallback to the process name. This way it gets better default names for...

pkg:OpenTelemetry

Per [spec](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#prometheus-exporter) It will be very helpful for https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation. This repo it is a better place to have it implemented. FYI @open-telemetry/dotnet-instrumentation-approvers

enhancement
area:exporter:prometheus

We should add a page describing OpenTelemetry .NET Automatic Instrumentation under https://opentelemetry.io/docs/instrumentation/net/ Follow-up after https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/issues/958

Refactor the span and metrics assertions to make them more readable and maintainable. _Originally posted by @pellared in https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/pull/901#discussion_r911136873_

I think that our continued reliance on these optional parameters is going make the tests harder to maintain. On the one hand, it's nice that the test only needs to...

It would be nice to have a method on the mock collector to get all spans already received and bail. This would avoid waiting for spans after the application already...