4 ms·
If Chronograf is a completely new product kudos to your team. I assumed it was a fork of Grafana because it looked and acted very, very similar to Grafana based
by netinstructions 11y ago
If Chronograf is a completely new product kudos to your team. I assumed it was a fork of Grafana because it looked and acted very, very similar to Grafana based on the 'Getting Started' docs of Chronograf.
Just curious, what are some reasons why one would choose Chronograf over Grafana right now?
- pauldix 11y agoI think it's similar because you're building graphs for a dashboard. Most of those UIs I've seen end up looking very similar. Our longer term goal with Chronograf is that it'll help with doing ad-hoc data exploration and, more importantly, give developers an easy tool to quickly build visualizations for their applications.
- benstronaut 11y agoProduct Designer for Chronograf here. We're currently filling in the basics of what we believe to be a strong dashboard tool, that it makes it easy to build queries, create graphs and put them in a dashboard in less than 15 min. We're at 0.3 and still implementing basic features. Where we differ in product is our approach. We see dashboarding, and building graphs as a design problem. What are the issues we're trying to solve? How can we solve them better? Main differentiation right now is the query builder which makes it easy to prototype influxql queries and see data. Also, our dashboard user flow is pretty quick to go from no graphs to full dash. We will add more visualization options later. Right now, it's a really good tool for mvping a dashboard. We're still figuring out the next steps, like more features and functionality to make it a more complete tool. My main concern is if we're solving the right problem for the right user. If you'd like to give us your thoughts as a user of dashboards we'd love to hear from you. Email us at Chronograf@influxdata.com