[Hawkular-dev] Host agent ?

[Lukas Krejci]

IMHO, rather than implement our own, we should try to leverage some of the 
already existing solutions in this area like collectd and only write a simple? 
"proxy" for it that would take its input and send relevant info to metrics, 
inventory and/or other hawkular components. Essentially we should enhance 
ptrans to be a true piece of hawkular glue.

This could even sit as a middleman on a remote machine (or indeed on the 
hawkular server itself) and manage a number of "native" agents.

On Tuesday, February 09, 2016 10:30:12 Thomas Heute wrote:
> With embedded agents, we lost few main features:
>     - Ability to discover servers that are off or not (yet) instrumented
>     - Ability to start servers remotely
>     - Ability to report DOWN availability (other than by lack of UP)
> 
> Should we reintroduce a small (optional ?) host agent ?
> 
> The agent would only fulfill those tasks (+ embedded agent installer) and
> redirect all other tasks to the embedded agents.
> 
> We can address a limited set of platforms (Linux only) to start with, and
> maybe use environment specific features if those exists (Like RHEV-M host
> agent if appropriate)
> 
> WDYT ?
> 
> Thomas