There are 3 main steps to setting up MetricsView:

1. Creating a new MetricsView Collector

System Requirements

  • 2-core CPU or higher
  • 4GB RAM
  • 2 GB hard drive space+1MB per monitoring results saved
  • OS Windows Server 2008 or higher 64bit or Supported Versions of Linux
  • .NET Framework 4.5 (exactly 4.5)

2. Downloading and installing the MetricsView Agent


  • Visit the MetricsView Download Page
  • Download the MetricsView installer
  • Complete the installation using an account with administrative rights

3. Setting up a MetricsView task to use the new Agent/Collector

Watch the following video or read more below to learn how to complete the MetricsView setup.

Creating a MetricsView Collector

In the configure section of the top navigation menu select MetricsView Collectors.

This page will display all MetricsView Collectors you have created.


Click the Add New Collector button on the lower right hand side of the screen.


To create a new collector specify the following values:

Name:  Give the collector a descriptive name so that you understand what the collector is when reviewing reports and alerts about this collector.

MetricsView Node Alert Email:  Specify the email address you wish to receive notifications if there are issues with the collector itself.

Alert Frequency: Specify how often you want the system to wait before re-sending an alert. (for example, if a server appears to be offline, do you want to receive an alert every 10 minutes until the machine is back online or do you want to receive an alert once an hour etc…

Switch to alert state if MetricsView Agent is not accessible [x mins]: This specifies how long the system waits after detecting a collector is not accessible before sending an initial alert.  For example, it might be ok for some systems to not report in for 30 minutes at a time while you may want to know as soon as possible if another system is not reporting in.

Switch to alert state if there are no responses received within [x mins]:  This specifies that an agent has been contacted but the agent has not sent any data for the specified period of time.

It is important to note:  If you have an agent that only reports data once per hour, and you specify an alert to trigger for a shorter time period you will receive false alerts until you change the value of this field to be greater than the frequency of the task.

Collector Type: There are two collector types, MetricsView Agents and Custom Collectors.

The MetricsView Agents are monitoring services installed on your devices that collect Windows Performance counters.

The Custom Collectors are available by pushing custom counter data to the Dotcom-Monitor platform using the REST API interface.  Custom Collectors allow you to define and push data about anything that you can monitor.  For more information on how to set up and configure a Custom Collector, see the Custom Collector article.

It is important to note:  If you create a new MetricsView Collector and set up an alert to be sent via email and you do not have a MetricsView Agent installed on a computer using the new Collector ID, you will begin receiving alerts from the system once the alert state has been triggered.

Installing the MetricsView Agent

When you are logged in to the system, go to the Downloads section in the top navigation and click on MetricsView Agent and click the download button.  Once you have downloaded the agent you need to install the software on the machine you wish to use as your collector agent.

Once you have installed the agent you will need to run the Registrator from the start menu under all programs, Dotcom-Monitor, MetricsView Agent, Registrator.  You will be prompted to enter your Dotcom-Monitor username and password in order to attach this collector to your account. You will also need to copy and paste the Collector ID from your browser on the MetricsView List page into the MetricsView Agent Unique ID field.

This agent will be able to monitor any windows performance counters available on this machine, as well as any additional performance counters of other machines on this network that the service has access to.

Setting up a MetricsView Task