davkal

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

> I love most of the people I've worked with at Grafana Cloud but it's a painful product. The price makes up for it though, so we use Grafana Cloud.

Hi, I run the Grafana team at Grafana Labs. If you could fix one thing, what would it be?

Which version are you using? And if you could tell us which datasources, that would help us as well. Narrowing this down helps us prioritise bugs.

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).

I'm curious to hear what the hurdles are. Let me know if you want to chat, I'm David at Grafana.

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

Amazing UX feedback, thanks!!

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.

We're working on this for v6.6, so there are no designs yet.

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.

[1] https://speakerdeck.com/davkal/on-the-path-to-full-observabi...

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.

[0] https://github.com/grafana/grafana/issues/new

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.

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 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

Weaveworks | London, Berlin, San Francisco | Mostly ONSITE | Full-time | open source | https://www.weave.works/

* Senior backend dev: develop microservices and container tools

* Senior frontend dev: 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 code in Go or JS on tools for containerized applications that run on Docker or Kubernetes. Those tools enable developers to focus all of their energies on the application itself. Tools like Weave Scope observe components and their interactions to provide visibility and insights; and provide runtime control over the resulting system.

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

The hiring process: Checking your CV/GH/SO (if not enough signal: small coding challenge), 30 mins hangout, 3h take home coding challenge, in person interview w/ future colleagues

If you’re interested please drop us a line at jobs (at) weave.works

Yeah, if your life runs in iterations ;-) Or just spend it outside the loop using those proportions.

$1: top-up someone else's metro card, it will restore their faith in humanity

$10: find a neighbourhood coffee shop, buy a coffee, tip the rest, talk to locals

$100: Kindle/books

$1,000: Choose a trade, buy the tools, master them

$10,000: Travel outside your comfort zone, talk to locals, learn their language, get perspective

$100,000: Invest half, spend the other half on the previous items

$1,000,000+: Don't be a money-driven role model to others, study politics and people, use your financial cushion to do good in your community. Stay interested, stay awesome.

Nice app! I'm a Runkeeper user and I'm missing two things there: track your friends in the same map when meeting for a run (useful if starting point is not the same), and some sort of soundcloud integration (the track could be included in the facebook post after the run). The graphics look very good and the color scheme is well balanced. Is this native or html5? Any particular UI framework used?