News for hackers. Stuff that matters.
Re:Vulcan: An API-compatible alternative to Prometheus by nixgeek on Thursday August 25, 2016 @01:34PM (#12360864)
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".

Re:Vulcan: An API-compatible alternative to Prometheus by kanwisher on Thursday August 25, 2016 @04:19PM (#12362155)
One 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
Re:Vulcan: An API-compatible alternative to Prometheus by eefy on Thursday August 25, 2016 @04:46PM (#12362362)
The 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 ;)
Re:Vulcan: An API-compatible alternative to Prometheus by decwakeboarder on Thursday August 25, 2016 @02:25PM (#12361227)
From 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.