AIOps 2.2 Post Deployment Process

Reference Data Changes:

A new entry should be added in ITOpsReferenceData/ITOpsProjectReferenceData mongo collection to re an internal group. This is to differentiate internal and external groups.

1. referenceType – internalGroups

2. referenceValue – <group id>, (ID of the group)

3. referenceValueCode – <group name>, (Name of the group)

Note:

• ‘Default Assignment Group’ in project configuration should be part of ‘internalGroups’

• State machine validates rules based on ids (assignedToUserId and assignedGroupId).

Migrate Existing Project:

For Migrate existing projects follow the below steps:

• For update existing project state, trigger “/api/updateProject” api.

• To get the execution details, trigger “/api/getUpdateProjectHistory” api

• Please find the api details from, Migration api details

Reference Data change post migration:

Post migration, the Virtual Engineer configuration in project reference data should be updated with id instead of name as further evaluation of state is done based on assignedToUserId. For this, the existing data needs to be deleted first and new data has to be added. Please see the API details below.

• API to delete virtual engineer configuration from referenceData
  

  ITOps Services (azure.com)Request: {   "projectId": <projectId>,   "referenceType": "ITOpsVirtualEngineerConfiguration" }

 

• API to add virtual engineer configuration
  https://smartops-dev03.eastus.cloudapp.azure.com/paas/itops/itopsservices/swagger#/ProjRefData/addProjectRefData
  

  Request: {   "projectId": <projectId>,   "referenceType": "ITOpsVirtualEngineerConfiguration",   "referenceValues": [     {       "ITOpsVirtualEngineer":"<Virtual engineer id>"     }   ] }

 

 

General Notes for Release 2.2 – Ticket Templates 

• New scenario ‘alertAddedToCluster’ available for ticket templates – This is to define how the ticket should be updated when a new alert is correlated to a ticket created before.

• For this scenario, fields – ‘longDescription', 'ticketStatus', 'assignedTo', 'assignedGroup' cannot be edited. Rest of the fields can be updated when new alert is added to a cluster.

• New notations introduced - ‘${baseAlert}’ and ‘${currentAlert}’. With this any notation with ‘${baseAlert}’ refers to baseAlert, ‘${currentAlert}’ refers to currentAlert and ‘${}’ refers to ticketTriggeringAlert.

• With the new notations, fieldRules of template can be evaluated against any attributes of specific alert (baseAlert, currentAlert or ticketTriggeringAlert) and matching fieldValues of specific alert can be updated.

• These notations can be applied to existing scenarios as well.

• While applying these notations for rules, please ensure that one rule block has only one notation. Within the same rule block, value of an attribute of baseAlert cannot be evaluated along with value of an attribute of currentAlert or ticketTriggeringAlert.

• While applying notations to fieldValues, different notations can be mixed in the same fieldValue.

API Details:

• Insert ‘alertAddedToCluster’ template using the template insert API. Update/Delete can also be done using template update/delete APIs.

• Swagger of APIs : Template APIs Swagger

• New field ‘ITSM Impact’ available in project configuration. Please update value of relevant field in itsm tool which denotes impact of ticket.

  eg ‘impact’ is the field for itsm tool servicenow.

• Sample ‘alertAddedToCluster’ template:
  

  {    "templateRules":{           },    "active":false,    "projectId":"<projectId>",    "scenario":"alertAddedToCluster",    "templateName":"alertAddedToClusterTemplate",    "templateMapping":[       {          "fieldName":"comments",          "values":[             {                "fieldRules":{                   "rules":[                      {                         "operator":"=",                         "value":"false",                         "field":"${currentAlert.recovery}"                      }                   ]                },                "fieldValue":"${currentAlert.alertID} is non recovery with severity ${currentAlert.severity} added to  ${baseAlert.alertID} with severity ${baseAlert.clusterInfo.severity}"             }          ]       },       {          "fieldName":"impact",          "values":[             {                "fieldRules":{                   "rules":[                      {                         "operator":"!=",                         "value":"warning",                         "field":"${baseAlert.severity}"                      }                   ]                },                "fieldValue":"2 - Medium"             }          ]       },       {          "fieldName":"urgency",          "values":[             {                "fieldRules":{                   "rules":[                      {                         "operator":"!=",                         "value":"warning",                         "field":"${baseAlert.severity}"                      }                   ]                },                "fieldValue":"2 - Medium"             }          ]       }    ] }