Assure1 Metric Poller Discovery Agent¶

Overview¶

The Assure1 Metric Poller Discovery Agent application uses the configured Polling Policies to create metrics that will be polled from a device and associate thresholds. This is accomplished by using instance information already gathered by other applications and put into the Assure1 database.

Below are some examples of processing that can be done so the base metric entries are created for the respective application, but other processing can also be done as well:

Ping Polling metrics can be created.
Interface Inbound and Outbound Bandwidth, Errors and Discards metrics can be created depending on the Device Type and Instance Name.
Response Time metrics can be created depending on the Device Type and Instance Name.

Poller Discovery Agent Setup¶

Devices must exist in the Device Catalog for this application to be able to function. Devices can be created in several different ways:
1. Using the "Device Auto Discovery" application (DeviceAutoDiscovery). See the application documentation for additional information.
2. Using the Manual Discovery UI:
  
  Configuration -> Device Discovery -> Manual Discovery
3. Manually entering all values using the Devices UI:
  
  Configuration -> Device Catalog -> Devices
Optional - The bandwidth metric creation functionality requires that instances have been discovered using the Metric SNMP Network Interface Discovery Agent job (which uses the SNMPInterfaceDiscoveryAgent application), or via another method.
Optional - The response time metric creation functionality requires that instances have been discovered using the Metric NMAP TCP Port Discovery job (which uses the PipeDisco application), or via another method.
Using the Polling Policies UI, create the entries that will be used when the application is run, and make changes as needed in the environment:

Configuration -> Metrics -> Polling Policies

When configuring policies, there are several defaults that have been configured for ease of use.
- If setting up Ping Polling, the following can be used:
  - Match
    - Instance
      - Match => LIKE
      - Name => Device
  - Assign
    - Method => NA
    - Poller Template => Default Ping
    - Threshold Group => Default Ping
- If setting up Network Interface Polling, the following can be used:
  - Match
    - Instance
      - Match => LIKE
      - Name => eth
  - Assign
    - Method => SNMP
    - Poller Template => Default Network Interface
    - Threshold Group => Default Network Interface
- If setting up Response Time Polling, the following can be used:
  - Match
    - Instance
      - Match => LIKE
      - Name => tcp
  - Assign
    - Method => Transaction
    - Poller Template => Default Response Time
    - Threshold Group => Default Response Time
Enable the default Job, unless a specific configuration option is needed.

Configuration -> Broker Control -> Jobs

Default Scheduled Job¶

Field	Value
Package Name	coreCollection-app
Job Name	Metric Poller Discovery
Job Program	bin/core/collection/PollerDiscoveryAgent
Job Arguments
Job Description	Automatically creates polling based up Poller Policies
Failover Type	Standalone (Supported: Standalone, Primary/Backup)
Status	Disabled
Privileged	(Checked)
Minutes	59
Hours	0
Days	*
Months	*
WeekDays	0

Default Configuration¶

Name	Value	Possible Values	Notes
LogFile	logs/MetricPollerDiscovery.log	Text, 255 characters	Relative path to Log File.
LogLevel	ERROR	OFF, FATAL, ERROR, WARN, INFO, DEBUG	Logging level used by application.

Best Practices¶

The default job configuration is to run every Sunday at 12:59:00am.

Administration Details¶

The following list shows the technical details needed for advanced administration of the application:

Package - coreCollection-app
Synopsis - ./PollerDiscoveryAgent [OPTIONS]

Options:

 -c, --AppConfigID N   Application Config ID (Service, Job, or Request ID)
 -?, -h, --Help        Print usage and exit

Threaded - Single Threaded