- 4 minutes to read

Configuring the Nodinite Windows Server Monitoring Agent

This guide teaches how to configure the Nodinite Windows Server Monitoring Agent.

Note: The Monitoring and the remote configuration is available if you first install and create the initial Monitoring Agent Configuration for the Windows Server Monitoring Agent. First-time users start here.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal to configure the agent:

RemoteConfiguration
Click the 'Configuration' button to open a modal to configure the agent.

Many specific configurations can also be made directly on the Resource using the Action button if the Monitor View uses Remote Actions feature enabled.

You must be a Nodinite Administrator to Manage the collection of Windows Servers.

Add Windows Server

The Nodinite Windows Server Monitoring Agent account must be a local administrator on the target server to monitor; Make sure to review the Prerequisites.

The agent performs Monitoring according to the user-defined configuration per Windows Server.

The Windows Server tab holds an array with zero or more Windows Server configurations.
Empty WindowsServer Tab
Add your target Windows Server(s) to monitor

  • Press the Add button to add one (or more) Windows Server(s):
    Empty Accordion
    Example Windows Server configuration, one Accordion per configuration.

    Repeat this step for each of your Windows Servers to monitor with Nodinite

To manage the configuration; Click the caret down icon to expand the Windows Server accordion.

  • Enable Monitoring of this Windows server configuration - When checked, enables the Monitoring of the Windows Server. Otherwise, Monitoring is disabled.
    Enabled Windows Server configuration
    Example of an Enabled Windows Server configuration

    Disabled Windows Server configuration Example of a Disabled Windows Server configuration.

Tabs

General Tab

Click the General tab to manage essential information about the Windows Server to include in the Monitoring.

General tab
Example of the 'General' tab

  • Name - The user-friendly Application name (parent for the collection of Resources).

Changing the name may require reconfiguration of affected Monitor Views.

  • Description - A short user-friendly description for this configuration.
  • Host-name or IP address - The host-name or IP address of the Windows Server to monitor.

Resources per host will be grouped by the Application concept, using the value from the Name text field.
Application Filter
Application filter by Display Name

Settings tab

From within the Settings tab, you provide some details that determines the operation behaviour of the Windows Server Monitoring Agent.

  • Environment
  • Debug
  • Culture Information

SettingsTab

Environment

Part of the common features shared with all Monitoring Agents, there is an option to set the name of the target Environment, for example, TEST, QA, PROD.

Debug

Part of the common features shared with all Monitoring Agents, there is an option to set the Debug flag for additional file logging that can be enabled/disabled as needed. Default is unchecked.

Culture Information

The Culture Information setting determines how time-based data from this agent is presented in the Web Client/Web API.

Save

You must click Save for changes to be written to the agent and take effect.
Save and Close buttons

NOTE: The delay in presenting the new evaluated state depends on the synchronisation interval set for the Monitoring agent. Click the Sync Now button to force an immediate synchronisation.

Save and close, save, and close the dialogue.
Cancel, close the dialogue without saving any changes.


Add Windows Server Monitoring Agent Configuration

After the successful installation of the Windows Server Monitoring Agent you must provide Nodinite with connection details, so the Monitoring Service knows there's a new guy in town.

No Monitoring or other configuration of the Windows Server Monitoring Agent can be performed before the steps outlined below has been executed.

Configuration Steps

  1. Add and configure a new Monitoring Agent Configuration

    • Connection information is available in the README.txt file in the installation folder

  2. Use the Remote Configuration feature to configure the agent. Detailed at the beginning of this user guide.

  3. Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Windows Server Monitoring Agent according to business needs.

  4. Fine-tune specific settings directly on Resources using Remote Actions


Next Step

Add or manage a Monitoring Agent Configuration
Add or manage Monitor View
Update

Install Windows Server Monitoring Agent
Monitoring Agents
Applications