Key Updates in AIOps 2.5

Notification

Navigation:

• Notification is available under ‘SETTINGS’ menu in Configuration’.

• On clicking ‘Create Notification’, a wizard to insert notification details pop-up. PFB:

• Email id and password from which notification mail is to be send needs to be configured in ‘Response Configuration’ as part of project configuration. PFB:

Events supported:

• Ticket Created For Alert Cluster

• Ticket Created For Acknowledgement Cluster

• Ticket Created Manually

• Surge Ticket Created

• Alert Cluster Acknowledged By User

Notations supported:

• ${currentAlert.<>}: Notation to be used to fetch attributes from current alert

• ${baseAlert.<>}: Notation to be used to fetch attributes from base alert

• ${<>}: Notation to be used to fetch attributes from ticket triggering alert

• ${ticket.<>}: Notation to be used to fetch attributes from ticket

Default templates:

1. Template for ticket creation:

   1. Subject: New ticket created - ${ticket.ticketNumber} - ${ticket.ticketPriority}

   2. Body: <b>Short Description:</b> ${ticket.shortDescription}<br><b>Long Description:</b> ${ticket.longDescription}<br><b>Ticket Triggering Alert Details</b><br><b>Alert ID:</b> ${alertID}<br><b>Alert Name:</b> ${alertName} <br><b>Resource Name:</b> ${nodeName} <br><b>Alert Metric:</b> ${alertMetric} <br><b>Alert Source:</b> ${source} <br><b>Alert Time:</b> ${alertTime}

2. Template for alert acknowledged:

   1. Subject: Alert cluster acknowledged - ${baseAlert.alertID}

   2. Body: <b>Base Alert Details</b><br><b>Alert ID:</b> ${baseAlert.alertID}<br><b>Alert Name:</b> ${baseAlert.alertName} <br><b>Resource Name:</b> ${baseAlert.nodeName} <br><b>Alert Metric:</b> ${baseAlert.alertMetric} <br><b>Alert Source:</b> ${baseAlert.source} <br><b>Alert Time:</b> ${baseAlert.alertTime} <br><b>Cluster Size:</b> ${baseAlert.clusterInfo.size}
      Note: Templates accept html tags for formatting.

 

Reverse acknowledgment update and merge cluster

For handling success and failure scenarios, some changes are added to the event mapping Apis. The latest changes were marked yellow.

To enable reverse acknowledgment, the following configurations should be added to the project,

1. Insert source versions in AIOpsConfigurations

   {

   "projectId" : 1096,

   "configType" : "sourceVersions",

   "configData" : {

   "versions" : [

   {

   "icinga":"1"

   }

   ]

   }

   }

   Swagger: https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/itopsservices/swagger#/Config%20Data/insertConfigData

2. Add action event mappings for the required events.

   {

   "projectId": 1096,

   "event": "newAlertCreated",

   "sequence": 1,

   "conditions": {

   "rules": [{

   "field": "source",

   "value": "icinga",

   "operator": "="

   }]

   },

   "actionType": "success",

   "actions": ["reverseAck"]

   }

   Swagger: https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/alertmapping/swagger#/ActionEventMappings/actionEventMappings

    

3. Insert monitoring tools wrapper configurations

   {

   "projectId" : 1096,

   "toolName" : "icinga",

   "version" : "1",

   "action" : "reverseAck",

   "wrapperURL" : "https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/aiopsicingawrapper/api/icinga/acknowledgeProblem",

   "connectionFields" : [

   "reverseAckHost",

   "reverseAckUsername",

   "reverseAckPassword"

   ],

   "type" : "API"

   }

    

   Swagger: https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/alertmapping/swagger#/MonitoringToolsWrapperConfig/monitoringToolsWrapperConfig

4. Insert reverse acknowledgment configurations

   {

   "projectId" : 1096,

   "source" : "Icinga",

   "reverseAckHost" : ">",

   "reverseAckUsername" : "icinga_username",

   "reverseAckPassword" : "icinga_password"

   }

    

   Swagger: https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/alertmapping/swagger#/ReverseAckConfigurations/reverseAckConfigurations

5. Add reverse acknowledgment templates

{

"precedence" : 1,

"active" : true,

"templateRules" : {

"rules" : [

{

"field" : "source",

"value" : "icinga",

"operator" : "="

}

]

},

"templateMapping" : [

{

"values" : [

{

"fieldValue" : "Service",

"fieldRules" : {}

}

],

"fieldName" : "type"

},

{

"values" : [

{

"fieldValue" : "",

"fieldRules" : {}

}

],

"fieldName" : "filter"

},

{

"values" : [

{

"fieldValue" : "icingaadmin",

"fieldRules" : {}

}

],

"fieldName" : "author"

},

{

"values" : [

{

"fieldValue" : "true",

"fieldRules" : {}

}

],

"fieldName" : "notify"

},

{

"fieldName" : "comment",

"values" : [

{

"fieldRules" : {

"rules" : [

{

"field" : "ticketNumber",

"value" : "",

"operator" : "="

}

]

},

"fieldValue" : "Acknowledging the alert ${alertName}"

},

{

"fieldRules" : {

"rules" : [

{

"field" : "ticketNumber",

"value" : "",

"operator" : "!="

}

]

},

"fieldValue" : "Acknowledging the alert ${alertName}, with ticket number ${ticketNumber}"

}

]

}

],

"scenario" : "reverseAcknowledgment",

"templateName" : "Reverse acknowledgement - Icinga",

"projectId" : 1096

}

 

Swagger: https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/alertmapping/swagger#/Template/TicketTemplate

• New event “mergeCluster” is introduced for merging clusters. For reverse acknowledge the merge clusters. Event mappings should be created for “mergeCluster” in “ActionEventMapping” collection