vCD Database Test

vCloud Director cells use a database to store shared information. This database must exist before you can complete installation and configuration of vCloud Director software. Long running transactions to the database can keep resources locked unnecessarily and can cause unprecedented delays in processing subsequent transactions. Using this test, you can be proactively alerted to transactions and sessions that have been active for a long time, so that you can quickly deep dive into your database server to know which sessions and transactions have been running for a long time and why.

Target of the test : A vCloud Director Cell

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for the vCloud Director Cell being monitored.

Configurable parameters for the test

Parameter	Description
Test Period	How often should the test be executed.
Host	The host for which the test is being configured.
Port	Specify the port at which the specified host listens in the Port text box. By default, this is NULL.
JMX Remote Port	Here, specify the port at which the JMX listens for requests from remote hosts. Ensure that you specify the same port that you configured in the vmware-vcd-cell file in the /opt/vmware/vcloud-director/binfolder of the vCloud Director.
JNDIName	The JNDIName is a lookup name for connecting to the JMX connector. By default, this is jmxrmi. If you have registered the JMX connector in the RMI registry using a different lookup name, then you can change this default value to reflect the same.
User, Password, and Confirm Password	By default, JMX requires no authentication or security (SSL). This is why, by default, the User and Password parameters are set to none. If JMX requires authentication only (but no security), then ensure that the User and Password parameters are configured with the credentials of a user with read-write access to JMX. To know how to create this user, refer to Pre-requisites for Monitoring vCloud Director. Confirm the password by retyping it in the Confirm Password text box.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Open transactions	Indicates the number of transactions that are currently open in the database.	Number	A consistent rise in the value of this measure could indicate that transactions are running for a long a time; this could imply that one/more transactions are slow and or are not getting completed. This is a cause for concern and warrants an investigation.
Open sessions	Indicates the number of sessions that are currently open in the database.	Number	A consistent rise in the value of this measure could indicate that sessions are not getting closed properly. This is a cause for concern and warrants an investigation.
Transactions	Indicates the time taken for transaction completion.	Secs	A high value indicates that transactions are taking too long to complete. This calls for an investigation into the reason for the slowness.