#Checks

Alert on a Check

Setting up an alert in Metricly requires the creation of a policy and the system checks are no exception. Any check coming into the system can have a corresponding alert as well as a notification. Click on policies and select New Policy. Name the policy and apply any scoping or filtering required (for example, narrowing the scope to WinServ in US-West region with Tag Environment:Production). Next click Conditions > Add Condition, and from the drop down you will see Add System Check Condition.

Checks

Checks are used to determine the state or health of infrastructure resources, services, or applications. Dynamic and customizable, Checks allow you to define a time duration and then notify you when that state change occurs. Checks can be completely custom built by you or leverage our OOTB checks. Prerequisites You must have already installed and configured a Windows and/or Linux agent to set up checks. We recommend you update your agents to their latest version before using this document.

Custom Checks

Metricly supports custom checks. These checks require scheduling mechanisms (such as Linux cron jobs or Windows task scheduler) to run. Using the Linux platform? When running on the Linux platform, our agent can also schedule your scripts via the Users Scripts Integration. You can then schedule a script that posts to our REST API as either a system check, a time-series metric value, even a text-based data. This removes the need for a separate scheduler or loop function.

Linux Checks

Enable Linux Checks Currently, Metricly comes with three pre-built checks; Heartbeat, Processes, and Ports. These are turnkey checks that do not require any scripting or coding, just simple configuration setting in the respective configuration files. Make sure the Linux agent is installed. Metricly checks can be enabled via the configuration files included with the agent. All checks configuration files for the Linux agent can be found in /opt/netuitive-agent/conf/collectors Some of the checks are enabled by default, while you would need to enable other checks.

View Checks

Leveraging our saved filters is a good way to find your checks. All checks are tagged with the key n.checks and value check name. Click Type and select either SERVER (for Linux) or WINSRV (for Windows) to pick where the check has been configured. Navigate to More > Tag and search for n.checks.

Windows Checks

Enable Windows Checks Make sure the Windows agent is installed. Metricly checks can be enabled via the configuration files included with the agent. All checks configuration files for the Windows agent can be found in C:/Program Files (x86)/CollectdWin/conf/ or C:/Program Files/CollectdWin/conf/ (depending on the version of windows). Simply change the enable setting for the ReadSystemChecks from false to true in the CollectdWin.config file to enable the system checks. To configure the checks, edit the ReadSystemChecks.