Skip to content
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

Option to disable OTEL completely in v2 to emit logs/metrics from connector to HGE #10656

Open
pari-m opened this issue Jan 22, 2025 · 0 comments
Labels
a/internal k/enhancement New feature or improve an existing feature

Comments

@pari-m
Copy link

pari-m commented Jan 22, 2025

Is your proposal related to a problem?

Hasura app imports io.opentelemetry.api.trace.Tracer into the Connector code for usage -- when building, if OTEL is disabled, the classes will not be compiled into the JAR

This causes resolution failure since now the Tracer import is asking for classes which don't exist

Describe the solution you'd like

An option to disable OTEL in the connectors

Describe alternatives you've considered

@pari-m pari-m added the k/enhancement New feature or improve an existing feature label Jan 22, 2025
@Kashish3009 Kashish3009 changed the title Option to disable OTEL completely in V2 Option to disable OTEL completely in v2 to emit logs from connector to HGE Jan 27, 2025
@Kashish3009 Kashish3009 changed the title Option to disable OTEL completely in v2 to emit logs from connector to HGE Option to disable OTEL completely in v2 to emit logs/metrics from connector to HGE Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a/internal k/enhancement New feature or improve an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants