News for hackers. Stuff that matters.
Re:Time series database Graphite seems to be falling into di... by dmourati on Sunday November 08, 2015 @11:28PM (#10531396)
Obligatory response from Graphite contributor and author Jason Dixon who is shouted out in the vividcortex intro.

http://obfuscurity.com/2015/11/Everybody-Loves-Graphite

Personal response:

I've used Graphite, OpenTSDB, Ganglia, Cacti, and a bunch more solutions. Recently, work transitioned from OpenTSDB to a hosted solution from a startup called Wavefront.

https://www.wavefront.com/

This has been a smash hit.

Scale matters. If you are a small shop, and can workaround the atrocious UI shortcomings of Graphite by all means, go for it. As you start to get larger, OpenTSDB looks attractive. We went too far down that path but were able to quickly (< 3 months) transition over to Wavefront and haven't looked back.

Re:Time series database Graphite seems to be falling into di... by duaneb on Monday November 09, 2015 @05:02AM (#10532150)
A closed silo seems like a distinct step backwards compared to a stack you can maintain yourself.
Re:Time series database Graphite seems to be falling into di... by dmourati on Monday November 09, 2015 @01:06PM (#10534624)
Read a little more into the second part of your sentence, especially the word "maintain."
Re:Time series database Graphite seems to be falling into di... by fapjacks on Monday November 09, 2015 @01:51AM (#10531704)
Wavefront looks like it's probably closed source. Is this true?
Re:Time series database Graphite seems to be falling into di... by dmourati on Monday November 09, 2015 @02:13AM (#10531741)
Yes, sorry if that wasn't clear.
Re:Time series database Graphite seems to be falling into di... by buro9 on Monday November 09, 2015 @06:43AM (#10532479)
And do they have a self-hosted solution?

The proprietary vs open argument is less important then the argument over where the data is physically held and ownership of it.

Re:Time series database Graphite seems to be falling into di... by js2 on Monday November 09, 2015 @08:15AM (#10532820)
Agreed. I built an in-house mobile crash reporting solution even though the commercial options range from decent to excellent because none of them offered self-hosted, nor a way to export your data. We really wanted the data because it's allowed us to determine the cause of crashes and answer other questions that we otherwise couldn't w/o the raw data. There were also privacy concerns, even though in theory crash reports shouldn't have any PII. And we really don't need third parties knowing our DAU numbers and whatever else in any case.

There are finally some self-hosted commercial options in this space, but we've already built our solution and it works well.