In Slack channel alerts are coming as NA for status and alarm ID fields
search cancel

In Slack channel alerts are coming as NA for status and alarm ID fields

book

Article ID: 231158

calendar_today

Updated On:

Products

DX Operational Intelligence

Issue/Introduction

In our Slack channel, we are observing that status and alarmID fields coming as NA for service alarms, where for other alarms we are getting proper status as Open and Closed with the same JSON configuration in the channel settings.

JSON Format:

{
   "text":" *Affected Service* = ${service_name} \n *Status* = ${status} \n *Alarm Id* = ${alarm_unique_id} \n *Message* = ${message} \n *Severity* = ${severity} \n *Date* = ${timestamp} \n *Metric Name* = ${metric_name} \n *ImpactedServices* = ${services_impacted} \n *Alarm Type* = ${alarm_type} \n *ServiceAlarmUrl* = ${service_alarm_url} \n *RootcauseSource* = ${rootCauseSource} \n *RootcauseAlarmurl* = ${root_cause_alarm_url} \n *Device/EntityfromtheRCAlarm* = ${rootCauseHost} "
}

Environment

Release : 20.2

Component : CA DOI NOTIFICATIONS

Resolution

Please make the following adjustments to the pay load:

You can remove the following:

*Alarm Id* = ${alarm_unique_id}

alarm_unique_id is not valid for service alarms.

Use the following values for service alarms:

*Alarm Id* = ${sa_unique_id} 

sa_unique_id is valid for service alarms.

Make the following adjustments for Status.

*Status* = ${state}

For Service Alarms the corresponding field name is "state" rather than "status".

Attachments