Time series database Graphite seems to be falling into disfavor
11–20 of 83 posts
Re: Time series database Graphite seems to be falling into disfavor
#12Re: Time series database Graphite seems to be falling into disfavor
#13What does a modern metrics stack look like? There are so many words... Graphfana, Kibana, StatsD, Graphite, etc. Which bits should I choose and attach together?
Not so much for the design (oh look it's white instead of black, who cares), but the way they've handled it subsequently.
The 3.x -> 4.x transition for Kibana left a product that was missing really basic features (like, the ability to set graph colors for one - a bug/feature request that's been open since last january).
As it stands, upgrading from Kibana 3 to Kibana 4 is a step backwards. You lose functionality rather than gaining it.
They also decided to require a major version bump to Elasticsearch (to 2.x) with a point release of Kibana.
I used to be super optimistic about the Elastic guys, but some of these decisions are just head-scratchingly awful.
Re: Time series database Graphite seems to be falling into disfavor
#14Can some one change heading so it is understood as software and not actual Graphite
Re: Time series database Graphite seems to be falling into disfavor
#15http://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.
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 disfavor
#16Can some one change heading so it is understood as software and not actual Graphite
Re: Time series database Graphite seems to be falling into disfavor
#17I've been in search of a good time-series database solution for some time now, and have pretty much given up on it and am in the process of rolling my own: https://github.com/grisha/timeriver My issues with the present state of TS isn't the volume. I was looking for using TS outside of the DevOps world. Everyday things like your heart rate over time, price of gas at the nearest station, number of people in line at yo…
While it is used for machine learning, it actually makes a lot of sense to follow a similar approach for more general time series applications.
Re: Time series database Graphite seems to be falling into disfavor
#18It is kind of amazing how hard it is for existing time series database systems to track the changing needs of the marketplace.
Re: Time series database Graphite seems to be falling into disfavor
#19Can some one change heading so it is understood as software and not actual Graphite
Re: Time series database Graphite seems to be falling into disfavor
#20Can some one change heading so it is understood as software and not actual Graphite