Ping Poller

The Ping Poller microservice performs ICMP discovery for the discovery request and pings the device for availability.

This microservice is part of the Discovery microservice pipeline. It uses a worker-coordinator design to balance workloads and allow for scaling. See Understanding the Discovery 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.

Autoscaling is enabled by default for this microservice. You can optionally disable autoscaling when you deploy the microservice. See Configuring Autoscaling.

This microservice provides additional Prometheus monitoring metrics. See Ping Poller Self-Monitoring Metrics.

Ping Poller 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

   • Discovery Service

Deploying Ping Poller

To deploy the microservice, run the following commands:

su - assure1
export NAMESPACE=<namespace>
export WEBFQDN=<WebFQDN> 
a1helm install <microservice-release-name> assure1/ping-poller -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 (ping-poller) 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 Ping Poller 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 Ping Poller 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.

• Disable autoscaling for the microservice by adding --set autoscaling.enabled=false.

• Set the autoscaling parameter described in Ping Poller Autoscaling Configuration by adding --set autoscaling.<parameter_name>=<parameter_value>. For example, --set autoscaling.totalTargetsPerWorker=4000.

Default Ping Poller Configuration

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

Default Ping Poller Coordinator Configuration

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

Default Ping Poller Worker Configuration

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

Ping Poller Autoscaling Configuration

Autoscaling is supported for the Ping Poller microservice. See Configuring Autoscaling for general information and details about the standard autoscaling configurations.

The Ping Poller microservice also supports the additional configurations described in the following table.

Ping Poller Self-Monitoring Metrics

The Ping Poller microservice exposes the self-monitoring metrics described in the following table to Prometheus. Each of the metrics in the table is prefixed with ping_coordinator prefix in the database. For example, the full metric name in the database for the first metric is ping_coordinator_acom_targets.