Event Monitoring for Standard HTAP Instances
Scenarios
Event monitoring provides reporting, query, and alarm functions for event data. You can create alarm rules for both system and custom events. When specific events occur, Cloud Eye generates alarms for you.
Events are key operations on TaurusDB HTAP instances that are stored and monitored by Cloud Eye. You can view events to see operations performed by specific users on specific resources.
Event monitoring provides an API for reporting custom events, which helps you collect and report abnormal events or important change events generated by services to Cloud Eye.
Event monitoring is enabled by default. You can view monitoring details about system events and custom events.
Events for Standard HTAP Instances
HTAP (Standard Edition) is a sub-feature of TaurusDB instances. The alarm notifications of event monitoring for standard HTAP instances are the same as those for TaurusDB instances.
Event Source |
Event Name |
Event ID |
Event Severity |
Description |
Handling Suggestion |
Impact |
---|---|---|---|---|---|---|
TaurusDB |
Faulty DB instance |
TaurusInstanceRunningStatusAbnormal |
Major |
The instance process may be faulty or there may be abnormal tables during instance data synchronization. |
Check whether there are abnormal tables. If there are, repair the abnormal tables. If the fault persists, submit a service ticket. |
Workloads may be affected, or instance data cannot be synchronized. |
DB instance recovered |
TaurusInstanceRunningStatusRecovered |
Major |
The instance is recovered. |
Observe the service running status. |
None |
|
Faulty node |
TaurusNodeRunningStatusAbnormal |
Major |
The node process may be faulty. |
Observe the instance and service running statuses. |
Workloads may be affected. |
|
Node recovered |
TaurusNodeRunningStatusRecovered |
Major |
The node is recovered. |
Observe the service running status. |
None |
Viewing Event Monitoring Data
- Log in to the management console.
- Click
in the upper left corner and select a region and project.
- Click
in the upper left corner of the page and choose Databases > TaurusDB.
- On the Instances page, locate a TaurusDB instance and click its name to access the Basic Information page.
- In the navigation pane, choose HTAP Analysis. Locate an HTAP instance and click View Metrics in the Operation column to go to the Cloud Eye console.
Alternatively, click the HTAP instance name. On the displayed Basic Information page, click View Metrics in the upper right corner.
- Click
to return to the main page of Cloud Eye.
- In the navigation pane, choose Event Monitoring.
- On the displayed Event Monitoring page, all system events of the last 24 hours are displayed by default.
You can also click 1h, 3h, 12h, 1d, 7d, or 30d to view events generated in different periods.
- Locate an event and click View Event in the Operation column to view details about a specific event.
Creating Alarm Rules for Event Monitoring
- Log in to the management console.
- Click
in the upper left corner of the page. Under Management & Governance, click Cloud Eye.
- In the navigation pane, choose Event Monitoring.
- On the event list page, click Create Alarm Rule in the upper right corner.
- On the displayed page, configure parameters as needed.
Table 2 Parameter description Parameter
Description
Name
Specifies the name of the alarm rule. The system generates a random name, and you can change it if needed.
Description
(Optional) Provides supplementary information about the alarm rule.
Enterprise Project
You can select an existing enterprise project or click Create Enterprise Project to create an enterprise project.
Alarm Type
Specifies the alarm type corresponding to the alarm rule.
Trace Type
Specifies the event type of the metric corresponding to the alarm rule.
Event Source
Specifies the service the event is generated for.
Example value: TaurusDB
Monitoring Scope
Specifies the monitoring scope for event monitoring.
Method
Specifies the event creation method.
Alarm Policy
Event Name indicates the instantaneous operations users performed on system resources, such as login and logout.
For details about events supported by Event Monitoring, see Table 1.
You can select a trigger mode and alarm severity as needed.
Clickto enable alarm notification. The validity period is 24 hours by default. If the topics you require are not displayed in the drop-down list, click Create an SMN topic.
Table 3 Alarm notification parameters Parameter
Description
Alarm Notification
Specifies whether to notify users when alarms are triggered. Notifications can be sent by email or text message, or through HTTP/HTTPS request to servers.
Recipient
Specifies the object an alarm notification is to be sent to. You can select the account contact or a topic.- Account contact is the mobile phone number and email address of the registered account.
- Topic is used to publish messages and subscribe to notifications. If the required topic is unavailable, create one first and add subscriptions to it.
For details, see Creating a Topic and Adding Subscriptions.
Validity Period
Cloud Eye sends notifications only within the validity period specified in the alarm rule.
If you set Validity Period to 08:00-20:00, Cloud Eye sends notifications only within 08:00-20:00.
Trigger Condition
Specifies the condition for triggering the alarm notification.
- After the configuration is complete, click Create.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot