Re: [Hawkular-dev] scope of the agent design

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