feat: Add support for tracing for http addon

[bhussain91]

Signed-off-by: Bilal Hussain [email protected]

Provide a description of what has been changed
The change is to add tracing capability into the keda http addon using opentelemetry. The changes allows the add on to generate and export spans to console (development) or otel gRPC endpoint. Further information on how to configure tracing can be found in the docs

Checklist

• Commits are signed with Developer Certificate of Origin (DCO)
• Changelog has been updated and is aligned with our changelog requirements
• Any necessary documentation is added, such as:
  • README.md
  • The docs/ directory
  • The docs repo

Fixes #

[zroubalik]

@bhussain91 any update on this please?

[bhussain91]

@bhussain91 any update on this please?

@zroubalik I've refactored the code as per comments by @JorTurFer

[zroubalik]

@bhussain91 could you please fix the linter problem?

[bhussain91]

@bhussain91 could you please fix the linter problem?

@zroubalik
added to exclude that line in linkinator
.github/workflows/linkinator.yaml

[zroubalik]

@bhussain91 could you please fix conflicts in go.mod? 🙏

[bhussain91]

@zroubalik conflicts should be resolved now :) thanks

[bhussain91]

@zroubalik @JorTurFer wondering why the e2e tests are failing here? whereas they seem to pass when I execute them locally. is there something I need to do?

[JorTurFer]

The only test that's failing is interceptor_otel_tracing_test. Does it pass on your local?

[bhussain91]

The only test that's failing is interceptor_otel_tracing_test. Does it pass on your local?

actually I've made some code changes, realised it was failing on my local again due to schema version conflict which should be resolved now, local e2e-tests are passing now on a brand new cluster with no test caches

[zroubalik]

The only test that's failing is interceptor_otel_tracing_test. Does it pass on your local?

actually I've made some code changes, realised it was failing on my local again due to schema version conflict which should be resolved now, local e2e-tests are passing now on a brand new cluster with no test caches

great, there are some problems in the static check, PTAL

[bhussain91]

The only test that's failing is interceptor_otel_tracing_test. Does it pass on your local?

actually I've made some code changes, realised it was failing on my local again due to schema version conflict which should be resolved now, local e2e-tests are passing now on a brand new cluster with no test caches

great, there are some problems in the static check, PTAL
@zroubalik I've fixed the static checks but I am not sure why the WhiteSource Security Check is failing. any ideas?

[zroubalik]

@bhussain91 let's ingore the whitesource, it is failing across the whole org, not related to this PR

The only test that's failing is interceptor_otel_tracing_test. Does it pass on your local?

actually I've made some code changes, realised it was failing on my local again due to schema version conflict which should be resolved now, local e2e-tests are passing now on a brand new cluster with no test caches

great, there are some problems in the static check, PTAL
@zroubalik I've fixed the static checks but I am not sure why the WhiteSource Security Check is failing. any ideas?

It is an env issue, not related to this PR, please disregard.

[JorTurFer]

LGTM! (sorry for the super late review, my life's been complicated). Could you rebase main branch to fix go.mod/go.sum issues?

[bhussain91]

LGTM! (sorry for the super late review, my life's been complicated). Could you rebase main branch to fix go.mod/go.sum issues?

Hey sorry was away on holiday, I've rebased now, should be all up to date

[JorTurFer]

Sorry because we were on vacations this time :( could you rebase your branch again? Now we are here to merge it