Interceptor Proxy - OTEL Instrumentation

[zorocloud]

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

[JorTurFer]

I think that this is a really interesting feature!
In KEDA (core) we already support prometheus and recently we added experimental support to otel (for metrics in both cases). I think that supporting both for metrics + otel for traces would be an awesome improvement.
If you are willing to help with that, I can assign the issue to you :)

[zorocloud]

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?

[JorTurFer]

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

[zorocloud]

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 :)

[zorocloud]

@JorTurFer I have raised an initial PR for metrics support. Let me know your thoughts :)

[stale]

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.