Issue Description
John is a DevOps engineer at his company, responsible for managing multiple application platforms. As these applications run for extended periods and the team size grows, disk space becomes insufficient, and the systems face prolonged high loads.
Despite regular checks on the applications, John repeatedly faces questions from business users such as "Crash again! Why?"and "Why can't we access the platform?"
John is troubled and seeks ways to detect these platform issues and address underlying risks.
Solution
John connects these applications to FineOps, where he can configure alert rules and notification methods by using the Alert function.
FineOps sends email alerts to John when it detects a rule being triggered (for reasons such as high node loads).
John can now resolve these potential issues of application platforms before they impact businesses.
You can apply the built-in default alert rules to all O&M projects.
You (the admin) can customize the alert triggering conditions (including the exception duration required to trigger alerts).
It records alert tasks triggered by exceptions that occur in O&M projects.
By reviewing alert records, you (the admin) can obtain key metrics and detailed information, such as alert occurrence time, the alert type, and the source project.
You (the admin) can be notified of exceptions that trigger alerts through various channels.
Channels include emails, Webhook, WeCom notification, WeCom chatbot, DingTalk chatbot, and Lark chatbot.
1. The alerting system relies on monitoring metrics on the monitoring dashboard. Ensure the prerequisites of using the monitoring dashboard are met before using the Alert function. For details, see Prerequisites of Using Monitoring Dashboards.
2. The alerting system relies on the Alertmanager component of FineOps. Ensure this component under Platform Management > O&M Component runs normally.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy