Re: Reservation status monitoring

The agents tab in Mesos WebUI should have a table for per role reservations. This is a new feature, so you might need to upgrade to the latest version to get it. On Tue, Jan 16, 2018 at 9:23 PM, 박도형 wrote: > Hi Folks, > > > > Is there a easy way to see the current overall

Reservation status monitoring

Hi Folks,   Is there a easy way to see the current overall status of reservation of resources in Mesos Master? I want to monitor status such as reserved resources per agent or per role with the Mesos Web UI.   DH Park.   Dohyeong Park, Engineer Cloud Platform Group, Mobile R Office

Re: Mesos Cluster Monitoring

t;user@mesos.apache.org<mailto:user@mesos.apache.org>> Date: Thursday, July 27, 2017 at 9:07 AM To: "user@mesos.apache.org<mailto:user@mesos.apache.org>" <user@mesos.apache.org<mailto:user@mesos.apache.org>> Subject: RE: Mesos Cluster Monitoring Hi there I am using

RE: Mesos Cluster Monitoring

Hi there I am using plugins from this repo for monitoring Master servers https://github.com/HariSekhon/nagios-plugins For slaves I use standard Nagios plugins (Memory, disk, etc.) Best regards From: Dharama Rao Sent: četvrtak, 27. juli 2017. 15:03 To: user@mesos.apache.org Subject: Mesos

Mesos Cluster Monitoring

Hi Team, We have a ask to monitor Mesos master , Slaves and Zookeeper using nagios. Do you have any suggestions for us? I have gone through web, but not finding appropriate guide for Setting up nagios on DCOS mesos. Could you please guide me here? Thanks & Regards, Dharama Rao, 470-589-8123.

RE: Cadvisor and Mesos: cgroup monitoring

My bad. I forgot to restart the tasks. It works fine. Thanks again. De : haosdent [mailto:haosd...@gmail.com] Envoyé : lundi 1 août 2016 16:10 À : user <user@mesos.apache.org> Objet : Re: Cadvisor and Mesos: cgroup monitoring Hi, which mesos version you used? cgroups/devices is available

Re: Cadvisor and Mesos: cgroup monitoring

ces. > > > I will try snap with the plugin from Roger. > > > Thanks. > -- > *De :* haosdent <haosd...@gmail.com> > *Envoyé :* vendredi 29 juillet 2016 17:30:20 > > *À :* user > *Objet :* Re: Cadvisor and Mesos: cgroup monitorin

RE: Cadvisor and Mesos: cgroup monitoring

: user Objet : Re: Cadvisor and Mesos: cgroup monitoring Hi, you could add `cgroups/devices` into your Mesos Agent isolation flags and restart it. On Fri, Jul 29, 2016 at 10:30 PM, aurelien.de...@gmail.com<mailto:aurelien.de...@gmail.com> <aurelien.de...@gmail.com<mailto:aurelien.de...

RE: Cadvisor and Mesos: cgroup monitoring

and Mesos: cgroup monitoring Hey Aurélien, I'm not sure if using cadvisor is a hard requirement for you, but might I suggest checking out Snap[0]? I recently wrote a Mesos metrics collector[1] that enumerates all running containers on an agent, in addition to other higher level resource

Re: Cadvisor and Mesos: cgroup monitoring

s` > cgroups to identify the cgroups of a process. In your case, devices cgroup > is still set to root `/`. > > Thanks for the answer. > -- > *De :* haosdent <haosd...@gmail.com> > *Envoyé :* vendredi 29 juillet 2016 16:21:07 > *À :* us

Re: Cadvisor and Mesos: cgroup monitoring

to root `/`. > > Thanks for the answer. > -- > *De :* haosdent <haosd...@gmail.com> > *Envoyé :* vendredi 29 juillet 2016 16:21:07 > *À :* user > *Objet :* Re: Cadvisor and Mesos: cgroup monitoring > > >- is there a way to "lin

RE: Cadvisor and Mesos: cgroup monitoring

set to root `/`. Thanks for the answer. De : haosdent <haosd...@gmail.com> Envoyé : vendredi 29 juillet 2016 16:21:07 À : user Objet : Re: Cadvisor and Mesos: cgroup monitoring >- is there a way to "link" the cgroup id to the mesos task id?

Re: Cadvisor and Mesos: cgroup monitoring

>- is there a way to "link" the cgroup id to the mesos task id? The cgroup id you saw is the ContainerId actually. You could get the mapping relations from querying the state endpoint of Mesos agent. >In mesos, this information is set to /, so all my process are shown in the / cgroup. May you

Cadvisor and Mesos: cgroup monitoring

Hello. I'm trying to find a solution to monitor the real usage of my mesos tasks. I don't use docker at all, but I gave a look to cadvisor. Unfortunatly, cadvisor uses ps and the device information to determine the cgroup ownership of a process. In mesos, this information is set to /, so

Re: Monitoring at container level

For now the easiest solution not requiring changing monitoring infrastructure would be the one proposed by Steven Schlansker so will try to get some information about it from Marathon team. Thanks! On Fri, Jul 8, 2016 at 5:20 AM, <connor@gmail.com> wrote: > Small plug for sn

Re: Monitoring at container level

5:51 AM, David Kesler <dkes...@yodle.com> wrote: >> We use a combination of new relic for application level monitoring and a >> custom python script that scrapes a bunch of stats from the docker socket >> file and throws them into elastic so we can use kibana to

Re: Monitoring at container level

Have you ever tried prometheus + Grafana? Please take a look at https://prometheus.io/docs/visualization/grafana/ to see if it helps. On Fri, Jul 8, 2016 at 5:51 AM, David Kesler <dkes...@yodle.com> wrote: > We use a combination of new relic for application level monitoring and a > c

RE: Monitoring at container level

We use a combination of new relic for application level monitoring and a custom python script that scrapes a bunch of stats from the docker socket file and throws them into elastic so we can use kibana to make graphs. From: Gregory Durham [mailto:gregory.dur...@gmail.com] Sent: Thursday, July

Re: Monitoring at container level

I have been using datadog to monitor my infrastructure. The integration into service discovery has been really helpful for these environments. On Thu, Jul 7, 2016 at 1:37 PM, Steven Schlansker wrote: > We use Graphite and ran into similar problems with huge metric

Re: Monitoring at container level

We use Graphite and ran into similar problems with huge metric namespaces. We use the Singularity framework which provides both the task "request id" (name) and "instance number" (0..N) to the task. So we set our Graphite namespace to be "request-number" e.g. "myservice-3" This has the downside

Re: Monitoring at container level

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 wrote: > Hi Michal, > > Do have a look at sysdig (http://www.sysdig.org). It is basically an > open-source tool which

Re: Monitoring at container level

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

Monitoring at container level

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

Re: Monitoring

://www.youtube.com/watch?v=zlgAT_xFNzU Tomek wt., 19.01.2016 o 21:04 użytkownik Michał Łowicki <mlowi...@gmail.com> napisał: > Hi, > > I've read Mesos Observability Metrics > <http://mesos.apache.org/documentation/latest/monitoring/> which gives > nice overview of cluster's health.

Re: Monitoring

TellApart also has a rather active fork of Diamond (they're working to merge it back upstream ~soonish) that you can take a look at https://github.com/tellapart/Diamond. They use it to monitor both Apache Mesos and Apache Aurora. Twitter has an internal monitoring system, and we have an agent

Re: Monitoring

llapart/Diamond. They use it to monitor both Apache > Mesos and Apache Aurora. > > Twitter has an internal monitoring system, and we have an agent which is > installed via RPM/puppet on each host that scrapes the metrics pages and > pushes data to our time series database. If you want

Re: Monitoring

Subject: Re: Monitoring We're using collectd (https://collectd.org/) to send system metrics to Graphite, and also using the https://github.com/rayrod2030/collectd-mesos collectd plugin to pull stats directly from the Apache Mesos stats endpoint. This works pretty well for us, and seems kin

Re: [Announce] Satellite: Two Sigma's Monitoring, Alerting, and Self-Healing Application for Apache Mesos

Amazing! Thanks for sharing Sunil! On 9 June 2015 at 11:22, Sunil Abraham sunil.abra...@twosigma.com wrote: We are pleased to announce that Two Sigma is open-sourcing Satellite, a Mesos monitoring and alerting application with self-healing capabilities. Satellite makes it easy

[Announce] Satellite: Two Sigma's Monitoring, Alerting, and Self-Healing Application for Apache Mesos

We are pleased to announce that Two Sigma is open-sourcing Satellite, a Mesos monitoring and alerting application with self-healing capabilities. Satellite makes it easy to continuously monitor your cluster, automatically add and remove slaves, and alert you via email or PagerDuty if your cluster

Resource Monitoring-run time optimization

Hi All, Is there a with which in mesos we can monitor the scheduled tasks and their resource access pattern and reschedule the tasks on the optimized resources? For example like NUMA balancer in case of Linux on a NUMA system. Regards, Pradeep

Re: Question on Monitoring a Mesos Cluster

the node load. This however includes all the process running on a node, not only mesos and its tasks. Hope this helps. On Mon, Mar 9, 2015 at 8:16 AM, Andras Kerekes andras.kere...@ishisystems.com wrote: We use the same monitoring script from rayrod2030. However instead

Question on Monitoring a Mesos Cluster

I wrote a python collectd plugin which pulls both master (only if master/elected == 1) and slave stats from the rest api under /metrics/snapshot and /slave(1)/stats.json respectively and throws those into graphite. After getting everything working, I built a few dashboards, one of which displays

Re: Question on Monitoring a Mesos Cluster

have the NOC watch this and simply add more hardware when the number starts getting low. Boy, I cannot wait to read the tidbits of wisdom here. Maybe the development group has more accurate information if not some vague roadmap on resource/process monitoring. Sooner or later, this is going

Re: Question on Monitoring a Mesos Cluster

the number starts getting low. Boy, I cannot wait to read the tidbits of wisdom here. Maybe the development group has more accurate information if not some vague roadmap on resource/process monitoring. Sooner or later, this is going to become a quintessential need; so I hope the deep thinkers are all

Re: Monitoring Mesos slave/master processes

Here we use the wonderfull consul tool as our monitoring and health check dashboard plus some other things. Check it out at consul.io, it's made by Hashicorp. I kinda like it because it's fast, realiable and it is build with huge distributed systems in mind from the ground up. 2014-12-10 1:11

Re: Monitoring Mesos slave/master processes

...@gmail.com: Billy, thanks for the link. It was not easy to tell from the website, but do you get email/text alerts if something goes wrong overnight? On Wed, Dec 10, 2014 at 3:54 AM, Billy Bones gael.ther...@gmail.com wrote: Here we use the wonderfull consul tool as our monitoring and health

Monitoring Mesos slave/master processes

We did this in the past with Nagios, but I was wondering if there was a recommended way from others using in production.

Re: Monitoring Mesos slave/master processes

On Dec 9, 2014, at 3:45 PM, Gary Malouf malouf.g...@gmail.com wrote: We did this in the past with Nagios, but I was wondering if there was a recommended way from others using in production. I wrote a Nagios plugin for it https://github.com/opentable/nagios-mesos