Monitoring & Alters
The MegaEase Cloud platform can host users' servers, support rapid deployment and management of common software service and cloud-native applications, and allow users to obtain a low-cost, high-availability cloud-native platform that is not locked by the platform.
This document introduces the basic operations of the MegaEase Cloud platform, including the monitoring and alerts.
Customize Dashboard
First, you should create a dashboard. The dashboard is a stage to display your chart panels.
You can create a dashboard by using the following two entrances.
A name is the only thing you need to offer when creating a dashboard.
After submitting, the newly created dashboard will be selected and you can see it in the drop list.
Then you can click the “New Panel” button to create a new chart panel.
In the “New Panel” dialog, the left part is a preview area and the right part is a form area. You can use the form area to adjust a chart’s configurations and preview it in the preview area instantaneously.
The form area contains the following inputs:
- Panel Title: This is the title that you want to give to the new chart.
- Category: This determines the services and metrics you can choose from. Candidate values include MySQL, ElasticSearch, Redis, Zookeeper, Kafka, MongoDB, Kubernetes, Prometheus, DockerApp, Docker, Host.
- Service: This determines which service’s data you want to display in the chart.
- Chart Type: This determines the display style of the chart. Candidate values include: “Time-Series Chart”, “Zoom-Time-Series Chart”, “Bar Chart”, “Stack-Bar Chart”, “Line-Stack Chart”, “Pie Chart”.
- Metrics: This determines what data you want to display in the chart. Each metric name defines a separate time series of data. A maximum of 5 metrics are allowed to be selected at the same time.
After submitting, you can see the newly created chart panel in the dashboard.
Multiple panels can be created in a single dashboard. Multiple dashboards can be created to group different panels.
Alter Rules
You will get some built-in alert rules after deploying a new instance.
You can disable or edit the built-in alert rules, but you can not delete them.
You can also create customized new alert rules.
First, click the “Add Rule” button. Then you will get a dialog like the following.
There are some inputs in the dialog:
- Status: This determines whether the rule is enabled.
- Name: This is the name you want to give to the new alert rule.
- Level: This determines the priority of the rules. Different levels mean different frequencies of notifications being sent.
- Description: This is the message that will be sent if the alert rule is triggered.
- Resolved Description: This is the message that will be sent if the alert rule is no longer triggered.
- Metrics: This determines the details of how an alert will be triggered, such as which metric will be used and how it will be used.
The “Metrics” field itself is a sub-form. With different values for the "Type" field, the form will have a different appearance.
When the type is Default, you can use WebUI to build your trigger logic.
When the type is Prometheus, you can write PromQL directly to express your trigger logic.
There are some common inputs for different types:
- Count: This determines the minimum count of the metric data to be matched before an alert rule is triggered.
- Duration: This determines the time window used to evaluate metric data matching. The unit of time is the second.
Once you have created an alert rule, you will see it in the list of alert rules.
Unlike the built-in alert rules, for customized alert rules, in addition to being able to disable or edit them, you can also delete them.
The editing operation is similar to the creating operation and will not be repeated here.
