Cloud Service & Website Monitoring

Cloud Service & Website Monitoring

Cloud Service & Website Monitoring

The Cloud Service & Website Monitor allow you monitor the availability and response of a website without having to install an agent on the web server. This is particularly useful for sites hosted externally by web hosting providers, who may not allow access to the underlying servers.

The website URL is monitored from one or more devices that have an Naverisk agent installed. This can be either a standard or advanced agent. The monitor measures the site response time, and is also able to test for specific text being returned from the server. By monitoring remotely, you can measure the real-world response time, including the effect of network and internet speed between the web server and monitoring device. By monitoring a URL from multiple devices, you add redundancy to the monitor, and measure performance from different locations.

Creating a Monitor

To monitor a website, a Passive Device must be added to the appropriate client. From the Devices tab, select New Device then click Create New Passive Device. Enter the device information as required then save.

The monitor then needs to be configured on a suitable device. This device can be on the same client as the passive device created above, or under a different client if required.

1. From the Monitoring tab, under Monitored URIs: select Add.

2. Enter the website URI, making sure the correct protocol is selected. The URI can be set to any available page on the site.

3. Under Device, choose the Passive Device created above

4. Set the other fields as required.

Searched Text: This is used to test for text returned within the tested web page. Setting this to text that you would see if the page is working correctly will allow the monitor to tell if the page is returning valid content or an error message. You can either test for content that should be present, or test if an error message is not present.

Threshold: An alert will be generated if the website does not respond within the configured time, allowing you to check for degraded performance.

Interval: The frequency that the monitor will poll the website

Failure threshold: The number of consecutive failed polls before an alert is raised. This can be set to a higher number to prevent occasional slow responses etc from creating alerts unnecessarily.

SLA Class: The desired classification. This would typically be set to Performance or Availability

SLA Status: The required SLA status severity used when an alert is created

SLA Trigger Text: Optional text added to the ticket trigger field when an alert is created. This can provide additional information or details about the alert.

Once the required fields have been completed, click save. Note that multiple URI monitors can be added to a device.

You will also need to save the OS template on the device so that the monitor is added.

Adding a Monitor to an OS Template

In addition to manually adding a Monitored URI to an individual device, you can also add one or more monitors to any OS Template.

Under Settings, go to OS templates and edit the required template. You can also copy an existing template or create a new one.

You can add a URI monitor under the Availability section. The monitor is configured in the same way as above. Once the template is saved, the URI monitor will be added to all devices currently using the template. when adding a URI monitor to an OS template, consideration should be given to the number of devices using that template, to prevent a large number of devices all monitoring the website and creating excessive load.

Further details on using OS templates can be found in the Knowledge Base.

Viewing Monitor Details

By opening the Passive Device created for the monitor, you can view tickets created by the monitor, and see the devices that the monitor is run from.

Advanced Concepts

Monitoring dynamic web pages

Many websites use dynamic pages driven by a back-end database. These can include catalogs, shopping cart sites, searches, blogs and forums. By referencing a dynamic page in the monitor, you can verify that the database and back-end code are performing correctly, however as the page is dynamic it can be difficult to search for specific text as it may not appear over time. For example, on a blog, if you are searching for text in a specific post, as new posts are added, the one with the text may eventually not be shown on the main page.

In many cases, we can request the specific article, post or other data within the URL. A typical example would look like:

www.website.com/search.php?article=text

Other sites may use what looks like a static URL (e.g. blogs) however the content is still fetched dynamically. Regardless of the method, by copying the specific dynamic page URL into the monitor will always return the expected page.

Using multiple monitors on one site

By configuring multiple monitors for one website, you can create more granular monitoring. Some examples include:

  • Different SLA Statuses. By creating monitors set to different threshold times, you can create alerts of increasing severity depending on how slow the site is responding.
  • Testing multiple pages in on a site. Create a monitor for each page required. Different threshold times could be created depending on the complexity/size of a page or whether it is static or dynamic.
  • Test for specific errors. By searching for a specific error message in each monitor (using the not-equal-to option), a separate alert will be raised for each error condition. The SLA Trigger Text field can be used to provide details of the error.
  • Monitor performance across distributed locations. By creating monitors on devices in multiple physical locations, the website performance can be verified from different networks/internet connections. This also provides monitoring redundancy.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!

Configure Naverisk to Monitor Veeam Backups

Configure Naverisk to Monitor Veeam Backups

Configure Naverisk to Monitor Veeam Backups

This guide will help you configure Naverisk to monitor Veeam backups. It should be read in conjunction with http://kb.naverisk.com/en/articles/2810682-backup-monitoring which describes the backup monitoring capabilities of Naverisk in more general terms.

This guide has been written and tested using the Veeam Agent for Windows, however it is also applicable for monitoring a central Veeam server, in which the event log name needs to be changed but all other settings remain the same.

Determining Veeam Event Log Entries

Veeam backup writes all events into an application event log called Veeam Agent (if using the Windows agent) or Veeam Backup (if using a Veeam server).

Log Entry Types

1. Backup Started

This entry is created each time a backup job is started, and has the event ID of 110, and a log level of Information. If the job does not run, no entry is created.

Log Entry Types

1. Backup Started

This entry is created each time a backup job is started, and has the event ID of 110, and a log level of Information. If the job does not run, no entry is created.

2. Backup Successful

This entry is created when the backup job completes successfully. The event ID is 190 and the log level is Information

3. Backup Failed

Should the backup job fail for any reason, a log entry is created, also with ID of 190, however the log level is Error.

We will use these three events to create monitoring in Naverisk that will create tickets if a backup does not start or if it starts and fails. It will also maintain the history of successful and failed backups for reporting purposes.

3. Backup Failed

Should the backup job fail for any reason, a log entry is created, also with ID of 190, however the log level is Error.

We will use these three events to create monitoring in Naverisk that will create tickets if a backup does not start or if it starts and fails. It will also maintain the history of successful and failed backups for reporting purposes.

Creating a Device Role

To provide correct alerting and reporting, the monitoring must be configured in a Device Role, and not by configuring the event log rules on an individual device. A device role template for Veeam Backups is available on our routine store, however we will discuss the procedure for creating one below. It is recommended that you read these steps even if you plan on importing the template, so you understand the settings used.

Create a new Device Role under Settings and give it an appropriate name (e.g. Backups – Veeam). You will then need to add Monitored Event rules for the three Event Log entries created by Veeam, described above.

1. Backup Start – This rule will check that the backup job starts as scheduled

Add a new event rule, and configure it as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 110

Event Description allows matching of text in the event description, it is not required for Veeam backup monitoring.

Set the SLA Class to Backup. This class will only generate a ticket if the SLA status is Failure, and also allows reporting history to be kept.

SLA Status: Failure – we are checking for backups that do not run, so we want an alert to be generated.

Set the Ticket Group and Ticket Trigger Text to your preferences.

Reporting Status: None – if the backup does not run, we want a blank entry for that day in the report, to indicate no backup was made

Tick Timed Event. When this is enabled, a ticket is generated if the event (backup started) is not received during the time window specified. If the backup starts and generates the event, this is detected, and no ticket is generated.

Set the desired start and end time. This should encompass the scheduled start time of the backup job, with some margin before and after to allow for any difference in system time. Note that it is not necessary to cover the entire backup period, just the time is should start.  Note that the start and end time must not cross 12:00am e.g. Start 11:30pm, End 12:30am.

If a backup job is started outside the specified time period, a ticket will be generated to warn you of an unscheduled backup starting.

2. Backup Successful – This rule checks for successful completion. A ticket is not generated, however the event is recorded for reporting.

Add a new event rule, and configure it as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 190

SLA Class: Backup

SLA Status: Information

Reporting Status: Success

2. Backup Successful – This rule checks for successful completion. A ticket is not generated, however the event is recorded for reporting.

Add a new event rule, and configure it as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 190

SLA Class: Backup

SLA Status: Information

Reporting Status: Success

3. Backup Failed – This rule checks for failed backups and generates a ticket. The event is also recorded for reporting.

Add a new event rule as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Error

Event ID: 190

SLA Class: Backup

SLA Status: Failure

Ticket Trigger Text: Backup Failed, or similar, to your preference.

Reporting Status: Failure

Save the Device Role, and copy if necessary to your clients. Add the role to the Device Profiles or individual devices as required.

With the monitoring in place, the following results will occur:

Monitoring backups that are taking too long

In some cases it is useful to know if a backup has not completed within the desired timeframe – for example a backup still running when business hours start could impact system performance. If required, an additional event rule can be added to generate a ticket if the backup has not completed within a specified period.

Add a new event rule as follows:

Event Source: Veeam Agent or Veeam Backup as applicable

Event Type: Information

Event ID: 190

SLA Class: Backup

SLA Status: Failure

Reporting Status: None

Select Timed Event and set start time to the scheduled start, and end time to the end of the backup window.

This rule will create a ticket if the backup is still running at the end of the backup window. No ticket is created if the backup completes within the window. The rule does not have any effect on the backup report.

Backup Reports

The rules configured above will result in a backup report showing the backup status for each day as follows:

Success – backup completed successfully

Failure – backup completed with errors

Warning – no backup ran.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!

Deploy & Monitor Webroot from Naverisk

Deploy & Monitor Webroot from Naverisk

Deploy & Monitor Webroot from Naverisk

This article covers how to deploy the Webroot application to devices using Naverisk, monitor that the Webroot service is running, and configure alerts to be sent from the Webroot console to generate tickets in Naverisk.

Deploying Webroot to Devices

A script pack is available that will check a device to see if Webroot is currently installed, and will install it if not present. This script can be run on demand, or triggered using a scheduled task.

If not already available in your Naverisk console, download the Webroot Auto Installer script pack from the Routine Store. In Naverisk, go to Settings > Script Packs and click Upload Script Packs to import the Webroot script pack. This would normally be imported to the top level of your Client Tree, so that it is available to devices at all your clients.

Before deploying the script pack, you must update it with your Webroot license key. The deployment will fail if the license key is not set in the script pack.

Obtain your Webroot license key. It will be in the form XXXX-XXXX-XXXX-XXXX-XXXX

Edit the script pack, enter your license key under Parameters

Save the script pack. It is now ready for use. Should your license key change, you will need to update the script pack accordingly.

Monitoring the Webroot Service

A Device Role is available on the routine store that checks that the Webroot service is running. Should it stop for any reason, an alert will be raised in Naverisk.

Download the Device Role from the routine store, and import it into Settings > Device Roles. Copy the device role to all clients that require Webroot service monitoring.

Add the device role to the desired devices either by adding it to the applicable Device Types, or individually to each device under the Monitoring tab.

Configuring Alerts

Webroot endpoints communicate directly to the Webroot console when events such as threats being detected occur. It is easy to configure the console to send these alerts to Naverisk so that your AV monitoring/alerting can be consolidated in one location.

In the Webroot console, click on the Alerts tab and create a new alert.

Name the alert, and select the required alert type. This would typically be Threat Detected, however you can also configure alerts for other events such as Endpoint Installed.

Under Recipients, enter the email address you are using for incoming support emails in Naverisk.

Select the desired Sites. This allows you to create separate alerts for different sites/clients if required.

You can customise the template used for the email by adding attributes from the list at the bottom of the window.

These could be used in conjunction with the Naverisk Automation Rules by testing on the values populated by these attributes – for example, test for site name to assign the client in Naverisk.

Once configured, whenever an event is received by the Webroot console, an email will be sent to Naverisk that will raise a support ticket. This frees your engineers from having to monitor the Webroot console as well as Naverisk for AV alerts.

Automate your service delivery with Naverisk:

Naverisk is an all-in-one RMM, Service Desk & PSA solution for MSPs and IT Professionals.

From monitoring and device management to ticketing and billing, Naverisk removes the need for running multiple programs.

Take advantage of Naverisk’s powerful automation features with a FREE demo today!

You will love the Naverisk experience. Try us today!