f Microsoft DNS Agentless Monitoring | Opsview

You are here

Microsoft DNS Agentless Monitoring

Requires Opsview Cloud or Opsview Monitor 6.7
check_circle
Opsview Supported

Microsoft DNS Agentless Opspack

Microsoft DNS (Domain Name System) is an implementation of DNS services that has come packaged with Windows Server since Windows NT. A DNS server allows client computers to request memorable alphanumeric domain names by returning the correct IP addresses for these names so that computers may communicate.

What Can You Monitor

With this Opspack you can monitor the status of a Microsoft DNS instance in detail with service checks that cover the amount of caching memory being used, the rate of recursive queries and requests and how the server is handling them.

Service Checks

Service Check Description
Microsoft DNS Agentless - Caching Memory Shows the total amount of caching memory used by the DNS server
Microsoft DNS Agentless - Recursive Queries Statistics Shows the rate at which recursive queries are received, failed and timeout by the DNS server
Microsoft DNS Agentless - Requests Statistics Shows the rate at which queries are received and responses are sent by the DNS server per second

Prerequisites

  • Ensure your Opsview Monitor version is at least 6.7.0. Check Opsview Release Notes for the latest version of Opsview Monitor.
  • To use this Opspack, your Windows host must first be configured for Powershell Agentless Monitoring.

Setup Windows Host for Monitoring

By default, Windows hosts will not allow remote PowerShell scripts to run, which is required for Opsview Agentless Monitoring plugins to work.

This can be configured manually by the Windows Host administrator, or automatically using our recommended approach by running the ConfigureRemoting.ps1 Powershell script on the Windows Host.

Powershell Agentless Monitoring requires at least version 5.0 of Powershell. Check the Powershell version on your Windows Host by running:

$PSVersionTable.PSVersion

Run the ConfigureRemoting.ps1 script with Administrator privileges using a Powershell terminal. This will configure firewall rules, self-signed SSL certificates and authentication for PowerShell remoting.

Check this has been configured properly by running:

winrm quickconfig

You should get the following output:

WinRM service is already running on this machine.
WinRM is already set up for remote management on this computer.

By default port 5985 must be opened from the Opsview monitoring server to the Windows host you wish to check. WinRM utilises the HTTP/HTTPS protocol and can be configured to use certificates to secure the data in transit.

Ensure the service is listening by running:

For HTTP: netstat -an | findstr 5985

For HTTPS: netstat -an | findstr 5986

When using basic authentication with WinRM, the following commands must also be run on the windows host:

winrm set winrm/config/service/auth '@{Basic="true"}'
winrm set winrm/config/service '@{AllowUnencrypted="true"}'
winrm set winrm/config/client/auth '@{Basic="true"}'

If you receive a 500 error, which is a known issue on Windows Server 2016, you may need to install WinRM-IIS-Ext. You can do so by running the following command:

Add-WindowsFeature winrm-IIS-Ext

Setup and Configuration

To configure and utilise this Opspack, you need to add the 'Application - Microsoft - DNS Agentless' Opspack to your Opsview Monitor system.

Note: It is recommended for the 'OS - Windows Base Agentless' Opspack to also be installed in your Opsview Monitor system

Step 1: Import the Opspack

Download the application-microsoft-dns-agentless.opspack file from the Releases section of this repository.

Navigate to Host Template Settings inside Opsview Monitor and select Import Opspack in the top right corner.

Then click Browse and select the application-microsoft-dns-agentless.opspack file. Click Upload and then click Import when the file is uploaded.

For more information, refer to Opsview Knowledge Center - Importing Opspacks

Step 2: Add the Host Template

Add the Application - Microsoft DNS Agentless Host Template to your Opsview Monitor host.

For more information, refer to Opsview Knowledge Center - Adding Host Templates to Hosts.

Step 3: Add and configure variables required for this host

Variable Description
WINRM_TRANSPORT Used for authenticating with the remote host. The Value is the Authentication Transport Type - must be one of: Basic, Certificate, Kerberos or NTLM. NOTE: CredSSP is not supported. Override the Username and Password with the credentials to be used for authentication with the remote host. Scheme can be overridden to make the check use HTTP (defaults to https). Extra arguments can be used to pass extra arguments to check_by_winrm.py
KERBEROS_REALM Only required if authenticating using Kerberos. The Value is the Kerberos realm.

For more information, refer to Opsview Knowledge Center - Adding Variables to Hosts.

Step 4: Apply changes and the system will now be monitored

Microsoft DNS Agentless Service Checks