Maria Event Stages Test
Events are named database objects containing SQL statements that are to be executed at a later stage, either once off, or at regular intervals. Events are only executed if the event scheduler is running.
Administrators need to continuously track the status of events that are scheduled, so that they can always tell which events are running as per schedule and which scheduled events are still waiting. The Maria Event Stages test helps in this regard. This test monitors pre-configured tasks at periodic intervals and reports the count of tasks in various stages of progress. To determine which tasks are in what state currently, use the detailed diagnosis of the test.
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 the database 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. |
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 |
---|---|---|---|
Total events |
Indicates the total number of events executed in the database server. |
Number |
|
Running events |
Indicates the number of events that were running during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the thread ID, the event ID, the name of the event, the time stamp at which the event was started, the time stamp at which the event was ended and the name of the source. |
Completed events |
Indicates the number of events that were completed during the last measurement period. |
Number |
|
Nested events |
Indicates the number of events that were waiting for the same resource used by another event. |
Number |
The detailed diagnosis of this measure lists the thread ID, the event ID, the name of the event, the time stamp at which the event was started, the time stamp at which the event was ended and the name of the source. |
Waited events |
Indicates the number of events that were in wait state during the last measurement period. |
Number |
The detailed diagnosis of this measure lists the thread ID, the event ID, the name of the event, the time stamp at which the event was started, the time stamp at which the event was ended and the name of the source. |
Waited events percentage |
Indicates the percentage of events that were in wait state. |
Percentage |
A value close to 100 indicates that the events executing on the database are in wait state. This may be due to a performance bottleneck or connection errors. |