Cassandra SQL Network Test

This test monitors the availability and responsiveness of the Cassandra Database node by emulating a client connecting and executing queries on the Cassandra Database node.

Target of the test : A Cassandra Database node

Agent deploying the test : An internal agent/remote agent

Outputs of the test : One set of results for the target Cassandra Database node being monitored

Configurable parameters for the test
Parameters	Description
Test Period	How often should the test be executed.
Host	The host for which the test is to be configured.
Port	The port on which the specified host listens. By default, this is 9042.
CQL User	Specify the name of the CQL User with the following privileges in this text box: SELECT privilege on the system_traces.sessions table SELECT privilege on the system.peer_events table
CQL Password	Specify the password corresponding to the CQL User.
Confirm Password	Confirm the CQL Password by retyping it in this text box.
Keyspace Name	The name of the keyspace to connect to. The default is “system_schema”. To monitor multiple keyspaces, ensure that the keyspaces are provided as a colon-separated list. Alternatively, you can use the semi-colon(;) as the separator for the keyspaces.
Query	The select query to execute. The default is “select * from keyspaces”. If the target Cassandra Database node is installed as case sensitive, then the value of query parameter should also be case sensitive. If multiple keyspaces are specified in the DATABASE text box, then you will have to provide multiple queries here separated by a semi-colon (;) - for e.g., select * from keyspaces;select * from alarm. Every keyspace being monitored, should have a corresponding Query specification.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Availability	Indicates the availability of the server.	Percent	The availability is 100% when the server is responding to a request and 0% when it is not. Availability problems may be caused by a misconfiguration/malfunctioning of the database server, or because the server has not been started. The availability is 100% when the instance is responding to a request and 0% when it is not. Availability problems may be caused by a misconfiguration/malfunctioning of the database nodde, 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 database instance is unavailable, or if a query to the database fails. In this case, you can check the values of the Connection Availability and Query Availability measures to know what is exactly causing the database node to not respond to requests - is it owing to a connection unavailability? or is it due to a query failure? Using the detailed diagnosis of this measure, you can easily find out unavailability of the server.
Connection response time	The time taken by the database node to respond to a user query. This is the sum total of the response time and query response time.	Seconds	A sudden increase in the connection response time is indicative of a bottleneck at the database node.
Connection availability	Indicates whether the database connection 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 SQL 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.
Query availability	Indicates whether the database query 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 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 database node unavailability.
Response time	Indicates the time taken by the database connection.	Seconds	A high value could indicate a connection bottleneck. Whenever the 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.
Query response time	Indicates the time taken for query execution.	Seconds	A high value could indicate that one/more queries to the database are taking too long to execute. Inefficient/badly designed queries to the database often run for long periods. If the value of this measure is higher than that of the Connection response time measure, you can be rest assured that long running queries are the ones causing the responsiveness of the server to suffer.
No of records	Indicates the number of records fetched from the database node.	Number	The value 0 indicates that no records are fetched from the database node.