| Measurement |
Description |
Measurement Unit |
Interpretation |
| availability |
Indicates whether the cluster node is responding to requests. |
Percent |
The availability is 100% when the cluster node is responding to a request and 0% when it is not. Availability problems may be caused by a misconfiguration/malfunctioning of the node, or because the node is using an invalid user account. Besides the above, this measure will report that the server is unavailable even if a connection to the node is unavailable, or if a query to the database fails. In this case, you can check the values of the DB connection availability and Query processor availability measures to know what is exactly causing the node to not respond to requests - is it owing to a connection unavailability? or is it due to a query failure? |
| responseTime |
Indicates the time taken by this node to respond to a user query. This is the sum total of the connection time and query execution time. |
Seconds |
A sudden increase in response time is indicative of a bottleneck at the node. This could even be owing to a connection delay and/or long running queries to the database. Whenever the value of this measure is high, it would be good practice to compare the values of the DB connection response time and Query execution time measures to zero -in on the root cause of the poor responsiveness of the server - is it because of connectivity issues? or is it because of inefficient queries? |
| connAvailable |
Indicates whether the database connection to this node is available or not. |
Percent |
If this measure reports the value 100, it indicates that the database connection is available. The value 0 on the other hand indicates that the database connection is unavailable. A connection to the database may be unavailable if the database is down or if the database is listening on a port other than the one configured for it in the eG manager or owing to a poor network link. If the Node availability measure reports the value 0, then, you can check the value of this measure to determine whether/not it is due to the unavailability of a connection to the server. |
| dbConnResTime |
Indicates the time taken to connect to the cluster node. |
Seconds |
A high value could indicate a connection bottleneck. Whenever the Node response time of the measure soars, you may want to check the value of this measure to determine whether a connection latency is causing the poor responsiveness of the node. |
| quryPrcsAvailability |
Indicates whether the query to this node is executed successfully or not. |
Percent |
If this measure reports the value 100, it indicates that the query executed successfully. The value 0 on the other hand indicates that the query failed. In the event that the Node availability measure reports the value 0, check the value of this measure to figure out whether the failed query is the reason why that measure reported a node unavailability. |
| quryExeTime |
Indicates the time taken for query execution on this node. |
Seconds |
A high value could indicate that one/more queries to the node are taking too long to execute. Inefficient/badly designed queries to the database often take too long to execute. If the value of this measure is higher than that of the Connection time measure, you can be rest assured that long running queries are causing the node to respond slowly to requests. |
| noOfRecords |
Indicates the number of records fetched from the database for this node. |
Number |
The value 0 indicates that no records are fetched from the database. |