📩 Email and SMS Alerts
GermainUX alerts notify the appropriate teams when monitored conditions require attention, including breaches of:
|
Category |
Details |
|
|---|---|---|
|
1 |
Technology SLAs |
Technology SLAs |
|
2 |
Business-process and workflow SLAs |
Business-process and workflow SLAs |
|
3 |
User-experience SLAs |
User-experience SLAs |
⚙️ Alert Sources
Alerts can be generated from:
|
Source |
Details |
|---|---|
|
Ingested monitoring data |
Ingested monitoring data |
|
Correlated events and transactions |
Correlated events and transactions |
|
SQL query results |
SQL query results |
|
HTTP or HTTPS actions |
HTTP or HTTPS actions |
|
Other custom analytics and automation conditions |
Other custom analytics and automation conditions |
📚 See
|
Topic |
Link |
|---|---|
|
Configure SLAs |
|
|
SQL Execution Automation |
|
|
HTTP/HTTPS Execution Automation |
💡 How Alerting Works
The standard alerting flow is:
|
Step |
Description |
|---|---|
|
1 |
GermainUX collects or generates a data point. |
|
2 |
The applicable SLA evaluates that data. |
|
3 |
GermainUX detects an SLA breach or another configured condition. |
|
4 |
An Alert Action is triggered. |
|
5 |
The alert message is generated from a configured template. |
|
6 |
The notification is sent by email or SMS to the selected Distribution List. |
Templates, recipients, priorities, and actions can be customized according to the KPI, SLA, environment, severity, or business impact.
Service: Action
Feature Availability: 8.6.0 or later