-
Notifications
You must be signed in to change notification settings - Fork 34
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
Support for HTTPS tracing protocol #194
Comments
I was looking at doing exactly the same thing @danielloader. Did you manage to make progress with this? |
I'll want to use http as well, any update? |
Because this repo looks unmaintained I added support for https in my fork corentinmusard/otel-cicd-action. I plan to maintain and release more features on my fork, feel free to use it. If you want to give it a try, you just have to replace the action name: uses: corentinmusard/otel-cicd-action@v1 Please tell me if it's not working as intended 🙂 |
Thank you @corentinmusard! Using your fork in: |
It looks from glancing at the source this action only supports gRPC for the OTEL traces, can I confirm this is correct?
Looks that you'd need to import/use https://www.npmjs.com/package/@opentelemetry/exporter-trace-otlp-proto conditionally based on the environment variable for the protocol, or pickup and guess from the endpoint protocol prefix in the URI.
Was trying to use the action with grafana cloud but they haven't got gRPC support yet for ingesting OTEL tracing spans and as expected if the above assumption is true then it's an expected failure.
Source: https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/#push-directly-from-applications-using-the-opentelemetry-sdks
https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/#otel_exporter_otlp_traces_protocol
The text was updated successfully, but these errors were encountered: