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
When configuring the Monitoring Agent Configuration you must choose and configure connection settings.
- Service URL is required - The Service URL is the address for the Monitoring Service to communicate with the Monitoring Agent.
The Monitoring Agents can either use:
- Local LAN using TCP/IP
- Anywhere in the World using Service Bus Relaying
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.
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.
- Authentication Key is required - The API key or Service Bus Relaying connection information
Note: If ServiceBus Relaying is being used to communicate with the Monitoring Agent a different security scheme is being used,
Example of shared access key, use the Azure Portal to acquire real values.
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.
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.
You can easily retrieve actual run-time values for the chosen Monitoring Agent.
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.
The list contains information about the following:
- Name - The display name of the Resource
- Description - The user friendly Description for the Resource
- Application - The Application the Resource belongs to
- Category - The Categories the Resource belongs to
Learn how to configure Remote Configuration