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 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

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

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

EUM Alerts overview – actions Send to recipient ( , 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

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

EUM Alerts overview – diagram

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

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

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)

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

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

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

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)

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 22 February February February 2016 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