4 ms·
Kinda don't get why DigitalOcean "forked" rather than solving the long-term retention problem by working with upstream, especially given the number of comments
by nixgeek 10y ago
Kinda don't get why DigitalOcean "forked" rather than solving the long-term retention problem by working with upstream, especially given the number of comments which state "Development in this area should be done in Prometheus first then merged into Vulcan".
Feels like another "We want our shed to be blue".
- decwakeboarder 10y agoFrom looking at their architecture diagram it seems that this is different enough from Prometheus's single golang binary to "justify" a fork. I haven't looked close enough, but hopefully they've done so in a way that common things (query functions, alertmanager integration, etc) can be kept in sync with upstream easily.
- kanwisher 10y agoOne of the devs here, we are actively working with the Prometheus devs. We are all at Prometheus Conf this week. The upstream Prometheus will unlikely ever have a distributed backend, however it will support projects like this
- eefy 10y agoThe prometheus core team has been pretty clear on their stance about some of the things that vulcan is focusing on (things like long term storage for example), as such it didn't make sense to fight with them to make them change their mind ;)