Robert Pająk

@MrAlias Is it needed for beta?

I think the proper fix is to improve the error handling and tell that `git worktree add` failed. Maybe the command is emitting something to stdout/stderr that is worth printing?...

> we don't support oter grpc or json, so it's kinda limited support. Related: https://github.com/signalfx/splunk-otel-go/issues/2582. I think I can change the our OTel Go distribution to use the HTTP/protobuf endpoint...

> we don't have support for mapping the content we support in builtin dashboards and alerts from otel. This looks like related to https://github.com/signalfx/splunk-otel-collector/blob/e1e54a2c780ce7689c4a52a3108defb23896f12c/go.mod#L93 CC @atoulme

> We depend on sfxclient for collectd use cases. @mdubbyap @atoulme How about moving the source code from `golib` to `splunk-otel-collector`?

Here are known importers: https://pkg.go.dev/github.com/signalfx/golib/sfxclient?tab=importedby. We would need to first check: - what importers has to still use `sfxclient` and they cannot use `splunk-otel-go`. If there are more than one...

@owais, can you take a look?

Do you mean this: https://github.com/signalfx/tracing-examples/blob/11347885f3854fec9d12ed401bfccbad50af6fc2/opentelemetry-tracing/opentelemetry-python-tracing/falcon/main.py#L18 ? If so, then this is just an example of creating a manual span on top of automatic instrumentation.

Just to make it clear. I think that the schema MUST accept multiple providers.

> @pellared why when you can create multiple providers by running multiple configurers? I do not know the exact use cases but I already heard that some people are having...