(Its something I'm really keen on myself - We use jsonnet internally to version control our dashboards and load them into config maps in our kubernetes clusters)
Edit: guessing it is: https://github.com/grafana/grafonnet-lib#examples ?
We also have a lot of other open source jsonnet tooling:
https://github.com/grafana/jsonnet-libs https://github.com/grafana/tanka
Congrats on the round!
We currently use Grafana Loki + Grafana and it's working amazingly well, we've tested load over 600 logs/second (1 Core VPS 2GB RAM) without any issues.
I got it wrong with Cortex (scalable Prometheus) and have been paying the price - poor adoption, smaller community and less mindshare. We're 100% committed to making sure Loki and Grafana are super easy to self-host, and are even putting time and effort into making Cortex and Metrictank easier too.
Do you plan on going the Gitlab route with self-hosted "premium" licensing? (Also called open core)
Having the right differentiation is key here, and something we're super sensitive to - for instance, we put LDAP (a typically enterprise feature) into OSS Grafana. What this space and let us know what you think!
My two cents:
- Deliver a version of Grafana that is available packaged as an appliance, with very little need to edit the INI files. Click to deploy from the Amazon marketplace with the enterprise license included. Easy guide to getting it running with the IAM roles needed to be a first class Cloudwatch adjunct.
- Build on your current SSO offerings and get support for SAML into the mix, as it's what most companies have settled on for access control.
- Keep working on the dashboard provisioning tech and maybe even provide a templating mechanism accessible from the UI that spits out new dashboards on demand, beyond the (excellent) variable functionality that's currently there.
- More work on alerting! You're so close to a first-class alerting system, but we need template variables in alert text and subject lines, support for alerts on dashboards with template variables, severity levels, and a better UX for configuring alarm conditions. Another feature I'd push hard for any company to pay for an Enterprise license to get would be any kind of adaptive, trend-based thresholds rather than the fixed min/max you currently have. It's about the only reason I'd still push some folks towards Datadog and they rake the money in hand-over-fist.
Thanks so much for your product, it really is an absolute gem. Hope I can get an employer to start paying for it one of these years.
It's also frustrating that it's effectively impossible with the Cloudwatch data source to select resources to alert on using their tags (e.g. select the elb with app=foo and env=prod). The dimension_values() function lets you filter based on tags, but instead of being usable directly in a panel's query it requires using a variable as an intermediary, which then disables alerting.
Currently there's no way to access dashboards unless you have an account on Grafana. There's no way to share dashboards with the public.
if not, maybe a distribution of values in the given time instead of just statistics? i'd be happy with sorted ranking of any kind.
Example: You have a graph and want to see a value, so you touch inside it. Instead of the value you get "Add annotation" without the value showing.
Haven't found a way to disable this. Grafana v6.4.2. Is this known?
Also, moving the finger sideways inside a graph should adjust the time. This should be configurable.
That being said, Grafana will always treat other datasources as first class citizens, like we already do with Influx, MySQL, CloudWatch, Stackdriver, Elastic etc. This is our "un-vendor" approach.