DocumentaciónHelp

Create a monitoring test

Choose the plugin, write its parameter line with device and credential macros, and define custom parameters, thresholds, interval and how many failures to wait for before alerting.

On this page

A monitoring test is a plugin with its parameter line, its values, how often it runs and how many consecutive failures it waits for before alerting. A test can derive from another one and inherit whatever doesn't change.

Before you start

  • You need Administer on Plugins.

  • If you will use one of your company's plugins, Upload a plugin first.

Steps

  1. Go to Settings → Monitoring → Monitoring tests and click New test.

  2. Enter the Name and the Description. In Based on, choose A plugin with its parameter line or Another test (inherits and overrides).

  3. Choose the Credential type it uses (or let the plugin ask for it).

  4. In Plugin and parameter line:

    • Plugin: From the plugin catalog (run by a probe; choose the plugin, the Mode and the Connection) or A company plugin (choose what runs it: probe or agent; it is only associated with what that source monitors, and the credentials it accepts).

    • Parameter line: use the device macros ($HOSTADDRESS$, $HOSTNAME$, $_HOSTINSTANCE$, $_HOST<NOMBRE>$) and the test macros ($_SERVICE<PARÁMETRO>$, $ARG1$…). To bring in a Centreon line, click Paste Centreon line.

  5. In Own parameters, click Add for each value that changes per device: Name, Help, Type (text, number or yes/no), Default value, Required and Order. In the line they are used as $_SERVICE<NOMBRE>$.

  6. Fill in Thresholds per metric, Named metrics and Execution and alerting (interval, timeout and Consecutive failures before alerting).

  7. Click Create test.

The credential is never written in the line: the probe or agent supplies it from the vault (a credential option contains only its macro; a company plugin receives it in ARGUNIS_CRED_*).

What happens next

  • The Associated devices tab lists each device with the test, its status, what runs it and which tag it came from (or "Manual"). You can also apply it in bulk from there.

  • If you change a test that is already on devices, ARGUNIS shows you how many monitors it affects and asks you to confirm with Save and apply.

  • A Required parameter without a value prevents adding the test to a device until it is filled in.

Built-in tests are read-only. Click Duplicate or Derive to change them.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

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