How Do I Set the Maximum Number of Sessions When Adding an Alarm Rule on Cloud Eye?
After connecting to a database, run the following SQL statement to check the maximum number of concurrent sessions globally:
1 |
show max_active_statements;
|
Go to the Cloud Eye console and set the threshold to 70% to 80% of the obtained value. For example, if the value of max_active_statements is 80, set the threshold to 56 (80 x 70%).
Procedure:
- Go to the Clusters page on the GaussDB(DWS) management console.
- Click View Metric in the Operation column of the target cluster to go to the Cloud Eye console.
- Click
in the upper left corner on the displayed page and click Create Alarm Rule of the target cluster.
- Set Method to Configure manually, Metric Name to Session Count, Alarm Policy to 56, and Alarm Severity to Major. Then click Create.
Cluster Management FAQs
- What Do I Do If Creating a GaussDB(DWS) Cluster Failed?
- How Can I Clear and Reclaim the Storage Space?
- Can I Switch My Cluster Nodes to Another Region After Purchase?
- Why Did the Used Storage Shrink After Scale-out?
- How Do I View Node Metrics (CPU, Memory, and Disk Usage)?
- Does GaussDB(DWS) Support BMS?
- How Is the Disk Space or Capacity of GaussDB(DWS) Calculated?
- What Are the gaussdb and postgres Databases of GaussDB(DWS)?
- How Do I Set the Maximum Number of Sessions When Adding an Alarm Rule on Cloud Eye?
- What Should I Do If the Scale-out Check Fails?
- When Should I Add CNs or Scale out a cluster?
- What Are the Scenarios of Resizing a Cluster, Changing the Node Flavor, Scale-out, and Scale-in?
- How Should I Select from a Small-Flavor Many-Node Cluster and a Large-Flavor Three-Node Cluster with Same CPU Cores and Memory?
- What Are the Differences Between Cloud SSDs and Local SSDs?
- What Are the Differences Between Hot Data Storage and Cold Data Storage?
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more