Maria Database Size Test
Storage space contentions on a database can result in the loss of critical data. To avoid this, administrators should keep a close watch on the space usage/growth rate of each database, proactively detect a space crunch, and promptly resolve it. This is where the Maria Database Size test helps. This test auto-discovers all the databases on the Maria Database server and monitors the size of each database. Alerts are promptly sent out if any database is running out of space. In the event of a space crunch in a database, you can also use this test to figure out what is causing the space drain - documents? or index files?
Target of the test : A Maria Database server
Agent deploying the test : An internal/remote agent
Outputs of the test : One set of results for each database on the server being monitored.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The IP address of the Maria Database server. |
Port |
The port on which the server is listening. |
Database |
Specify the name of the database that is to be monitored on the target Maria Database server. |
User and Password |
The eG agent has to be configured with the credentials of a user who has server-wide PROCESS and SELECT privileges on the monitored Maria Database server. To know how to create such a user, refer to Configuring the eG Agent with Access Privileges |
Confirm Password |
Confirm the password by retyping it here. |
SSL |
This indicates that the eG agent will communicate with the Maria Database via HTTPS or not. By default, this flag is set to No, as the target Maria database is not SSL-enabled by default. If the target database is SSL-enabled, then set this flag to Yes. |
Verify CA |
If the eG agent is required to establish an encrypted connection with the target Maria Database server by authenticating the server's identity through verifying the server CA certificate, set Verify CA flag to Yes. By default, this flag is set to No. |
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Database size |
Indicates the total size of this database. |
MB |
|
Data size |
Indicates the total size of all the documents and padding stored in the database. |
MB |
The value of this measure will decrease when you delete documents, but will not decrease when documents shrink because the space used by the original document has already been allocated (to that particular document) and cannot be used by other documents. Alternatively if a user updates a document with more data, the value of this measure will remain the same as long as the new document fits within its originally padded pre-allocated space. |
Index size |
Indicates the total size of all indexes created on this database. |
MB |
If the value of this measure is equal to the Database size measure, then it indicates that the indices are consuming the entire space in the database. Comparing the value of this measure with that of the Data size measure helps administrators to figure out whether documents are consuming the maximum space in the database or the indices are consuming the maximum amount of database space. |
Growth rate |
Indicates the rate at which the size of this database is growing. |
MB/Sec |
The value of this measure is calculated using the following formula: (Data size + Index size) of the current measurement period (-) (Data size + Index size) of the previous measurement period A consistent increase in the value of this measure is a cause for concern, as it indicates a steady growth in database size. |