Path semantics for pattern READ request should be changed #106
When doing a pattern read request which results in multiple matches, then providing a path doesnt make much sense currently, since it applies on the whole map returned with the MBean names as keys in the first level (see the reference manual for details).
For homogenous reads on similar MBean it would make much more sense to apply the path only on the final value parts (for each MBean matched).
Since pathes are currently not usable with this sort of request, changing the behaviour shouldn't harm much so that it can be done within a minor release.
The text was updated successfully, but these errors were encountered:
It would be nice if described behaviour could be implemented in some of next releases. I am preparing monitoring tool for couple of environments on WebSphere 7.0 and I found out that I can not use pattern read request.
I do not want the whole structure of the response, so what I want to do is:
But it fails with:
On the other hand following request with full mbean name works fine:
I would like to use pattern requests instead of requests with full mbean names because it is easier to transfer to other environments and it is more readable too.
So, it's finished so far. Quite complex beast, but I think it was worth because of the gained flexibility.
In you case you can use
to get to the statistics entries only. Also I recommend to have an eye on https://github.com/rhuss/jolokia-extra which makes access to Websphere (or JSR-77 metrics in genenral) statistic informations much easier.
The feature will be available in 1.2.2 to be released quite soon.