Take a look at https://github.com/scrapinghub/marathon-apps-collectd-plugin, basically it works like this:
- there is a custom collectd (https://github.com/collectd/collectd) plugin, written in python - the plugin uses docker inspect api to query the MESOS_TASK_ID and MARATHON_APP_ID environment variable for each container - the plugin queries cpu/mem/network stats from docker stats api - collectd sends the (marathon app, task id, stats) data to a storage backend, e.g. graphite, elasticsearch, influxdb, etc. Hope that helps. Shuai On Tue, Jan 12, 2016 at 4:12 AM, Scott Rankin <[email protected]> wrote: > Hi all, > > I’m trying to put together a monitoring system for our > Marathon/Mesos/Docker app infrastructure, and I’m having some trouble > linking between Mesos and Docker. Mesos has a task ID > (like app_auth.6fb24412-af26-11e5-9900-02d62c7c9807), but the only place > that shows up in the Docker container is in the MESOS_TASK_ID environment > variable passed to the Docker containers. I see that the Docker containers > are created using the format mesos-<slaveid>-<something>, but I cannot find > the <something> value anywhere in the metadata from the master or the > slave. > > Am I missing something, or is there any way that I can configure Mesos to > add a label or something to the Docker container so that our monitoring > scripts can tie the Docker container to the Mesos task? > > Thanks! > Scott > > SCOTT *RANKIN* > VP, Technology > > *Motus, LLC* > Two Financial Center, 60 South Street, Boston, MA 02111 > 617.467.1931 (W) | [email protected] <[email protected]> > > > > Follow us on LinkedIn <https://www.linkedin.com/company/motus-llc/> | > Visit us at motus.com <http://www.motus.com/> > > > > This email message contains information that Motus, LLC considers > confidential and/or proprietary, or may later designate as confidential and > proprietary. It is intended only for use of the individual or entity named > above and should not be forwarded to any other persons or entities without > the express consent of Motus, LLC, nor should it be used for any purpose > other than in the course of any potential or actual business relationship > with Motus, LLC. If the reader of this message is not the intended > recipient, or the employee or agent responsible to deliver it to the > intended recipient, you are hereby notified that any dissemination, > distribution, or copying of this communication is strictly prohibited. If > you have received this communication in error, please notify sender > immediately and destroy the original message. > > Internal Revenue Service regulations require that certain types of written > advice include a disclaimer. To the extent the preceding message contains > advice relating to a Federal tax issue, unless expressly stated otherwise > the advice is not intended or written to be used, and it cannot be used by > the recipient or any other taxpayer, for the purpose of avoiding Federal > tax penalties, and was not written to support the promotion or marketing of > any transaction or matter discussed herein. >
