Skip to content

Feature: Tracing via OpenTelemetry #1709

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

xBlaz3kx
Copy link
Contributor

@xBlaz3kx xBlaz3kx commented Mar 22, 2025

Proposed changes

  • Added tracing:
    • HTTP API tracing with otelgin (tracing is only enabled on the /v1 endpoints and is skipped for UI)
    • GRPC server and client tracing (internals) with otelgrpc
    • Custom store level tracing
  • Added context to various interfaces as it is required in order to properly create/propagate traces/spans
  • New config/env variable - tracing
  • Added docker compose example setup with complete observability

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Todo

  • Documentation update

Relates to #1694

@xBlaz3kx
Copy link
Contributor Author

@vcastellm Mind taking a look? Id appreciate more insight on what could/should be included in tracing.
I can add those later, this serves as a good demo/base for future efforts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant