Hi! I work on the Grafana OSS team. We added some more export options recently (dashboards have a big Export button at the top right; panels can export their data via the panel menu / Inspect / Data), try it on our demo page: https://play.grafana.org/d/000000003/graphite3a-sample-websi...
Could you describe your use case around "exportable to any code" a bit more?
> I've used Grafonnet before for doing Grafana at scale. Simply put, I hate it. Apparently an alternative is being worked on at Grafana so I'm waiting for that. But if you need to make hundreds of panels....it works well enough.
Hi, I run the Grafana team at Grafana Labs. I'd love to learn more about your Grafonnet use to help us build something better. I'm david at grafana com
Ryan (mentioned in the article) is building a team around this (non-timeseries data, sensors data, manufacturing). Head to our hiring page if you want to join his R&D team (US-remote).
It’s literally my job to keep Grafana real. Our budding UX team is getting a lot of training on SRE as a discipline and we run weekly internal UX feedback sessions where all of engineering can join and course-correct. Same with weekly feedback sessions with our existing user base. Get in touch with david at grafana if you’d like to participate.
Director of UX here. This year we rewrote a lot of the data flow plumbing in grafana to allow streaming with the very goal to enable sensor and other high frequency use cases. More to come soon
Director of UX here. We’re trying to find a way to have a graphical builder for simple queries. But anything with binary operators is a UI challenge that will be text based for a while. We’re testing the waters with a graphical LogQL builder for Loki first. Watch this space.
Yeah, we’re trying to make datasource query latency more obvious soon. It’s too easy to say Grafana is slow right now. We want users to make better decisions on what to optimize in their monitoring stack. That being said, dashboard search can be slow on bigger instances. But we’re working on it.
Director of UX here, we do want to integrate a trace viewer soon. We actively talking to Uber to find ways of directly reusing their Jäger components. Still considering other options too. Will check out your project!
Director of UX here. What's your mobile vs desktop use? Which devices are you using?
That will help us getting more mobile-friendly in upcoming releases.
Director of UX here. We're trying to focus on improving existing workflows and less on visual design changes. That being said, form styles will be overhauled soon.
Grafana Explore author here: just posted my slides from the announcement talk [1] that hopefully clarifies a bit on what it is.
Re splunk, depends what features you rely on. Loki is a no-frills log aggregation. Would be great to hear what features are needed for you. Feel free to write to me at david at grafana or open an issue.
Grafana Explore author here. It's still in Beta and would love feedback. Simply open an issue at [0].
What we tried to get right is the seamless switch from a Prometheus to Loki where it's retaining the labels of the query to essentially find the logs that come from the same e.g., "job". The assumption is that you need to be consistent with your relabelling rules of Prometheus and Loki.
Weaveworks | Senior Backend Developer | San Francisco, London, Berlin, Madrid | ONSITE, Full-time, https://www.weave.works
* Senior backend dev: develop microservices (primarily in Go) and container tools
* Senior frontend dev: write reactive and snappy web UIs that show complex data and are easy to navigate (Berlin only)
* Developer experience/evangelist: spread the word in meetups/conferences, develop integrations for our tools
Come help us build OSS tools that other developers use to tame their containerized applications. Projects like Weave Scope observe containers/pods/services and their interactions to provide visibility and insights. Developers can quickly see the state of the resulting systems and validate their assumptions.
We offer family-friendly hours (some of us have kids, too) and encourage a good work-life balance. Feel free to work from home on certain weekdays, or combine work and travel for a month. It's no big deal if you're not a Go expert, we trust that you can learn on the job. Also, all our tools are open source: https://github.com/weaveworks Browse our PRs to see how we work as a team!
The hiring process: Checking your CV/GH/SO (if not enough signal: small coding challenge), 45 mins hangout, afternoon take-home coding/design challenge, in person interview with future colleagues
If you’re interested please drop us a line with your desired location at jobs (at) weave.works
Note: Weaveworks will consider visa sponsorship on case-by-case basis, subject to business needs and individual eligibility.
https://www.weave.works | San Francisco, CA & London, UK & Berlin, Germany | ONSITE | Full-time
* Senior backend dev: develop microservices (primarily in Go) and container tools (all locations)
* Senior frontend dev: write reactive and snappy web UIs that show complex data and are easy to navigate (Berlin only)
* Developer experience/evangelist: spread the word in meetups/conferences, develop integrations for our tools (London and SF only)
Come help us build OSS tools that other developers use to tame their containerized applications. Projects like Weave Scope observe containers/pods/services and their interactions to provide visibility and insights. Developers can quickly see the state of the resulting systems and validate their assumptions.
We offer flexible hours with a good work-life balance, with a typical day going from 10am-6pm. All our tools are open source: https://github.com/weaveworks Browse our PRs to see how we work as a team!
The hiring process: Checking your CV/GH/SO (if not enough signal: small coding challenge), 30 mins hangout, afternoon take-home coding/design challenge, in person interview with future colleagues
If you’re interested please drop us a line with your desired location at jobs (at) weave.works
Note: Weaveworks will consider visa sponsorship on case-by-case basis, subject to business needs and individual eligibility.
https://www.weave.works | San Francisco, CA & London, UK & Berlin, Germany | ONSITE | Full-time
* Senior backend dev: develop microservices (primarily in Go) and container tools
* Senior frontend dev: write reactive and snappy web UIs that show complex data and are easy to navigate
* UX Designer: design UIs for our various container tools, visualize networks and data traffic
* Developer experience/evangelist: spread the word in meetups/conferences, develop integrations for our tools
Come help us build OSS tools that other developers use to tame their containerized applications. Projects like Weave Scope observe containers/pods/services and their interactions to provide visibility and insights. Developers can quickly see the state of the resulting systems and validate their assumptions.
We offer flexible hours with a good work-life balance, with a typical day going from 10am-6pm. All our tools are open source: https://github.com/weaveworks Browse our PRs to see how we work as a team!
The hiring process: Checking your CV/GH/SO (if not enough signal: small coding challenge), 30 mins hangout, afternoon take-home coding/design challenge, in person interview with future colleagues
If you’re interested please drop us a line with your desired location at jobs (at) weave.works
Note: Weaveworks will consider visa sponsorship on case-by-case basis, subject to business needs and individual eligibility.
Could you describe your use case around "exportable to any code" a bit more?