71–80 of 120 posts
Earlier quoted context omitted.
"The path of MongoDB is often the same: first the primary DB, then the configuration store, then it's finally removed" - (friend of mine)
Expand. MongoDB is finally removed? Why?
(e.g. regular sql database/redis/sqlite/etc)
I would like to share some thoughts on this based on experience of being a crusty old enterprise developer. The dashboard problem keeps coming back. I think the time might be finally coming for some dashboard framework to actually succeed. A dashboard framework has been tried many many times. Here are some old ones just on the top of my head: * Shindig aka OpenSocial aka Google Gadgets * J2EE portlets * OpenUSS I'm n…
How do you deal with Grafana having no isolation? Do you deploy a new instance per client? Each user has full access to all datasources from what I've seen.
I suppose you are confused because of my mentioning building product based on shindig. That was a previous employment many moons ago. I now am a many hat wearing owner of a SaaS.
While I'm speaking of Grafana I find Kibana for more useful probably because we have a lower level of traffic than big boys but still produce an atrocious amount of logging. Logs are damn useful. In some ways metrics are actually a subset of event aggregation (ie logs) so I think Kibana is more useful at first.
https://github.com/square/cube
Those can be embedded into dashboards
How does this compare to something like Grafana? https://github.com/grafana/grafana
I like Grafana. I use Grafana. I've got Grafana open in another tab right now. For all that, Grafana ain't all that and a bag of chips. Grafana is very hard to extend with new visualizations. It uses "flot", a JavaScript library that hasn't seen a commit in Github in 2 and a half years. The documentation is poor. There is definitely a need for dashboard software that allows for more complex custom visualizations -- I…
Full disclosure, I work for Grafana, but seemed relevant to mention.
I would like to share some thoughts on this based on experience of being a crusty old enterprise developer. The dashboard problem keeps coming back. I think the time might be finally coming for some dashboard framework to actually succeed. A dashboard framework has been tried many many times. Here are some old ones just on the top of my head: * Shindig aka OpenSocial aka Google Gadgets * J2EE portlets * OpenUSS I'm n…
Jenkins: the duct tape and WD40 of software automation.
Easy enough to 'just get the thing done', but as complex as you want it to be.
I would like to share some thoughts on this based on experience of being a crusty old enterprise developer. The dashboard problem keeps coming back. I think the time might be finally coming for some dashboard framework to actually succeed. A dashboard framework has been tried many many times. Here are some old ones just on the top of my head: * Shindig aka OpenSocial aka Google Gadgets * J2EE portlets * OpenUSS I'm n…
Jenkins: the duct tape and WD40 of software automation.
Easy enough to 'just get the thing done', but as complex as you want it to be.
Forgive my ignorance... what makes a dashboard different that a regular webapp?
A dashboard is a web app displaying aggregate data - usually on something like a digital signage display at a company's office - often includes 'vanity metrics' like web traffic data, Git commits, social media feeds, CI builds, etc.
So while most framework models are oriented around their own ORM, a dashboard is probably better off modeling a set of translators, and providing tools for adding new translators. Translators can take a random API, and convert into a normalized data type the rest of the framework can understand. And a good community will have a lot of these translators available.
Additionally, the dashboard framework can provide a variety of standard visualizations for the translators to send normalized data. Time series, histogram, pie chart, text, etc. And provide an intelligent layout engine for arranging a collection of these on a screen. Dashing, for example, allows a user to re-arrange dashlets.
tl;dr -- it _is_ a webapp, but the more limited scope allows for better tooling and your valuable engineers can focus the more productive uses of their time, like writing new visualizations or, more likely, new translators.
There is also Redash http://docs.redash.io/en/latest/ We are using it and it's awesome.
I was hoping that this would be a maintained fork of http://dashing.io/
I would like to share some thoughts on this based on experience of being a crusty old enterprise developer. The dashboard problem keeps coming back. I think the time might be finally coming for some dashboard framework to actually succeed. A dashboard framework has been tried many many times. Here are some old ones just on the top of my head: * Shindig aka OpenSocial aka Google Gadgets * J2EE portlets * OpenUSS I'm n…
The incoming events have a spec, like Riemann, and is compatible with Graphite. Godot2 also has it's own mini query lang [1], which allows for easy selection of events for the dash, e.g.
service =~ 'health/machine/disk/%' and status = 'ok'
There seems to be a plethora of these open source dashboard builder systems. I just want to pay for a hosted version that isn't going to be $1k monthly and require me to build "plugins" to do something that is akin to an API call.
Sorry for a shameless plug, but you might check something that I built and launched today [1] as I felt exactly the same pain point.