Associate monitoring tests and use tags
Add reusable catalog tests to a host or database, assign monitoring tags, and set tag rules so they apply on their own.
On this page
A monitoring test is a reusable check (CPU, disks, interfaces, database, HTTP, certificate, etc.) that a monitoring probe or the server agent runs against a host. Tests are defined once and associated with many hosts.
Whoever monitors the host decides which tests it gets (a monitor has a single origin and is never combined):
Monitored by | Tests |
|---|---|
A monitoring probe | probe tests only, run by that probe |
The server agent | agent tests only, run by that agent |
ARGUNIS (cloud or integration) or APM | none |
If several origins watch the same target, they are separate monitors. Web services, cloud services and APM services don't get tests; a database does, depending on who monitors it.
Before you start
You need permission to operate.
For tests run by a probe, you need an active Monitoring probes.
The test catalog and the monitoring tags are managed in Settings → Monitoring → Monitoring tests and Settings → Monitoring → Monitoring tags.
Add a test to a host
Open the host page, click Configure and go to the Monitoring tab.
Click Add from the catalog.
In Search the catalog, type part of the name (for example, CPU, disk, interfaces, HTTP or certificate) and choose the Test. Its description appears below.
The list shows only the tests that apply to the host, and below you see who runs it (its probe or its agent).
If a probe runs it, choose the Credential (vault) if the test needs one. If it's missing, use Create credential.
Complete the arguments the test asks for (they appear as
$ARG1$,$ARG2$, etc. with their description). If you leave them empty, the test's values are used.Optional: Macros for this host only, a Name and an Address different from the host's.
In On failure, set Creates incident, whether it stays Enabled, the Resolver group and whether it Depends on another monitor.
Click Add.
The probe runs the test within seconds and you'll see it on the page's Monitoring tab.
Assign a monitoring tag
A monitoring tag groups several tests (formerly a “template”).
In Configure, go to Tags and macros.
In Monitoring tags, choose the tag. Only its tests that apply to the host are applied; the rest are skipped with the reason.
Click Assign. Its tests appear in Monitoring, with the device credential of the type each one requires; whatever the host already has is skipped.
You can also choose one when you Add a host from a probe. See Create a monitoring tag.
Tests on databases
On the page of a database monitored by a probe or an agent, click Configure and go to Tests and macros. The Monitoring tests panel has:
Add test: choose the test (only those for its origin), the credential and its arguments, and click Add. The probe or agent that monitors the database runs it.
Apply template: applies the tests of a monitoring tag.
Macros: the object's macros, one per line.
Tags: the object's tags.
Tests: opens the test catalog in Settings.
Each test in the list shows its status, the command line it runs, who runs it, the output, the interval and the last check. With the chart button you see its performance data for the last 24 hours.
Use tags to apply tests automatically
A tag (for example produccion, sap or sede-norte) lets you apply tests to every object that has it, now and in the future.
Add tags to an object
In Configure → Tests and macros, click Tags.
Enter the tags separated by commas (up to 20).
Click Save tags.
If a new tag has rules, its tests are applied immediately and the notice tells you how many were added. Removing a tag doesn't remove the tests already applied.
Create a tag rule
Go to Settings → Monitoring → Monitoring tests (or Monitoring tags) and open the test or the tag.
In Apply in bulk, choose the Object type and enter the Tag.
Choose the Probe and the Credential (vault).
Select Also to whatever gets this tag later.
Click Preview to see which objects it would reach, and then Create rule and apply.
Active rules are listed in Tag rules. With Remove you stop applying the test to objects that get the tag from now on; the monitors it already created remain until you remove them on each object's page.
Without selecting the rule option, Apply in bulk also lets you apply a test just once to several objects, filtering by group, site or type.