DocumentaciónHelp

Configure a host

Change a host's name, category, group, site, environment and status, and what each monitor does when it fails.

On this page

Configure brings together in tabs what is checked on the host, what it does when it fails and who gets the notification.

Before you start

  • You need permission to operate in Infrastructure.

  • Hosts that come from an integration (Wazuh) don't have Configure.

Steps

  1. Open the host page and click Configure.

  2. Go through the tabs you need (each one is explained below). The tab shows an amber counter with the changes you haven't saved yet.

  3. Click Save to save and keep going, or Save and close to go back to the page. Cancel goes back without saving.

Tabs

General

  • Display name. On a server with an agent, the name the agent reports doesn't change.

  • Alias and Instance (optional): tests use them as $_HOSTALIAS$ and $_HOSTINSTANCE$ (for example, the SQL Server instance).

  • Monitored from: the monitoring probe, the server agent or the ARGUNIS cloud, and its IP or FQDN. Choosing another origin opens the window that migrates the monitoring. See Change where it's monitored from.

  • Category and Group.

  • Site: where the host is; it places it on the dashboard map. See Assign a host's site.

  • Environment: Production, QA, Development or Other.

  • Status: Active, In maintenance or Inactive. In maintenance or inactive, its failures are recorded only as events.

  • Alert thresholds (%) for Disk, RAM and CPU. See Adjust the alert thresholds.

  • Host availability and metrics on failure: Creates incident and the Resolver group (or From routing (group, rules or default)).

Monitoring

A table with each of the host's monitors, where you can change:

  • Creates incident (Yes or No).

  • Resolver group (From routing or its own group).

  • Dependency: the monitor it depends on (None if it doesn't depend on another).

Each monitor says who runs it and where it came from: From tag … or Manual.

These three changes are saved with Save. You can also:

  • Add from the catalog: adds a reusable test. See Associate monitoring tests and use tags.

  • Edit, Duplicate or Remove a test. Probe checks are edited in Monitor from the probe, and agent plugins on their own page.

Tags and macros

  • Monitoring tags: the list of assigned tags, with their tests and how many monitors come from each one. To assign one, choose it (and, if the host isn't monitored from a probe, the Probe for its tests) and click Assign: its tests appear immediately in Monitoring. Remove unassigns it without deleting its monitors. See Create a monitoring tag.

  • Host macros: values in the format NOMBRE=valor (one per line) that tests use as $_HOST + name + $. For example, SITIO=norte is used as $_HOSTSITIO$. Never put credentials here. Below you see the automatic macros.

Credentials

  • If the host is checked from the cloud over SSH or SNMP, you choose its vault credential here.

  • If a probe checks it, you see which credential it uses and the link to Monitor from the probe to change it.

  • Device credentials: vault credentials used by its monitoring tags, according to the type each test requires. They are added and removed immediately.

  • Below, the list of credentials its tests use.

  • Create credential opens the vault form.

Logs and traps

For hosts checked by a probe:

  • Fetch logs from the host: with SSH, journald (with priority), services and files; with WinRM, the Event Log channels.

  • Specific logs: file, text it Searches for and Level. Add them with Add specific log.

  • Reception on the probe: Receive syslog from this host and Receive SNMP traps from this host.

On a server with an agent, logs are configured on the agent's page. If the host has neither a probe nor an agent, the tab offers you Monitor from the probe.

Interfaces

Choose the host's main interface. If the probe reports the interfaces over SNMP, you choose one from the table (with its status, speed, traffic and errors); if not, you type its name, for example Gi0/1 or eth0.

Related

Search Argunis Monitoring

Type at least 2 characters to search Argunis Monitoring.

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