a. Install docker. b. docker run --name=mesos-prometheus-exporter -p 9105:9105 prom/mesos-exporter -exporter.scrape-mode=master -exporter.url=http://${COREOS_PRIVATE_IPV4}:5050 Luck!
---------------------------------------- From: "June Taylor" <[email protected]> Sent: Friday, April 15, 2016 11:44 PM To: [email protected] Subject: Re: Prometheus Exporters on Marathon Thanks for the tip - I am not familiar with Golang and just installed whatever came from Ubuntu's packages. I see that is 1.2.1, so I will check out a newer version. Thanks, June Taylor System Administrator, Minnesota Population Center University of Minnesota On Fri, Apr 15, 2016 at 8:36 AM, Dick Davies <[email protected]> wrote: You are probably building on an older version of Golang - I think the Timeout attribute was added to http.Client around 1.5 or 1.6? On 15 April 2016 at 13:56, June Taylor <[email protected]> wrote: > David, > > Thanks for the assistance. How did you get the mesos-exporter installed? > When I tried the instructions from github.com/mesosphere/mesos-exporter, I > got this error: > > june@-cluster:~$ go get github.com/mesosphere/mesos-exporter > # github.com/mesosphere/mesos-exporter > gosrc/src/github.com/mesosphere/mesos-exporter/common.go:46: unknown > http.Client field 'Timeout' in struct literal > gosrc/src/github.com/mesosphere/mesos-exporter/master_state.go:73: unknown > http.Client field 'Timeout' in struct literal > gosrc/src/github.com/mesosphere/mesos-exporter/slave_monitor.go:56: unknown > http.Client field 'Timeout' in struct literal > > > Thanks, > June Taylor > System Administrator, Minnesota Population Center > University of Minnesota > > On Fri, Apr 15, 2016 at 4:29 AM, David Keijser <[email protected]> > wrote: >> >> 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 >> > >> >> > > > >
