Add/Edit MetricsView Collector Alerts

Device Type: MetricsView Glossary: MetricsView Collectors How to Edit a MetricsView Collector  Name: Defines the collector’s name, and is listed as part of the MetricsView custom collector task configuration. MetricsView Node Alert Email: Is the address that will receive notices about issues with collector. Send first alert after: Defines the duration to wait while the system has not received incoming counters until the system will trigger an alert. Continue Alerting Every: Determines how often alerts are sent when the collector is in an alert state. Collector Type: Selecting MetricsView agent will use the metricsview software that you download to your computer.  Selecting Customer Counter will  require you Read more

MetricsView: Linux Performance Counters

The MetricsView Linux monitoring service allows users to set thresholds for data from Collectd performance counters and set alerts when those thresholds are exceeded. A “MetricsView Agent” (aka, MV-Agent) is an application installed locally on your server as a service that gathers the WPC statistical data. The MV-Agent provides access to collectd linux performance counter data from the local machine where the MV-Agent is installed, as well as any machine available on an adjoining network. The configured Linux performance counter monitoring is stored as a task within a MetricsView device. An MV-Agent gathers Linux statistics values at approximately 45-second intervals. Therefore, the number of Linux statistic values gathered within a data set Read more

MetricsView: Using an existing collector

If you already have a collector setup and running in your environment that is capable of collecting the data for the current task, you can simply select the collector from a list and press the continue button.

MetricsView: Collectors

MetricsView uses collectors to gather performance counters or server statistics from devices and servers within your environment. A collector must be installed on a computer within your network and run as a user with sufficient permissions capable of gathering statistics from the machines you wish to monitor. Hostname: The hostname is the name or IP address of the computer you wish to monitor. Error Thresholds:  Error thresholds define the numerical values which, when exceeded, will trigger alert states. Aggregate : All received data will be aggregated on a regular basis, according to the adjusted device frequency. Maximum – the highest value from Read more

MetricsView Reports

MetricsView Device Summary Contains all individual monitoring results of MetricsView Counters including Time Monitored, Status Aggregated Counter Value, Number of Collected Samples, If there is an error, the reason for the error. MetricsView Device Executive Summary Contains an overview of MetricsView monitoring results including Performance data, lists of periods where data is outside of specified ranges, average counter value chart. MetricsView Overall Summary Contains a timeline and summary of metrics averages, minimums and maximums.

MetricsView Linux Agent (collectd)

The MetricsView Collectd Linux agent is a plug-in that aggregates various system metrics and sends them to Dotcom-Monitor. While this agent supports over 90 metric by default, the current release is limited to five metrics: cpu, memory, interface (network), disk and df (space usage). The agent is written on python 2 and utilizes open source “requests“. The MetricsView Linux agent is based on the system statistics collection daemon, Collectd and is designed so there is no need to make any additional configuration changes except those appropriate for different Linux distributions, as described below. The following files are placed in /opt/com/dotcom during Read more

MetricsView: Linux (Collectd) Custom Collector Task Setup

Device Type: MetricsView Platform Glossary Entry:  Linux Custom Collector Setting up and Installing a Linux Custom Collector How to Edit a Linux Custom Collector Task Wizard Interface Task Name: Enter a name that describes the function of the task. For example “Server 2 CPU % in use”. Task UID:  The UID is a unique ID that is generated for each task.  This ID is used to interface with the task in the API. Collector:  Select the collector from which to retrieve the data for the task. Custom Counterpath: reflects the relative path to the counter in the source system for example : Read more

MetricsView Linux Agent (collectd) Installation

Glossary:  MetricsView Linux Agent (Collectd) Installation: We strongly recommend not to install under root user, but utilize “sudo” command. The following command will show if the service is running on your machine: service collectd status Logs/Errors: The script will output everything considered an ”error” to the master collectd process and using “syslog” collectd plugin, will log it according to configuration. All error messages are pretty straightforward and self-explanatory. Depending on the Linux distribution you are using, the logs are stored either in file “dmesg”, or in “messages” in the /var/log/ folder or can be accessed with journal logging system (journalctl) Read more

MetricsView: Monitoring the Status of a Windows Service

Here are instructions to setup a Windows Power shell data collector to monitoring the status of any windows service. In your Dotcom-Monitor Account, set up a MetricsView Custom Collector: Setup a custom collector task. You must fill out the host category instance and counter fields, but it doesn’t matter what they are, they are not used for this.  The Aggregation type for the Task must be set to MIN or MAX.  The service status can be in 7 states. By default they are transformed into values: Service is stopped – default 1000 Service is starting – default 2000 Service is stopping – default Read more

Understanding MetricsView Custom Collectors

Device Type: MetricsView Glossary: Custom Collectors Creating a new MetricsView Collector MetricsView Custom Collectors are used to gather data about the performance of any custom metrics you are able to gather with your own monitoring equipment. Some examples of custom data you may be able to collect are digital thermometer readings, or the results from other sensors attached to a computer. Custom Collectors are setup on the Dotcom-Monitor website to be used as the monitoring target for MetricsView monitoring tasks.