DocumentaciónHelp

Plugins

Plugins, monitoring tests, monitoring tags, plugin catalog and plugin checks: how ARGUNIS checks what doesn't come ready out of the box.

On this page

Plugins extend what ARGUNIS checks. In Settings → Monitoring you'll find, with no subfolders:

Menu

What it is

Plugins

Your company's Nagios-compatible files (Perl, bash, sh, Python 3, PowerShell). ARGUNIS doesn't read their content: it stores them with their fingerprint, signs them and delivers them verified

Monitoring tests

A plugin with its parameter line, its own parameters, thresholds, interval and retries

Monitoring tags

Tests and syslog and SNMP trap reception that reach together each device they are assigned to (formerly "Templates" and tag rules)

Plugin catalog

The plugins included with the monitoring probe for network devices, storage, UPS, hardware, virtualization, databases, clouds and applications

Plugin checks

The results of the older "Nagios script" checks that the agent runs on each server

How they relate

  1. A plugin (from the catalog or uploaded by your company) is what gets run.

  2. A monitoring test says which parameter line it runs with (macros such as $HOSTADDRESS$ or $_SERVICEPUERTO$), its values, thresholds, interval and retries.

  3. A monitoring tag groups tests so they reach a device together.

  4. Each test reaches a device through a tag, from the device's page or in bulk.

Credentials never go in the line: the probe or agent takes them from the company's vault.

Who sees what

  • Plugins, Monitoring tests and Monitoring tags appear for those who have Administer on Plugins.

  • Plugin catalog and Plugin checks appear if your plan includes agents and probes.

Pages

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

↑↓ to navigate · Enter to open · Esc to close