4:55 p.m.
I just added something else that Heiko and I talked about.
This agent now installs a MetricStorage object in JNDI (which is what this log message
means):
2015-03-31 17:43:32,025 INFO [org.hawkular.agent.monitor] (MSC service thread 1-4)
HAWKMONITOR010003: JNDI binding [java:global/hawkular/agent/monitor/metrics]: bound to
object of type [org.hawkular.agent.monitor.scheduler.storage.MetricStorage]
So this (should) mean in anyone's app that is deployed in a Wildfly instance that has
our agent installed, you can do something like:
@Resource("java:global/hawkular/agent/monitor/metrics")
MetricStorage metricStorage;
Once you have that, you can use it to store your own metrics. Something like this:
MetricDataPayloadBuilder data = metricStorage.getMetricDataPayloadBuilder();
data.addDataPoint("my-metric-key", System.currentMillis, 23.846);
data.addDataPoint("my-other-metric-key", System.currentMillis, -1.03);
metricStorage.store(data)
Here's the MetricStorage interface - it is not complex:
https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-m...
This now allows apps to be their own feeds.
NOTE: no inventory stuff is integrated here.
----- Original Message -----
OK, I can report some success.
In our new Hawkular Agent repo [1] I have a new-and-improved
hawkular-wildfly-monitor maven module. It produces the hawkular monitor
subsystem that gets deployed inside Wildfly and can monitor any number of
attributes of any number of wildfly resources (right now I just have it
configured to collect some memory and thread metric data - see [2] for the
subsystem configuration's metricSet definitions).
It isn't baked into kettle, but using Libor's nice maven plugin, when you
build that new agent you can tell maven to install it in your kettle
instance (see [3] for the command to run when building
hawkular-agent/hawkular-wildfly-monitor).
You won't be able to see anything in any nice graphs since kettle is strongly
typed to that pinger thing. But the kettle log file should show many
messages about the data getting pushed into hawkular-metrics. So, it should
be in there.
This hawular agent's sole job is to monitor the wildfly instance it is
running in.
That's all for now. Just wanted to give an early status since I was out last
week.
--John Mazz
[1] https://github.com/hawkular/hawkular-agent
[2]
https://github.com/hawkular/hawkular-agent/blob/master/hawkular-wildfly-m...
[3] mvn
-Dorg.hawkular.wildfly.home=/source/hawkular/kettle/target/wildfly-8.2.0.Final
clean install wildfly-extension:deploy
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev