-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Proposal] Add documentation for monitoring Gin with OpenTelemetry #4107
Comments
I hope the observable part of the document will focus on the otel project, supplemented by the alibaba project. |
I agree, the project will be donated into OpenTelemetry Community soon, see open-telemetry/community#1961. We will focus on the otel project. |
We could also mention the OpenTelemetry eBPF based auto-instrumentation (https://github.com/open-telemetry/opentelemetry-go-instrumentation/), which supports Gin as well. |
Yes, I really want to raise a PR to introduce different ways of monitoring Gin Application based on OpenTelemetry EcoSystem!. @appleboy @thinkerou What do you think about that? cc @damemi |
And can we also add a middleware for OpenTelemetry in |
@123liuziming Yes
|
Cool!!! Should I raise a PR to modify https://github.com/gin-gonic/gin/blob/master/docs/doc.md or put the document into |
@123liuziming Thanks for your contribution. I closed the issue when PR was merged. |
Hi all, As we all know gin is the best http framework in the golang ecosystem. But I found that gin doesn't have the ability to integrate tracing and metrics by default and there doesn't seem to be a best practice in the documentation on how to monitor gin applications. Our project(https://github.com/alibaba/opentelemetry-go-auto-instrumentation) allows tracing and metrics to be collected and reported on the gin app without making changes to user code. I was wondering if it would be possible for me to add an observable subsection to the official documentation for this project that describes best practices for observing the gin application. Thanks!
The text was updated successfully, but these errors were encountered: