Re: Feature request: Include state of Agent (UP/DRAINING) in Get_Agents Response

[Benjamin Bannier <be...@mesosphere.io>]

Hi Sachin,

> I would like to make a feature request to include maintenance state of the agent as a part of response of Operator HTTP API Get_Agents call.


we currently already have a number of maintenance related calls, e.g., the information you are after should be available through `GET_MAINTENANCE_STATUS`. This not only allows users to query the information they are after in a low-overhead way, but also mirrors the v0 HTTP API. Does that work for you?


Cheers,

Benjamin

Re: Feature request: Include state of Agent (UP/DRAINING) in Get_Agents Response

[Sachin Sharma <sa...@uber.com>]

Hi Benjamin,

Thanks for your reply. I am aware of GET_MAINTENANCE_STATUS call. I agree
it is a light-weight, low overhead call.

*GET_AGENTS*
> This call retrieves information about all the agents known to the master.


But what I am trying to say is it would be good to have all agent related
information in the GET_AGENTS response. GET_AGENTS response has a lot of
fields describing the agent state. Since "maintenance state" is also
contributes to an agent state, why not make it a part of GET_AGENTS
response?

Thank you,
Sachin

On Sun, Sep 2, 2018 at 2:03 PM, Benjamin Bannier <
benjamin.bannier@mesosphere.io> wrote:

> Hi Sachin,
>
> > I would like to make a feature request to include maintenance state of
> the agent as a part of response of Operator HTTP API Get_Agents call.
>
>
> we currently already have a number of maintenance related calls, e.g., the
> information you are after should be available through
> `GET_MAINTENANCE_STATUS`. This not only allows users to query the
> information they are after in a low-overhead way, but also mirrors the v0
> HTTP API. Does that work for you?
>
>
> Cheers,
>
> Benjamin
>