forked from docs/docsportal
32 lines
1.3 KiB
ReStructuredText
32 lines
1.3 KiB
ReStructuredText
======
|
|
Alerts
|
|
======
|
|
|
|
Alerta is the component of the ApiMon that is designed to integrate alerts
|
|
from multiple sources. It supports many different standard sources like Syslog,
|
|
SNMP, Prometheus, Nagios, Zabbix, etc. Additionally any other type of source
|
|
using URL request or command line can be integrated as well.
|
|
|
|
Native functions like correlation and de-duplication help to manage thousands of
|
|
alerts in transparent way and consolidate alerts in proper categories based on
|
|
environment, service, resource, failure type, etc.
|
|
|
|
Alerta is hosted on https://alerts.eco.tsi-dev.otc-service.com/ .
|
|
The authentication is centrally managed by OTC LDAP.
|
|
|
|
The Zulip API was integrated with Alerta, to send notification of errors/alerts
|
|
on Zulip stream.
|
|
|
|
Alerts displayed on OTC Alerta are generated either by Executor, Scheduler,
|
|
EpMon or by Grafana.
|
|
|
|
- “Executor alerts” focus on playbook results, whether playbook has completed
|
|
or failed.
|
|
- “Grafana alerts” focus on breaching the defined thresholds. For example API
|
|
response time is higher than defined threshold.
|
|
- "Scheduler alerts" TBD
|
|
- "EpMon alerts" provide information about failed endpoint queries with details
|
|
of the request in curl form and the respective error response details
|
|
|
|
.. image:: training_images/alerta_dashboard.png
|