[Hawkular-dev] scope of the agent design

[Heiko W.Rupp]

On 16 Mar 2015, at 20:07, John Sanda wrote:

> For monitoring purposes, do we really need to write an agent? Should 
> we just leverage existing tools/libraries? I previously cited three

(Re)using all those tools is fine and certainly desired, but the issue 
is less
about what some random tool uses to collect metrics inside an app, but
rather how to access and transport them. Using JMX like in the good ol'
days is certainly a way. Or using the Jolokia Java agent. But still 
someone
needs to talk to them.

Writing a subsystem for inside Wildfly to actively report/submit data
is in fact an (embedded) agent. Not a general purpose one.

We already have converters from collectd, gmon and a few other
protocols into Hawkular(-metrics). So yes, they should all be allowable
as input.

And then we will have more specialized use cases that most probably go 
much
further than just submitting some metrics to the Hawkular(-metrics) 
server.
In this case some more specialized code may be needed too.