Trap Collector

The Trap Collector microservice receives SNMP traps and informs and converts them into a JSON event structure that includes the trap OID, varbinds, network socket information, and timestamp. By default, it publishes the JSON to the Pulsar topic to which the FCOM Processor microservice is subscribed.

This microservice is part of the Event microservice pipeline. See Understanding the Event Pipeline in Unified Assurance Concepts for conceptual information.

You can enable redundancy for this microservice when you deploy it. See Configuring Microservice Redundancy for general information.

This microservice provides additional Prometheus monitoring metrics. See Trap Collector Self-Monitoring Metrics.

Trap Collector Prerequisites

Before deploying the microservice, confirm that the following prerequisites are met:

1. A microservice cluster is set up. See Microservice Cluster Setup.

2. The Apache Pulsar microservice is deployed. See Pulsar.

3. If you are collecting SNMP v3 informs, you have created an SNMP v3 access profile with authentication information to send acknowledgments. To create a profile:

   1. Log in to the Unified Assurance user interface.

   2. From the Configuration menu, select Device Discovery, then select SNMP Access.

   3. Click Add.

   4. From SNMP Version, select 3.

   5. Fill out the required fields, save the profile, and make note of the ID assigned to it in the All SNMP Profiles table.

      See SNMP in Unified Assurance User's Guide for information about the fields in this interface.

      Note:

      The engine ID that you use in the profile should be a remote engine ID.

Deploying Trap Collector

To deploy the microservice in a single server environment, run the following commands:

su - assure1
export NAMESPACE=<namespace>
export WEBFQDN=<WebFQDN> 
a1helm install <microservice-release-name> assure1/trap-collector -n $NAMESPACE --set global.imageRegistry=$WEBFQDN

In a multi-server environment, deploy the Trap Collector microservice to a specific node by running the following commands:

su - assure1
export NAMESPACE=namespace>
export WEBFQDN=<WebFQDN>
export NODEFQDN=<NodeFQDN>
a1helm install <microservice-release-name> assure1/trap-collector -n $NAMESPACE --set global.imageRegistry=$WEBFQDN --set nodeSelector."kubernetes\.io/hostname"=$NODEFQDN

In the commands:

• <namespace> is the namespace where you are deploying the microservice. The default namespace is a1-zone1-pri, but you can change the zone number and, when deploying to a redundant cluster, change pri to sec.

• <WebFQDN> is the fully-qualified domain name of the primary presentation server for the cluster.

• <NodeFQDN> is the FQDN of the cluster node to deploy the microservice to.

• <microservice-release-name> is the name to use for the microservice instance. Oracle recommends using the microservice name (trap-collector) unless you are deploying multiple instances of the microservice to the same cluster.

You can also use the Unified Assurance UI to deploy microservices. See Deploying a Microservice by Using the UI for more information.

Changing Trap Collector Configuration Parameters

When running the install command, you can optionally change default configuration parameter values by including them in the command with additional --set arguments. You can add as many additional --set arguments as you need.

For example:

• Set a parameter described in Default Trap Collector Configuration by adding --set configData.<parameter_name>=<parameter_value>. For example, --set configData.LOG_LEVEL=DEBUG.

• Enable redundancy for the microservice by adding --set redundancy=enabled.

Default Trap Collector Configuration

The following table describes the default configuration parameters found in the Helm chart under configData for the microservice.

Trap Collector Self-Monitoring Metrics

The Trap Collector microservice exposes the self-monitoring metrics described in the following table to Prometheus.