-
Notifications
You must be signed in to change notification settings - Fork 95
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
Interceptor Proxy - OTEL Instrumentation #910
Comments
I think that this is a really interesting feature! |
Yes I'm happy to do that. I actually know someone who is interested in contributing the trace portion of this, is it possible for both of us to take the issue and split it? |
I think so. You can work in a single fork together if both parts are required for working, or just in to PRs if they can work independently, in that case, the second PR will just rebase the first one and validates that it works |
Sweet, will go with this approach :) |
@JorTurFer I have raised an initial PR for metrics support. Let me know your thoughts :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Proposal
Currently the interceptor proxy does not emit any metrics or traces which makes it difficult to understand how the service is performing. It should use OTEL instrumentation to provide observability, making it easier to monitor key performance attributes of the service in a real world setting.
Use-Case
Running the interceptor proxy in a production setting where having insight into the performance of your platform services is key.
Is this a feature you are interested in implementing yourself?
Yes
Anything else?
No response
The text was updated successfully, but these errors were encountered: