-
1. Re: Is it possible to monitor each web service method using JON
mazz Jan 22, 2013 11:03 AM (in response to ssroy73)One way you could do it is with the netservices plugin:
http://management-platform.blogspot.com/2012/11/monitoring-ip-endpoints-via-rhq.html
I'm not sure if it fully supports the different HTTP methods (GET, POST, HEAD) but I bet the code could be enhanced easily for that. Code contributions are welcome!
-
2. Re: Is it possible to monitor each web service method using JON
ssroy73 Jan 24, 2013 3:03 AM (in response to mazz)Thanks a lot John.
I installed the plugin where agent is installed. The same is also visible from administration > Agent plugin screen. But I can't see any metrics around this listed anywhere. Will really appreciate any clue.
Thanks a lot.
Best Regards - Roy
-
3. Re: Is it possible to monitor each web service method using JON
mazz Jan 24, 2013 8:38 AM (in response to ssroy73)Did you manually add your endpoints? Because the agent won't be able to auto-discovery any endpoints that you want to monitor (what algorithm could it use to know what endpoint (URL with host/port) you actually want to monitor? - they technically could be anything, anywhere on the 'net).
So, you'll want to go to the GUI, navigate to the platform for your agent and view the Inventory>Children page (I think that's the name). From there, manually add a "HTTPService" or a "PingService" object and follow the screen instructions. See this blurb from the online docs: https://docs.jboss.org/author/display/RHQ45/Inventory#Inventory-Manualdiscovery
If I may hedge my bets here - I can't vouch that this plugin works well. However, the descriptor shows these metrics the HTTPService "should" be collecting:
<metric property="connectTime" units="milliseconds" displayType="summary"
description="The time to connect to the service"/>
<metric property="readTime" units="milliseconds" displayType="summary"
description="The time to transfer the requested content"/>
<metric property="contentLength" units="bytes"
description="The size of the returned content"/>
<metric property="contentAge" units="milliseconds"
description="The declared age of the requested page"/>The PingService is very limited in what it collects (all that does is verify the endpoint is reachable).
I suspect this plugin may need additional code to flesh out its capabilities. It was a prototyped contribution and I can't say much of any testing went into it. This is why I kind of seem like begging to get someone in the community to work on it