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

[Feature]: Support Azure Data Explorer as storage #4640

Closed
markrendle opened this issue Aug 9, 2023 · 1 comment
Closed

[Feature]: Support Azure Data Explorer as storage #4640

markrendle opened this issue Aug 9, 2023 · 1 comment

Comments

@markrendle
Copy link

Requirement

As a developer at a site that prefers to use Azure Platform Services where available,
I want to use Azure Data Explorer (Kusto) as a storage backend for Jaeger
So that I can have a decent UX for exploring traces instead of the Azure Portal

Problem

Nobody on the platform engineering team has an appetite for maintaining a Cassandra or Elasticsearch cluster, so we are currently writing traces to Azure Monitor but I'm leading an effort to switch to Azure Data Explorer. There's a reasonable UX for logs, and metrics can be surfaced in Grafana, but there's basically nothing for traces. If Jaeger supported ADX as a persistence backend, I could persuade people that we could use the Jaeger UI.

Proposal

Reach out to the Azure Data Explorer team and get them to contribute a storage backend or plug-in? They seem pretty keen on creating integrations.

Open questions

No response

@yurishkuro
Copy link
Member

Jaeger project does not support proprietary storage solutions as official backends for Jaeger, only open source databases. The best path for proprietary storage is to implement support for Jaeger's Remote Storage API (rather than a plugin route).

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

No branches or pull requests

2 participants