-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto tracing with OpenTelemetry + tracepusher #90
Comments
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? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: