Cloud native analytics gateway configmap

The ea-noi-layer-eanoigateway configmap for the cloud native analytics gateway is created during the installation.

For the ea-noi-layer-eanoigateway configmap, two types of changes can be made:
  • One change is to the mapping.
  • The second change is to the filter used for selecting the fields.

You can modify the map to send more custom fields to cloud native analytics. This modification is done so that the view policy windows are enriched with extra columns from your data. These additional optional columns can be for example: MUNICIPALITY, INCIDENTID, CCMDBID, NENAME, and depending on your requirements, vary in importance, which allows you to validate the correctness of the group and results. They can even be abstracted and added as an <Additional Column> rather than all listed, as not all columns are sent to Agile Service Manager.

If changes are needed to Agile Service Manager entities, consider making the same changes to the topology-noi-gateway-config configmap.

Both Agile Service Manager and ea-noi-layer-eanoigateway maps are configured by adding into a YAML file with the Agile Service Manager file better configured, given each column is on a separate line, as displayed: |-
             CREATE MAPPING StatusMap
                 'Agent'                      = '@Agent',
                 'AlertGroup'                 = '@AlertGroup',
                 'AsmStatusId'                = '@AsmStatusId',
                 'CEAEventClassification'     = '@CEAEventClassification',
                 'CEAEventClassificationText' = '@Summary',
                 'CEAEventScore'              = '@CEAEventScore',
                 'CEAProcessType'             = '@CEAProcessType',
                 'Class'                      = '@Class',
                 'Customer'                   = '@Customer',
                 'EventId'                    = '@EventId',
                 'FirstOccurrence'            = '@FirstOccurrence',
                 'Identifier'                 = '@Identifier',
                 'LastOccurrence'             = '@LastOccurrence',
                 'LastOccurrenceUSec'         = '@LastOccurrenceUSec',
                 'Manager'                    = '@Manager',
                 'Node'                       = '@Node',
                 'NodeAlias'                  = '@NodeAlias',
                 'ServerName'                 = '@ServerName',
                 'ServerSerial'               = '@ServerSerial',
                 'Severity'                   = '@Severity',
                 'StateChange'                = '@StateChange',
                 'Summary'                    = '@Summary',
                 'Tally'                      = '@Tally',
                 'Type'                       = '@Type'

An example of an ea map follows, where the format is a single line of values with embedded \t.

 cea-map: "CREATE MAPPING StatusMap\n(\n    'Identifier'\t   = \t'@Identifier',\n    'Node'\t\t   =\t'@Node',\n    'NodeAlias'\t   =\t'@NodeAlias' NOTNULL '@Node',\n    'Manager'\t   =\t'@Manager',\n    'Agent'\t\t   =\t'@Agent',\n    'AlertGroup'\t   =\t'@AlertGroup',\n    'AlertKey'\t   =\t'@AlertKey',\n    'Severity'\t   =\t'@Severity',\n    'Summary'\t   =\t'@Summary',\n    'StateChange'\t   =\t'@StateChange',\n    'FirstOccurrence'  =\t'@FirstOccurrence',\n    'LastOccurrence'   =\t'@LastOccurrence',\n    'InternalLast'\t   =\t'@InternalLast',\n    'Poll'\t  \t   =\t'@Poll',\n    'Type'\t\t   =\t'@Type',\n    'Tally'\t\t   =\t'@Tally',\n    'Class'\t\t   =\t'@Class',\n    'Grade'\t\t   =\t'@Grade',\n    'Location'\t   =\t'@Location',\n    'OwnerUID'\t   =\t'@OwnerUID',\n    'OwnerGID'\t   =\t'@OwnerGID',\n    'Acknowledged'\t   =\t'@Acknowledged',\n    'Flash'\t  \t   =\t'@Flash',\n    'EventId'\t   =\t'@EventId',\n    'ExpireTime'\t   =\t'@ExpireTime',\n    'ProcessReq'\t   =\t'@ProcessReq',\n    'SuppressEscl'\t   =\t'@SuppressEscl',\n    'Customer'\t   =\t'@Customer',\n    'Service'\t   =\t'@Service',\n    'TaskList'\t   =\t'@TaskList',\n    'NmosSerial'\t   =\t'@NmosSerial',\n    'NmosObjInst'\t   =\t'@NmosObjInst',\n    'NmosCauseType'\t   =\t'@NmosCauseType',\n    'X733EventType'    =\t'@X733EventType',\n    'X733ProbableCause'=\t'@X733ProbableCause',\n    'X733SpecificProb' =\t'@X733SpecificProb',\n    'X733CorrNotif'\t   =\t'@X733CorrNotif',\n    'URL'\t\t   =\t'@URL',\n    'ServerName'\t   =\t'@ServerName',\n    'ServerSerial'\t   =\t'@ServerSerial',\n    'CEAEventScore'    =    '@CEAEventScore',\n    'CEAEventClassification' = '@CEAEventClassification',\n    'CEAProcessType' = '@CEAProcessType',\n    'ScopeID'          =   \t'@ScopeID'\n);"

The configmap file might be lost if you do an upgrade, but that is no reason to limit the use of remapping. If a configmap is modified, you need to back up your configmaps before the upgrade procedure, and then reapply the backup copy.

Note: Customizations to the gateway set might be necessary, but bear in mind that support might require you to replicate on a noncustomized environment to proceed with Salesforce tickets.