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
If we could get this working, a user would provide a plain shell script, run it with webhookd and provide an OpenTelemetry collector endpoint and thus get an Opentelemetry instrumented shell script automatically, it would make life very easy for DevOps operators and SREs.
The text was updated successfully, but these errors were encountered:
I can understand the need, but webhookd is not designed to alter the scripting part in order to add auto-instrumentation. However, what it could do, is implement OpenTelemtry traces for its internals and provide the span ID to the script to let the script continue tracing operations with the tooling of its choice (such as tracepusher). Would this approach meet the need?
This project looks great and I'm wondering if it is possible to auto-instrument the provided shell scripts to emit Opentelemetry traces.
I have a project called tracepusher which does this, but I'd need assistance from this project on the instrumentation side.
Here's a sample instrumented shell script: https://github.com/agardnerIT/tracepusher/blob/main/samples/script.sh
If we could get this working, a user would provide a plain shell script, run it with
webhookd
and provide an OpenTelemetry collector endpoint and thus get an Opentelemetry instrumented shell script automatically, it would make life very easy for DevOps operators and SREs.The text was updated successfully, but these errors were encountered: