Per the info in USE CASE: count and duration for Tibco proesses, by process. tra file for every process to be monitored. tra file option Jmx.Enabled=true must be set in the. Tibco processes must be run with the standard JMX localhost command-line options: Info-level logging is not great for troubleshooting, but debug-level logging should give reasonable information on how the JMX connection is working, and on what stats objects are being returned from JMX. The other values should work fine with the defaults, only change if there is a use case reason to do so. The port is the only value in monitor.xml that MUST be changed. This extension levarages localhost JMX, so the machine agent running this extension should be on the same OS instance as a Tibco process with JMX enabled. That port number must be configured in monitor.xml for this extension to work. When enabling JMX in Tibco BW, you select the JMX port in the ".tra" file of your Tibco deployment. % mvn -Dtibhawk=/Users/paulbunyan/tibco/bw6/hawk/5.1 -Dappd-ma=/Users/paulbunyan/machine-agent clean package For example, if you have Tibco installed in a directory called /Users/paulbunyan/tibco and an AppDynamics machine agent installed at /Users/paulbunyan/machine-agent, then you build using: Variables are used in the build files to resolve these dependencies. Also, the AppDynamics machine agent is a dependency. To build you must have Tibco dependencies available, they are not available through Maven. Process counts are important because in a BW environment there is usually a fixed thread pool available for running process jobs - high counts mean that jobs are sitting around waiting for an available thread. This extension monitors Tibco BW processes and their sub-processes ("Jobs"), giving count and duration metrics for each. Do not try to build the hawk console monitor in the github repo, it will not build and is as of now just a template. Tibco BW must be run with JMX enabled for this extension to work.Īs of this writing the Hawk Console monitoring capability is not functional, so only the JMX monitor is usable.
0 kommentar(er)
