I have had a good experience so far with bosun and scollector with cadvisor. Check it out at bosun.org.
On Friday 8 July 2016, Pradeep Chhetri <pradeep.chhetr...@gmail.com> wrote: > Hi Michal, > > Do have a look at sysdig (http://www.sysdig.org). It is basically an > open-source tool which provides container insights. Maybe your will find > something helpful over there. > > To tackle the case of new metrics for new containers, maybe you should tag > metrics by service-name instead of container id. (Graphite doesn't have > concept of tags but something like opentsdb and influxdb do have. I don't > see a reason to replace graphite for that. You can use your service-name > (which the container is representing) instead of hostname in the metrics > name) > > On Fri, Jul 8, 2016 at 1:18 AM, Michał Łowicki <mlowi...@gmail.com > <javascript:_e(%7B%7D,'cvml','mlowi...@gmail.com');>> wrote: > >> Hi, >> >> Before introducing Mesos we're using mainly Graphite / Grafana. Ideally >> we would like to have metrics per container as an easy way to detect if >> problem touches only single, subset of containers or it's global. >> >> Unfortunately using Graphite for that is far from being perfect. Having >> container identifier as a part of metric has many negative implications >> like having tons of new metrics every release on Marathon (new containers = >> new identifiers). >> >> Investigated InfluxDB so far but project isn't mature enough as still >> components like >> https://github.com/influxdata/telegraf/blob/master/plugins/inputs/statsd/README.md#influx-statsd >> have major blockers: >> >> COMING SOON: there will be a way to specify multiple fields. >> >> >> What do you use to monitor your Mesos clusters and f.ex. to detect that >> some containers are having issues? >> >> -- >> BR, >> Michał Łowicki >> > > > > -- > Regards, > Pradeep Chhetri > -- Thumb typed mail
