Sure. there is not a lot to it though. So we have simple service file like this
/usr/lib/systemd/system/mesos_exporter.service ``` [Unit] Description=Prometheus mesos exporter [Service] EnvironmentFile=-/etc/sysconfig/mesos_exporter ExecStart=/usr/bin/mesos_exporter $OPTIONS Restart=on-failure ``` and the sysconfig is just a simple /etc/sysconfig/mesos_exporter ``` OPTIONS=-master=http://10.4.72.253:5050 ``` - or - /etc/sysconfig/mesos_exporter ``` OPTIONS=-slave=http://10.4.72.177:5051 ``` On Thu, Apr 14, 2016 at 12:22:56PM -0500, June Taylor wrote: > David, > > Thanks for the reply. Would you be able to share your configs for starting > up the exporters? > > > Thanks, > June Taylor > System Administrator, Minnesota Population Center > University of Minnesota > > On Thu, Apr 14, 2016 at 11:27 AM, David Keijser <[email protected]> > wrote: > > > We run the mesos exporter [1] and the node_exporter on each host directly > > managed by systemd. For other application specific exporters we have so far > > been baking them into the docker image of the application which is being > > run by marathon. > > > > 1) https://github.com/mesosphere/mesos_exporter > > > > On Thu, 14 Apr 2016 at 18:20 June Taylor <[email protected]> wrote: > > > >> Is anyone else running Prometheus exporters on their cluster? I am stuck > >> because I can't get a working "go build" environment right now. > >> > >> Is anyone else running this directly on their nodes and masters? Or, via > >> Marathon? > >> > >> If so, please share your setup specifics. > >> > >> Thanks, > >> June Taylor > >> System Administrator, Minnesota Population Center > >> University of Minnesota > >> > >
signature.asc
Description: PGP signature
