3 ms·

Obligatory response from Graphite contributor and author Jason Dixon who is shouted out in the vividcortex intro. http://obfuscurity.com/2015/11/Everybody-Love

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 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/ 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.

fapjacks 11y ago
Wavefront looks like it's probably closed source. Is this true?
- dmourati 11y ago
  Yes, sorry if that wasn't clear.
  - buro9 11y ago
    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.
    - js2 11y ago
      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.
duaneb 11y ago
A closed silo seems like a distinct step backwards compared to a stack you can maintain yourself.
- dmourati 11y ago
  Read a little more into the second part of your sentence, especially the word "maintain."

fapjacks 11y ago

Wavefront looks like it's probably closed source. Is this true?

dmourati 11y ago
Yes, sorry if that wasn't clear.
- buro9 11y ago
  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.
  - js2 11y ago
    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.

duaneb 11y ago

A closed silo seems like a distinct step backwards compared to a stack you can maintain yourself.

dmourati 11y ago
Read a little more into the second part of your sentence, especially the word "maintain."