[Hawkular-dev] scope of the agent design

[Thomas Heute]

We still need:
     - something to monitor the platform, the container... (what is it 
if not a "standalone agent" ?)
     - monitoring non-WF/EAP based servers: Fuse, AMQ... (vert.x...)

Thomas


On 03/12/2015 07:34 PM, John Mazzitelli wrote:
> So what I heard today was we don't want a standalone agent, but we do want something that can be embedded in Wildfly/EAP so it can monitor things running in Wildfly (not just monitor Wildfly itself, but applications running inside wildfly).
>
> That lends itself to supporting customizable modules that can be deployed in Wildfly/EAP as hawkular subsystems.
>
> Can someone give me a quick summary of what Wildfly-Monitor does? https://github.com/hawkular/wildfly-monitor
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev