Is anyone using a log management tool in conjunction with Grafana? I.e. if you see something anomalous or see an alert triggered, how do you investigate what's going on?

We've used Grafana with Sematext Logsene (which exposes Elasticsearch API, so it's like having Grafana talk to ES).

Here's a short howto + video: https://sematext.com/blog/2015/12/14/using-grafana-with-elas...

You can use ElasticSearch as an annotation provider over the top of your time series metrics. We publish events from our continuous deployment pipeline into ES and then surface those in a generic application dashboard. There hasn't been a deployment that we didn't already know about, but in theory when more users are going through CD it will provide more of a heads up.

You can use Graylog for log management, that's the free open-source solution. (graylog + elasticsearch + mongodb)

You can use Splunk if you have money. That's the de facto standard. Beware that it's one of the most expensive software license on the planet :D

Looks interesting at first glance. I was always wondering if DSLs like this one require too much boilerplate code. What do others think? Is this a feasible tool to use for testing a larger web app?

Gaah that's addictive. I mean, the source and blog post is nice too, but that game...! :)

On a more serious note: I've never heard of ECS before, but it seems like it's been used in game development for a while. I feel like most data visualization projects these days (especially the ones using D3.js) use some form of ECS, although not necessarily out of deliberation. I wonder if there are best practices from game development that can aide the development of data visualizations

Posts like this is what I like about Hacker News! It would be great if there were other examples like this where organizations share their setup for real-world projects and presences.

Yeah, you guys were slamming our servers. Feel free to try again, and if you run into the same problem, hit us up!

Unfortunately it doesn't work at all now, but I'll definitely keep trying :)

It's something that we wanted to show too. Apart from the technical complexity involved it would be hard to show warming. In the last century overall warming was maybe 1 deg C, but temperatures fluctuate from year to year by up to 15 degrees. Here is a delta graph for 1900 - 2012, for example: https://www.evernote.com/shard/s5/sh/6d1d932a-c1ed-411d-9b74... One way of doing it though would be to use a rolling average of, say, 5 years.

You mean something like http://halftone.co/projects/temperatures/date/2003/4? Good idea, thanks!

FYI: I get a 404 on this link.

I don't think he was sarcastic, he probably really meant that such shortcut urls are good ideas and thanks the parent for it.

That's right, and I hope that's where both Tributary and programming in general are headed. However, saying that they "make the same mistake" seems odd. Progress can happen incrementally, and sometimes you have to see what works and what not. It's almost as if you have to prototype your idea and see real results immediately, very similar to the goals of learnable programming.

You are right of course; the problem is that even though there have been people working on this problem since 2003, no one has communicated very well about the results outside of a few academic circles.

Hancock solves this problem with live text in Flogo II, but all we know about it is from his dissertation (http://llk.media.mit.edu/papers/ch-phd.pdf). I observed the same phenomena when I did my Sueperglue work back in 2007 (http://research.microsoft.com/apps/pubs/default.aspx?id=1793...), but I never really bothered to follow up until now (with inspiration from Bret's work, of course).

This is pretty amazing. Granted, I'm friends with the authors (@enjalot, @mrejfox), but Tributary has easily become one of my most used tools on a daily basis.

Love it! The beats alone make these tutorials so much more enjoyable to follow than usual tech turtorials.