Discovery Service

The Discovery Service microservice discovers SNMP, Ping, and VMware devices. It uses a specific payload as input to discover the devices and the result can be used to update the for inventory.

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

Discovery Service 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 following microservices are deployed:

   • Pulsar

   • DOM Processor

   • Any of the following pollers that you require:

     • Ping Poller

     • SNMP Poller

     • Vmware Poller

Deploying Discovery Service

To deploy the microservice, run the following commands:

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

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.

• <microservice-release-name> is the name to use for the microservice instance. Oracle recommends using the microservice name (discovery-service) 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 Discovery Service 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 Discovery Service Configuration by adding --set configData.<parameter_name>=<parameter_value>. For example, --set configData.LOG_LEVEL=DEBUG.

Default Discovery Service Configuration

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