Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Quadrotech Nova Current - User Guide

Adoption Accelerator Delegation & Policy Control Reporting Tenant Management System Settings About

Service Monitoring

Many organizations move their on premises services to the cloud in hopes of getting better service than they have—better up-time, security, resiliency, data protection, etc. Nova Service Monitoring provides Office 365 workload availability monitoring that helps an organization see whether Office 365 is as reliable as the organization hoped. This is achieved through:

·Performance monitoring

·Outage location tracking

·Workload availability monitoring

·SLA reporting

 

This information is invaluable when troubleshooting Office 365-related problems. The service gives an organization quick answers to questions like:

·Is the service available? Nova Service Monitoring offers global awareness of Office 365 service status.

·Is it performing like it should? Find answers in SLA planned-versus-actual reporting.

·Can a certain user use the service? Helpdesk troubleshooting is easier with per-user visibility.

·Are there any problems with the service that might affect my users? Check per-location statuses to find out.

 

Nova Service Monitoring gives you access to historical and real-time monitoring data, so you can see what is broken now, what was broken in the past (including when it broke and when it started working again), and a historical record of latency, uptime, etc. This allows you to make data-driven decisions.

You can monitor service availability globally, or focus on a specific location.

Here is a video with more information about Nova Service Monitoring.

What does it monitor?

Microsoft data centers are automatically monitored for Office 365 workload availability, outages, performance, etc.

Besides monitoring those data centers, Nova Service Monitoring can be configured to track availability and performance of other services, as well.

For example, if you have a lot of users in a certain location, let us say Toronto, you could install a beacon on a virtual machine in Toronto. Then, Nova Service Monitoring reaches out to a mailbox that you configure and tests the availability/performance.

In this example, it will test the connection from Toronto to the data center where the mailbox exists

Service Health beacons, workloads and rules

A beacon is a Windows service, running on a virtual machine (Windows 2012+ or Windows 8+). The virtual machine is dedicated to running this service. A dedicated VM is important because the beacon is testing all aspects of the email user experience and in order to get clean baseline metrics, you need a dedicated VM.

 

It is important to constantly monitor the end-user experience because:  

·Gives helpdesk personnel foresight for potential issues with a user's experience which results in tickets to helpdesk, infrastructure admins, network admins, etc.

·Gives administrators and first level support people a baseline of performance and understand the impact of changes in the environment.  

·Can provide insight into network conditions and changes to improve user experience.  

 

A Beacon manages one or more Office 365 Workload, but only one Workload of each type. A Beacon is visually represented in the Nova Monitoring dashboard as a status icon or a cluster of icons depending on map zoom level.  Quadrotech has provided a worldwide fleet of Beacons free for Nova subscribers. An example of that is below:

 

Beacons1

Customers can install their own Beacons in locations throughout their environment to provide tier 0 user experience monitoring.

What is a workload?

Each workload runs a unique set of user experience tests.

 

Active Directory Federation Services (AD FS) Workload tests: Tests SSL certificate health and the performance and functionality of federated sign-in through your on-premises AD FS farm. Combine with the URL scan tests to get a complete picture of your AD FS infrastructure.

 

Exchange Online Workload tests: Open Mailbox, Create Email, Create Task, Create Folder, Create Meeting, Resolve User against Global Address List, Download Attachment, Free/Busy lookup, Search and send email. All these tests allow you to correlate user experience with potential network or service-related issues. (Read more)

 

Exchange ActiveSync Workload tests: Simulates Exchange ActiveSync device synchronization, including opening mailboxes, creating tasks and meetings, checking free/busy state, resolving users against an address list. These tests help measure the actual performance and availability that mobile device users will see against Exchange Online.

 

Mail routing Workload tests: These tests inject mail using Exchange Web Services (EWS) and SMTP, measuring Autodiscover performance, logon performance and functionality, and the performance, end-to-end latency, and functionality of mail routed between mailboxes in the service.

 

OneDrive for Business Workload tests: performance latency for logon, file upload, and file download.

 

Skype for Business and Teams Workloads tests: Runs network analysis tests to identify issues in call quality and measures the following: Jitter, Degradation, Packet Loss, Packet Reorder, Latency and Network MOS. Additionally, it provides valuable information that can be used to further investigate network issues which affect call quality. Open a ticket with any network admin and they will ask you source / target IP and port so they can sniff traffic. We provide all of that for you. (Read more)

 

URL scan Workload tests: Tests the SSL certificate health, HTTP response code, and response time for URLs, allowing you to monitor health of load balancers, SSL accelerators, and other devices in the network path between users and Microsoft 365.

What are monitoring rules?

There are rules applied to each test. For each test there is a pass / fail rule to identify if a test completed successfully. There are also thresholds for each test that are applied if the test completes successfully. When a workload is installed, a default set of rules is applied. A customer can modify those rules when the workload is installed, or they can wait to tune the rules to their specific requirements after they've established a baseline for their environment.

Changes to monitoring rules take effect on the next scan run by the workload. Each Workload performs its tests every 60 seconds.

Monitoring-Rules

How do I add a beacon?

Go to this section to see how to add a service monitoring beacon.

Adding a Service Monitoring beacon

There are two types of beacon you can deploy; an on-premise beacon, or a beacon deployed from the cloud.

 

Adding an on-premise beacon

info

NOTE: The on-premise beacon requires .Net Framework 5.0.

Follow the steps below to install your on-premise own beacons that will be monitored using Nova Service Monitoring.

1.Log in to Nova.

2.Click the Settings button (a gear icon) located in the top right of the page.

3.Click Monitoring, which is located under Application Settings.

4.Select Beacon Management.

5.Click Add > Beacon.

6.On Deployment Type, click On Premises.

7.Enter an email address, and then click Send. An email containing an installation code and a link to download the installer will be sent to the email address.

8.From the email, download the installer to your Windows server.

9.Run the installer. When prompted, enter the installation code from the email.

10.Review the logs to ensure the beacon was registered successfully.

 

From here, you can add a workload to the beacon. The steps to do that are below.

 

info

NOTE: Until you add workloads to your beacon, the beacon icon on the Monitoring dashboard shows the NoData icon. After you add workloads to the beacon, you will see test results in the dialog after one minute:

SMBeacon

By default, a scan of the workloads occurs every 60 seconds. However, the status on the dashboard map only changes if the beacon status has changed since the last scan.

 

Adding a cloud-based beacon

There is also the option to add a beacon from an Azure container. To do this:

1.Log in to Nova.

2.Click the Settings button (a gear icon) located in the top right of the page.

3.Click Monitoring, which is located under Application Settings.

4.Select Beacon Management.

5.Click Add > Beacon.

6.On Deployment Type, click Azure Container.

7.Select the Azure region where you would like the beacon to be placed from the drop-down menu.

8.Then, either:

a.Use the map to locate the exact location where the beacon will be placed, or

b.enter the co-ordinates of your desired location into the longitude and latitude boxes.

9.Enter the name of the Beacon in Name.

10.In Beacon City, enter the location name where the beacon is placed.

11.Ensure that the details are correct, then click Save. The beacon will then be created. This may take several minutes.

12.Once the status is panel.add.beacon.status.Ready, click Close.

 

From here, you can add a workload to the beacon.

 

Adding a workload to a beacon

Once you have successfully added a beacon, you can add a workload to receive monitoring data. To do this:

1.Select the beacon you would like to add a workload to, then click Add, then Workload.

2.From Workload Type, there are three different options:

 

Exchange Online

3.Enter the Login Name and Password of the user.

4.Enter the Target Mailbox address that the beacon will monitor.

5.Optionally, choose to configure the Monitoring Rules.

6.Click Save, or Next, depending if you have chosen to configure the Monitoring Rules.

 

OneDrive

3.Enter the Login and Password of the User.

4.Enter the URL of the OneDrive.

5.Optionally, choose to configure the Monitoring Rules.

6.Click Save, or Next, depending if you have chosen to configure the Monitoring Rules.

 

URL Scan

3.Enter the URL where you would like the beacon to be deployed.

4.Optionally, choose to configure the Monitoring Rules.

5.Click Save, or Next, depending if you have chosen to configure the Monitoring Rules.

Your workload should then begin to install. See its progression under the Status field of the beacon.

Configuring monitoring rules

You can configure the rules for your beacons to alert you.

1.Select the Test Name of your rule. These are:

oHTTP Response Status Code

oTotal Execution Time

oCertificate Name

oCertificate Alternative Names

oCertificate Expiration Date

oCertificate Error Status

2.Select your Rule Type:

oValue Validation

oExecution Failure

3.Select your operator. You can select values:

onot equal

oequal

ostarts with

oends with

ocontains

omatches

4.Select the value you would like to apply to the operator.

5.Select the action that the beacon will take once this rule has been taken effect. These values are:

ocritical

odegraded

ofailed

oexecutionFailure

onotEvaluated

opassed

oinfo

6.Once you are done, click the tick icon next to the Test Name box, then click Save.

 

Editing a workload

You can change monitoring rules (pass/fail and latency) by editing the beacon's workload:

1.Click the Settings button (a gear icon) located in the top right of the page.

2.Click Monitoring, which is located under Application Settings.

3.Select Beacon Management.

4.Select Edit > Workload.

5.Click the ellipsis button (...) and select Edit.

6.Make desired changes (using the screen shown below), and then click Save.
SMEditWorkload

Stopping a workload

You can stop a workload to stop future scanning.

1.Click the Settings button (a gear icon) located in the top right of the page.

2.Click Monitoring, which is located under Application Settings.

3.Select Beacon Management.

4.Select Edit > Workload.

5.Click the ellipsis button (...) and select Stop.

After a workload is stopped for about 5 minutes, the old test results are removed and the workload status changes to Critical. The beacon status changes to NoData.

Removing a workload

Removing a workload removes it from the server running the beacon. Here is how to do it:

1.Click the Settings button (a gear icon) located in the top right of the page.

2.Click Monitoring, which is located under Application Settings.

3.Select Beacon Management.

4.Select Edit > Workload.

5.Click the ellipsis button (...) and select Remove.

How to create a notification for issues encountered on beacons

When custom beacons have been deployed, it is often required to create some notifications about the health/status of the beacon. For example, you may want to configure a notification to alert an administrator if a particular test on a workload fails or takes too long to run.

 

The first step is to access the monitoring settings from the menu:

Beacon-1

 

After selecting the option from the menu you will see this page:

Beacon-2

Select Notifications from the list of options on the left, and you will see all the existing notifications for the tenant.

You can then begin adding a new notification by clicking on +Add, which will take you to this screen:

Beacon-3

 

To configure a notification when a workload result is degraded/poor:

·Beacon Name = the beacon you want to be notified about

·workload = name of the required workload

·severity = degraded

 

If you want to know when any of the tests result in degraded or poor responses:

·Beacon Name = the beacon you want to be notified about

·severity = degraded

The final thing to configure is how to receive the notifications. To do this click on the notifications icon at the top right of the user interface, and choose ‘My alert settings':

 

Beacon-5

 

On the page in the interface you can choose different severities of alert, along with the method you want to receive the alert:

 

Beacon-6

 

info

NOTE: In order to configure notifications the user that performs the actions outlined here needs to be in the System Administrator role.

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation