Google Cloud Spanner Details Test
Spanner is a fully managed, mission-critical database service that offers transactional consistency at global scale, automatic, synchronous replication for high availability, and support for two SQL dialects: GoogleSQL (ANSI 2011 with extensions) and PostgreSQL. Spanner is designed to handle massive amounts of data across multiple regions, providing high availability and performance. A distributed clock called TrueTime guarantees transactions are strongly consistent even across multiple regions. Data is automatically split for scalability and replicated using a synchronous Paxos-based scheme to ensure availability.
Storage space contentions and excessive CPU utilization on a Spanner instance can result in the loss of critical data, make reliability questionable. To avoid this, administrators should keep a close watch on the space usage of each Spanner instance in the Google Cloud project, proactively detect a space crunch, and promptly resolve it. This is where the Google Cloud Spanner Details test helps. This test auto-discovers all the Spanner instances in the Google Cloud project and monitors the readiness and space usage of each instance. Alerts are promptly sent out if any instance is in unknown state or is running out of space.
Note:
This test will report metrics only if the Cloud Spanner API is enabled in the target Google Cloud project. If you want to know how to turn on a service API in the Google Cloud project, refer Enabling Service APIs.
Target of the test : Google Cloud
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each Spanner instance in the Google Cloud project
Parameters | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Private Keyfile Name |
To connect to the Google Cloud Project in which the services are running, the eG agent requires a private key of a service account with Compute Viewer, Monitoring Viewer, and Cloud Asset Viewer roles in the target project. If a service account pre-exists in the project, then you can download the private key as a JSON file. Save this JSON file in the <eG_Install_Dir>/agent/lib folder and provide the name of that file against this parameter. However, if no such service account pre-exists, you will have to create one for monitoring the project. To know how to create a service account and download its private key, refer to How does eG Enterprise Monitor Google Cloud?. |
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:
|
Measurement | Description | Measurement Unit | Interpretation | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Instance status |
Indicates the current status of this Spanner instance. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the current status of this Spanner instance. The graph of this measure however, represents the status of each instance using the numeric equivalents only. |
||||||||||
Database status |
Indicates the current status of a database on this Spanner instance. |
|
The values reported by this measure and its numeric equivalents are mentioned in the table below:
Note: By default, this measure reports the Measure Values listed in the table above to indicate the current status of database. The graph of this measure however, represents the status of each database using the numeric equivalents only. The detailed diagnosis of this measure reveals the name of database and time stamp at which the database is created. |
||||||||||
Nodes |
Indicates the number of nodes in this Spanner instance. |
Number |
|
||||||||||
Version retention period |
Indicates the retention period configured for this Spanner instance. |
Hours |
|
||||||||||
Backup storage used |
Indicates the amount of backup storage used by this Spanner. |
MB |
A high value for this measure is a cause for concern. |
||||||||||
Smoothed CPU utilization |
Indicates the average percentage of the CPU resources consumed by the this instance during the lat 24 hours. |
Percentage |
The value reported by this measure helps administrators to create alerts and analyze CPU usage over long period of time, for example, 24 hours. |
||||||||||
CPU utilization |
Indicates the average percentage of CPU utilized by this instance. |
Percentage |
A low value is desired for this measure. |
||||||||||
Total sessions |
Indicates the total number of sessions established from client applications to this Spanner instance. |
Number |
|
||||||||||
Total storage |
Indicates the total amount of storage allocated to this Spanner instance. |
GB |
|
||||||||||
Storage used |
Indicates the amount of storage that is utilized by this Spanner instance. |
GB |
|
||||||||||
Storage utilization |
Indicates the percentage of storage utilized by this Spanner instance. |
Percent |
A value close to 100 for this measure denotes that the Spanner instance is running short of storage. |
||||||||||
Total queries |
Indicates the total number of queries processed by this Spanner instance. |
Number |
|