3.3.4 Configuring Alert Manager for SNMP Notifier

Grouping of alerts is based on:

• podname
• alertname
• severity
• namespace
• nfServiceType
• nfServiceInstanceId

User needs to add subroutes for SCP alerts in AlertManager config map as below:

1. Take a backup of the current config map of Alertmanager by running the following command:

   kubectl get configmaps <NAME-alertmanager> -oyaml -n <Namespace> > /tmp/bkupAlertManagerConfig.yaml
   

   Example:

   kubectl get configmaps occne-prometheus-alertmanager -oyaml -n occne-infra > /tmp/bkupAlertManagerConfig.yaml

2. Edit Configmap to add subroute for SCP Trap OID:

   kubectl edit configmaps <NAME-alertmanager> -n <Namespace>

   Example:

   kubectl edit configmaps occne-prometheus-alertmanager -n occne-infra

3. Add the subroute under 'route' in configmap:

   routes:
         - receiver: default-receiver
           group_interval: 1m
           group_wait: 10s
           repeat_interval: 9y
           group_by: [podname, alertname, severity, namespace, nfservicetype, nfserviceinstanceid, servingscope, nftype]
           match_re:
             oid: ^1.3.6.1.4.1.323.5.3.35.(.*)

MIB Files for SCP

There are two MIB files which are used to generate the traps. The user need to update these files along with the Alert file in order to fetch the traps in their environment.

• ocscp_mib_tc_24.2.6.mib: This is considered as SCP top level mib file, where the Objects and their data types are defined.
• ocscp_mib_24.2.6.mib: This file fetches the Objects from the top level mib file and based on the Alert notification, these objects can be selected for display.

Note:

MIB files are packaged with ocscp_csar_23_2_0_0_0.zip. You can download the file from MOS as described in Oracle Communications Cloud Native Core, Service Communication Proxy Installation, Upgrade, and Fault Recovery Guide.