1 / 16

Alert types

Alert types. EUM Alerts (aka Event Based Alerts) BPM Transaction Alerts RUM Application Alerts RUM Event Alerts RUM Transaction Alerts CI Status Alerts SLA Alerts SLA Status Alerts SLA Forecast Alerts. Glossary.

trujillor
Télécharger la présentation

Alert types

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Alert types • EUM Alerts (aka Event Based Alerts) • BPM Transaction Alerts • RUM Application Alerts • RUM Event Alerts • RUM Transaction Alerts • CI Status Alerts • SLA Alerts • SLA Status Alerts • SLA Forecast Alerts

  2. Glossary • Trigger - a condition or criteria that determines when an alert should be sent • Alert configuration is stored in ODB • event_alert • dashboard_alert • slm_alert • forecast_alert

  3. EUM Alerts overview - triggers • Event Based triggers – an alert is calculated upon discrete samples arrival • Time Based triggers – alert is calculated upon all the samples that arrived during the specified period of time • ‘Sliding window’ calculation principle • Follow-up (positive) alert – is triggered when the conditions that previously triggered the alert are no longer true

  4. EUM Alerts overview – additional • Filters – only specific samples are used in alert calculation • Group-by – the samples used for alert calculation are grouped by the specified criteria and trigger condition is calculated for each group separately • Notification frequency • every trigger occurrence • once in a period of time • once per trigger

  5. EUM Alerts overview – actions • Send to recipient (email, SMS, pager) • Access URLs. • Send SNMP trap. • Run executable file. • Log to Event Viewer application log (Windows only). • Make specified alerts subordinate to this alert • Generate event - CEM

  6. EUM Alerts overview – lifecycle • Alert configuration (Alert Admin UI) • Alert conditions calculation (Alert Rule) • Alert message creation (Alerts Handler) • Notifications (Notifications Handler)

  7. EUM Alerts overview – diagram

  8. EUM Alerts overview – log files configuration (DPS server): • HPBSM\conf\core\Tools\log4j\marble_worker \alerts-rules.properties – alert calculation • HPBSM\conf\core\Tools\log4j\EJB\alerts.properties – alerts actions&notifications log files: • HPBSM\log\alerts\alerts.rules.log • HPBSM\log\alerts\alerts.ejb.log

  9. CI Status Alerts overview – triggers • CI Status Alerts are based on the KPI statuses of CIs in BAC dashboard. • Defined on CMDB CI KPIs, alert is send on CI status changed (i.e. when a KPI Status is changed) • The severity of the alert is based on the CI current status. • Notification templates are provided with BSM and not editable

  10. CI Status to EUM Alerts comparison CI Status Alerts • Templates are attached to alerts • No filters (just on KPIs) • Severity is calculated every trigger • ‘Once per trigger’ NF does not exist • Alert can be defined on multiple CIs EUM Alerts • Templates are attached to Recipients • Filters (on transactions, locations, etc.) • Severity is defined as part of alert config • ‘Once per trigger’ NF exists (except RUM Evt) • Alert is defined on one CI only (application)

  11. CI Status to EUM Alerts comparison CI Status Alerts • No follow-up • No dependencies • No Event Viewer action • No email output for exe actions • SM integration • Business impact + reports in email EUM Alerts • Follow-up alert • Dependencies between alerts • Event Viewer action • Support result output in email for exe action • SM integration is not supported • No Business Impact and reports in email

  12. SLA Alerts overview • Configured in purpose to see that the business IT and applications are met with the their demands and at their pick. • SLM Alerts are configured on tracking periods of SLA (day, week, month, …) • SLA Forecast Alerts’ purpose is to warn the user that the SLA is going to breached

  13. Status Alerts overview - logs configuration (DPS server): • HPBSM\conf\core\Tools\log4j\marble_worker \cialerts.properties – alert calculation • HPBSM\conf\core\Tools\log4j\EJB\alerts.properties – alerts actions&notifications log files: • HPBSM\log\marble_worker_1\status.alerts.log • HPBSM\log\alerts\alerts.ejb.log

  14. CEM overview • Event Sub System (ESS) is integrated into BSM Platform and can be used by all the applications (Omi, Impact Subsystem, etc.) • Common Event Model (CEM) describes how a normalized event in BSM 9.0 is defined • Customer is able to license additional event management functionality (e.g. Omi 9.0)

  15. CEM overview • Each alert has a configuration that defines whether an event should be created for this alert • Event Template is used to map alert attributes to the event attributes • The attributes of an CEM event can be divided into two categories: • Event attributes that must or can be provided by the different domains (e.g. Severity of the event) • Event attributes that are used/added within the event processing done in the ESS (e.g. Date Received of the event or Number Of Duplicates)

  16. Troubleshooting • Check whether your environment is not running in staging mode • Check SMTP server name in Infrastructure Settings • Check the correctness of recipient’s address Check logs for errors

More Related