Last updated: 2019-02-27

Add or manage a Monitoring Agent Configuration

In this section you will learn how to setup and configure a Monitoring Agent Configuration.

One Monitoring Agent Configuration is used to uniquely target/identify/configure one installed Monitoring Agent.


Click on the 'Add Monitoring Agent Configuration' button to begin enter the configuration details for one installed Monitoring Agent.

  • Name is required to create the Monitoring Agent
  • Description is optional. Enter a user friendly Description about this configuration
  • Website is optional. Provides a link for users

Add Monitoring Agent Configuration

When configuring the Monitoring Agent Configuration you must choose and configure connection settings.

The Monitoring Agents can either use:

The Service URL is always available in the 'README.txt' file located in the installation folder of the Monitoring Agent.

  • Polling Interval is required -Set how often the Monitoring Service polls for the actual state of the Resources. This value is set in Seconds using a positive Integer value.

Default is 60 seconds.

TIP: Do not poll for status updates more often than really required by your business needs. A short poll interval will add pressure on valuable system resources.

Security Tab

An Authentication Key must be entered to get access to Remote Configuration of the Monitoring Agent. The Monitoring Service must have this security setting to authenticate calls sent to the Monitoring Agent.
The Authentication Key is available in the 'README.txt' file located in the folder of the installed Monitoring.

Check the 'Monitoring Agent Configuration is authenticated' if you the Monitoring Service should use the Authentication Key settings for the connection against the Monitoring.

In order to allow Remote Configuration of the Monitoring, the connection with the Monitoring Agent Configuration must be secured using either an API key or Service Bus Relaying.

Note: If ServiceBus Relaying is being used to communicate with the Monitoring Agent a different security scheme is being used,

Shared Access Signature security Key. See the following Microsoft article for more information MDSN. The Monitoring Agent needs additional configuration for Service Bus Relaying.

Example of shared access key, use the Azure Portal to acquire real values.


Advanced Tab

Optional overrides are available in the Advanced tab.

Check the Change default Timeout if the Monitoring Agent Configuration should use a custom Timeout. The default timeout value is 120 seconds.

Check the Change default Retry handling to set custom retry values. This should only be used if the connection between the Monitoring Service and the Monitoring is using an unreliable WAN link.

Common Problems

If the Monitoring Agent Configuration is not available and/or cannot be reached it will be displayed in the list of Monitoring Agents as being offline:

A warning message can also be seen when configuring the specific view. The information is refreshed in the background and will disappear if the service comes back online or connectivity is re-established. SourceNotAvailable

Monitoring Agent Configuration Information

Remote Configuration, Monitoring Agent Configuration Information, and Available Resources

Server, Environment and Version

You can easily retrieve actual run-time values for the chosen Monitoring Agent.

Alive Check

Test the connection to the Monitoring Agent Configuration by clicking Check.

You can see the status for the last alive check as well as the time of the last check.

Monitoring Agent Configuration Information

Available Resources

Clickable List all Resources provided by the Monitoring Agent.

The list contains information about the following:

Available Resources

Next Step

Learn how to configure Remote Configuration

Monitoring Agents Overview
Add or manage a Monitoring Agent Configuration
Add or manage Monitor View

View Monitor Views
Monitor Views