-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Open
Labels
Description
I’ve noticed that in the past there was an intention to support MongoDB as a storage option for Zipkin. However, it seems the effort didn’t move forward due to a lack of contributors and support.
I would like to help by implementing the MongoDB storage integration myself (or in collaboration with others). Before starting, I’d like to confirm if this approach is still welcome and aligned with the current project goals.
- Is MongoDB storage support still desired by the maintainers/community?
- Are there any technical guidelines or architectural decisions I should be aware of before starting?
Adding MongoDB as a storage option could benefit teams already using MongoDB, reduce operational complexity, and broaden Zipkin’s adoption.
If the maintainers agree, I’m happy to draft a proposal or start with an initial implementation to get feedback.