WebSocket Application Monitoring

Platform: UserView   EveryStep records interactions with websites that utilize WebSockets.  After recording your WebSocket monitoring script, you can upload it to the Dotcom-Monitor cloud and schedule monitoring from dozens of locations around the world. Recording a script with EveryStep  

Edit a UserView Task

Device Type: UserView Platform Glossary: UserView How to create devices and tasks Adding / Editing a UserView Device How to Edit a UserView Task Task Name Provide a descriptive name for the task so that you would be able to identify the task later among a list of similar tasks.  For example, “www.example.com 3 step login script” Script Timeout (in Seconds) Enter the number of seconds the task should wait for a response from the web page before aborting the task and returning an error.  If this is left blank the default timeout for a step is 120 seconds. Browser Type This field displays the Read more

LoadView: Test Execution Profiles

There are three LoadView test profiles: Normal User Simulation Maximum Speed Simulation (For Stress Testing) User Session Simulation   Normal User slows down page interaction and adds random delays between actions of 3 to 6 seconds. Maximum Speed  Runs the test scripts as fast as possible, essentially attempting to stress the server to maximum capacity User Session  Simulates a slower user interacting with the website with the slowest page interactions and random delays between actions of 6 to 10 seconds.

Record Video on Each Run

Device Type: BrowseView Platform, UserView Platform Record Video on Each Run will record a video capture for every single monitoring session.  If this option is not turned on the task will only record a video on the first session that errors.

Simulate a Return Visitor

Device Type: BrowseView Platform, UserView Platform If you want to see how a webpage performs for a frequent visitor or someone who already has elements from the page cached, you can turn on the return visitor flag on the task edit screen. Simulate a Return Visitor immediately revisits the webpage a second time and only records the results of the second visit. Results may differ from a first visit (which always starts with an empty cache) based upon how the browser handles things like the expiry of elements on the page.

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