Runtime Information of TIBCO ActiveMatrix Administrator (Collected in Real-time)

 

Runtime Information of TIBCO ActiveMatrix Administrator
[AMXAdminTask] 04 Apr 2024 16:16:41  INFO - Admin Info:
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Time taken to ping Admin: 0.022 seconds
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Time for which Admin is up: 0 days, 5 hours, 36 minutes, 8 seconds
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Time taken for Admin to start up: 03 minutes, 19 seconds
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Time taken to ping the Database: 0.001 seconds
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Time taken to ping Qin Notification Server: 49ms
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Admin suspend state: Unsuspended
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Admin readOnly state: Write
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Admin suspend/readOnly description:
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Is this Admin Qin Notification Group leader: true
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Number of Notifications processed by Admin: 4104
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Number of Runtime Artifacts in Admin Staging Area: 47 (RDA files: 47, ZIP files: 0)
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Admin Entities:
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Entities Total Last Modified/Deployed On
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Environments 2 02 Apr 2024 12:25:27,160
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Hosts 14 03 Apr 2024 12:42:39,733
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Nodes 6 04 Apr 2024 11:38:11,005
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Applications 9 03 Apr 2024 13:45:21,048
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Resource Templates 5 03 Apr 2024 12:10:54,597
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Resource Instances 83 N/A
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO - Application Templates 1 02 Apr 2024 15:08:51,766
[AMXAdminTask] 04 Apr 2024 16:16:41 INFO -

Above CLI Output snippet shows the runtime information of TIBCO ActiveMatrix Administrator, collected in real-time as Enterprise Deployment Health Check was being executed, notably:

  1. Time taken to ping the TIBCO ActiveMatrix Administrator (the CLI JVM that runs the Enterprise Deployment Health Check is also a client to the TIBCO ActiveMatrix Administrator).
  2. Time for which the TIBCO ActiveMatrix Administrator is up.
  3. Time taken for the TIBCO ActiveMatrix Administrator to start (this includes the time taken to start the web application of the TIBCO ActiveMatrix Administrator that is deployed on SystemNode).
  4. Time taken for the TIBCO ActiveMatrix Administrator to ping the backend database.
  5. Time taken for the TIBCO ActiveMatrix Administrator to ping the Notification/Qin server.
  6. Whether or not the TIBCO ActiveMatrix Administrator is responsible for processing all the Qin notifications, denoted by “is a Qin leader”.
  7. Number of Qin notifications processed by the TIBCO ActiveMatrix Administrator since restart.
  8. Number of Runtime artifacts pending in the TIBCO ActiveMatrix Administrator staging area yet to be delivered to or processed by the TIBCO ActiveMatrix Runtime.
  9. Listing of the Entities organized by type, detailing the count and when the Entity was Deployed or Last Modified.

Depending on the selection of the “Options” targets, the runtime information may not be in the CLI output. For example, if you run Enterprise Deployment Health Check as follows, the runtime information is not shown:

ant -f enterprise_healthcheck_build.xml do.ping health.ent 

or

ant -f enterprise_healthcheck_build.xml test.deploy he

If a report file is generated at the end of Enterprise Deployment Health Check invocation, it contains detailed information related to above output under the <adminInfo> element.