Skip to content

🔌 Plugin: Distributed Tracing #1905

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

Closed
3 tasks done
iblancasa opened this issue Nov 9, 2024 · 2 comments
Closed
3 tasks done

🔌 Plugin: Distributed Tracing #1905

iblancasa opened this issue Nov 9, 2024 · 2 comments

Comments

@iblancasa
Copy link

🔖 Summary

The goal of this plugin is enhance the usability of Backstage through various ways of depicting distributed tracing.
It would be a generic plugin that could be integrated with different distributed tracing storages.

This issue supersedes #253 because this proposal is to create something more generic than just focused on one tracing storage.

I started working on a first version of the plugin and will send a proposal soon.

🌐 Project website (if applicable)

https://grafana.com/oss/tempo/
https://www.jaegertracing.io/
https://zipkin.io/

✌️ Context

Distributed tracing is essential for understanding the interactions between services in complex, microservices-based applications. As organizations adopt distributed architectures, they often rely on tracing tools like Grafana Tempo, Jaeger, or Zipkin to gain insights into service performance and root causes of latency or errors.

This plugin will bridge the gap between tracing data and the Backstage developer portal, bringing observability closer to developers by allowing them to view trace data directly within Backstage. The initial version will focus on Grafana Tempo, with planned support for other backends. The implementation will include abstractions to facilitate this future extensibility, ensuring the plugin remains backend-agnostic while maintaining compatibility across tracing systems.

👀 Have you spent some time to check if this plugin request has been raised before?

  • I checked and didn't find similar issue

✍️ Are you willing to maintain the plugin?

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

Yes I am willing to submit a PR!

@vinzscam
Copy link
Member

it would be a great addition, indeed

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jan 18, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 26, 2025
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