You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Alexander Rojas <al...@mesosphere.io> on 2015/06/04 13:51:53 UTC
/state.json /sumary-state /slaves /tasks.json endpoints
If you use any of these endpoints: /state.json /sumary-state /slaves /tasks.json can you provide feedback in how you use them, if the information provided is adequate? too much, too little?
Re: /state.json /sumary-state /slaves /tasks.json endpoints
Posted by Brian Hicks <br...@brianthicks.com>.
There was an appropriate amount of information present for developing
mesos-consul[1]. We use it in that project to forward Mesos app
information to Consul services for DNS purposes.
It would be *really* handy to have a webhook system for this
information. Currently, mesos-consul polls state.json at an interval, it
would make our system more robust if it could be notified of changes. I
suspect this would help the mesos-dns project as well.
[1]: https://github.com/CiscoCloud/mesos-consul
On 4 Jun 2015, at 6:51, Alexander Rojas wrote:
> If you use any of these endpoints: /state.json /sumary-state /slaves
> /tasks.json can you provide feedback in how you use them, if the
> information provided is adequate? too much, too little?
Re: /state.json /sumary-state /slaves /tasks.json endpoints
Posted by zhou weitao <zh...@gmail.com>.
I am often using /state.json by the command 'curl -s <IP>:5050/state.json |
python -m json.tool | grep sth' or 'curl -s <IP>:5050/state.json | python
-m json.tool | less'
About if adequate, I think more is better of course, BTW, we need render it
better on WEB-UI. Some real-time report chart is sexy to me. ;-)
2015-06-04 19:51 GMT+08:00 Alexander Rojas <al...@mesosphere.io>:
> If you use any of these endpoints: /state.json /sumary-state /slaves
> /tasks.json can you provide feedback in how you use them, if the
> information provided is adequate? too much, too little?