graphite-dev team mailing list archive

[Jason Dixon <question253869@xxxxxxxxxxxxxxxxxxxxx>]

New question #253869 on Graphite:
https://answers.launchpad.net/graphite/+question/253869

Once upon a time, Graphlot was merged into graphite-web because it provided a new way of looking at charts. Specifically, it offered an interactive legend as you hovered over the chart. Back in 2010 this was innovative and a great way of looking at data stored with Graphite.

Leap forward to 2014, and everyone is doing client-side rendering. We've got a wealth of 3rd party dashboards and tools that support this sort of interaction. The future of Graphite is (imho) defined by the retrieval and transformative capabilities of its render API, not the static images shown in the Composer window. With tools like Grafana, Giraffe, Dusk and Tessera,we have innovative tools that provide both composition and interactive visualization workflows.

As such, I propose that we remove Graphlot from the Graphite tree. It hasn't received any significant advancements in the last four years. It's far less useful than the Composer for prototyping charts, and it doesn't offer any dashboarding capabilities. With it we had to bring various flot.js libraries into the tree, causing both internal and upstream (distro) packaging headaches. Thanks to the aforementioned tools, I believe there simply is no good reason to keep this on life support any longer.

Looking for feedback.

-- 
You received this question notification because you are a member of
graphite-dev, which is an answer contact for Graphite.