You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Running an OpenTelemetry scenario (e.g. an instrumented Python server, a client, and a Collector/Docker), then gathering the telemetry it produces, is a common requirement for testers, developers, and learners. Could this be made easier?
Describe the solution you'd like
Would like to be able to define all of the inputs of an OpenTelemetry scenario, point a tool at it, then have the outputs (telemetry) be available in the same place.
Is your feature request related to a problem?
Running an OpenTelemetry scenario (e.g. an instrumented Python server, a client, and a Collector/Docker), then gathering the telemetry it produces, is a common requirement for testers, developers, and learners. Could this be made easier?
Describe the solution you'd like
Would like to be able to define all of the inputs of an OpenTelemetry scenario, point a tool at it, then have the outputs (telemetry) be available in the same place.
Describe alternatives you've considered
There is manual setup, and there's tooling like https://github.com/open-telemetry/opentelemetry-python/tree/main/tests/opentelemetry-docker-tests/tests and https://github.com/signalfx/splunk-otel-python/tree/main/tests/integration, which require Docker.
Additional context
I have a working prototype here.
The text was updated successfully, but these errors were encountered: