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.

Sign up for GitHub

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

Jump to bottom

Consider alternatives to GRPC for charm_tracing #53

Closed
PietroPasotti opened this issue Nov 30, 2023 · 0 comments · Fixed by #55
Closed

Consider alternatives to GRPC for charm_tracing #53

PietroPasotti opened this issue Nov 30, 2023 · 0 comments · Fixed by #55
Labels
Status: Triage Type: Enhancement

Comments

@PietroPasotti
Copy link
Collaborator

Enhancement Proposal

ATM charm-tracing uses tempo's otlp_grpc ingester to submit traces to Tempo
we should consider a more lightweight non-grpc (e.g. http) alternative to:

  • prevent future compatibility issues when the grpc model versions end up desyncing
  • prevent adding 100MB to every charm using charm_tracing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Status: Triage Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Switch to otlp/http protocol in charm_tracing canonical/tempo-k8s-operator
1 participant
@PietroPasotti