Flashduty is a one-stop alerting platform whose core capability is event On-call: integrate with monitoring systems across cloud, on-premises, open-source, and commercial environments; collect alert events; then reduce noise and dispatch them uniformly. Last year, we expanded Flashduty with an alert engine that can connect to internal storage systems and evaluate alert conditions.
The alert engine makes Flashduty's alerting capability more complete. Flashduty can now generate alert events, not only receive them passively. A company usually has multiple monitoring systems. Grafana can help unify visualization, and Flashduty can help unify alerting.
However, the Flashduty alert engine had one missing piece: if the engine itself has a problem, related data sources can no longer generate alerts. You can use systemd to restart the process automatically or deploy multiple monitedge instances for high availability, but one capability was still missing: alerting when the engine disconnects. We have now added it.
As shown above, we added a tab called "Engine Offline Alert" in the Alert Engine menu. It manages rules for alerting when engines disconnect. Click New to create an engine offline alert rule:
The fields are prefilled with defaults and can be adjusted based on your environment. Most fields are self-explanatory; fields with a question-mark icon provide tooltip explanations. You can keep the defaults and only configure which workspace should receive the alert. Once the event enters the workspace, actual notification depends on that workspace's dispatch rules.
With this addition, Flashduty can automatically send alerts when an alert engine disconnects, so maintainers can respond quickly. This cloud-and-edge alerting mechanism improves availability for Flashduty alert engines. You are welcome to try it; signup includes a two-week free trial: https://flashcat.cloud/product/flashduty/.
