Example Grafana dashboard?

[ThisIsMissEm]

Hi,

I'm currently using your module to get the metrics out of ECS, but I'm having a bit of trouble making sense of the values and figuring out the graphs for Grafana (Statsd + Graphite + Grafana)

Would you happen to have a Grafana dashboard for the metrics this program produces?

Thanks!
Em

[pcowgill]

@ThisIsMissEm Hi! We don't have Grafana set up for our statsd stats. We're using Librato and Datadog for that.
@ecstasy2 Maybe you can comment?

[ThisIsMissEm]

Ah, so, I'm guessing DataDog is just automatically representing them in a certain manner?

I ended up deciding in the end that container level metrics usually aren't useful, and opted for application metrics instead.

Container level metrics seem only important for monitoring resource utilisation and doing capacity planning; However, if I'm to do that, then I'd really want to be comparing allocated resources of a Kubernetes service, versus the amount of resources the containers for that service regularly use.

Rather than to just be monitoring things like CPU and Memory for the purposes of "seeing something wrong", which is commonly done on server-level, when we used to run VPS's or VMs, instead of containers, where multiple applications where running on the one machine without any form of isolation. However, in a container environment, you have isolation, so instead you'll detect issues through your healthchecks, and noise-neighbour problem becomes a concern for the cluster/container scheduler, not for the devops person trying to debug issues.

At least, this is my now more evolved thinking; I'd definitely be interested in hearing other perspectives on monitoring and containers.

[ThisIsMissEm]

Here's a short article on these thoughts, in a more expanded manner: https://medium.com/@thisismissem/thoughts-on-monitoring-docker-containers-251d7347c775#.duhvlrddk

…

On 10 Mar 2017, at 7:39 PM, Paul Cowgill ***@***.***> wrote: @ThisIsMissEm Hi! We don't have Grafana set up for our statsd stats. We're using Librato and Datadog for that. @ecstasy2 Maybe you can comment? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.