Release Notes
Configuring the Nodinite Azure Monitoring Agent
This guide teaches how to configure the Nodinite Azure Agent.
Add or manage:
- Subscriptions
- Resource groups
- Storage accounts
- Triggered Web Jobs
- Continous Web Jobs
- Functions
- Data Factories
- Application Insights
- Event Grid Topics
- Event Hub
- API Management Services
- Certificates
Note: The Monitoring and the remote configuration is available if you first install and create the initial Monitoring Agent Configuration for the Azure Agent. First-time users start here
Remote Configuration
As a Nodinite Administrator, click on the 'Configuration' button to open a modal to configure the agent:
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 has the use of Remote Actions feature enabled.
You must be a Nodinite Administrator, to Manage the collection of Azure Subscriptions.
Add Subscription
First, you need to add one or more Subscriptions. Click on the Add button in the Azure Monitoring tab.
Click on the Add button to add a Subscription to Monitor.
Then, expand the accordion.
Each Subscription is on the list. Click on the accordion to expand the entry.
Each configuration has a unique name. Next, give the configuration entry a unique name.
You must enter a name for the Subscription configuration.
Add Web Jobs
Azure access information is required, follow the 'Azure Applications Access' user guide first if you have not yet configured and created an Azure AD application and service principal that can access resources
No changes to the existing solutions must be made!
The Web Jobs tab holds an array with zero or more subscription/resource group entries.
Add your Resource groups for Azure Subscriptions to Log and Monitor
Press the
Add
button to add one (or more) Azure subscription(s):
An example subscription configuration with one accordion per configuration.Repeat this step for each of your Azure subscriptions to Log and/or Monitor with Nodinite
Configuring the Azure Subscription
Click the Accordion to expand the subscription configuration and you can then manage the content of the configuration.
Add connectivity information, client secret is masked
For each subscription, the following properties can be set:
- Enabled - When not checked, no monitoring at all is performed for any Azure Storage configuration for this subscription
- Display Name - The name for this monitoring configuration.
This name is also the prefix part of the application naming scheme
- Description User friendly description for this configuration
- Subscription Id - GUID
- Tenant Id - GUID
- Application Id / Client Id - GUID
- ClientSecret - your secret password
Note: If you update a working client secret with a new one, you may need to restart the agent to apply the changes. The token is cached for one hour.
TIP: See Azure Application Access page for additional information and learn how to obtain the mandatory values
Configuring Resource Groups
Click the Resource Groups tab to manage resource groups to include in monitoring.
- Enabled - When checked, monitoring of this Resource Group is enabled
- Resource Group - Name of the resource group to monitor
Example of configuration of named Resource Groups
You can add as many Resource Groups as you like
Configuring Triggered Web Jobs
From within the Triggered Web Jobs tab you can manage the following monitoring properties :
-
- Global - Default values used when not overridden by a specific setting
-
- Specific queue settings - Overrides global configuration on named Web Job
Specific Web Jobs
You can override general thresholds with specific thresholds for named Web Jobs.
!Specific Web Jobs]6
Example of configuration of user-defined thresholds for named Web Job
Triggered Web Jobs Global configuration
Enable monitoring, determine if Monitoring of Web Jobs for this configuration is enabled or not
Enabled whenChecked
or Disabled whenUnchecked
Time-based evaluation Time-based evaluation is always evaluated. If you do not want to perform an evaluation based on time then simply provide long enough thresholds.
State | Name | Data Type | Description |
---|---|---|---|
Warning TimeSpan | Timespan 00:05:00 (5 minutes) | Web Job should run every configured time interval otherwise set Warning alert | |
Error TimeSpan | Timespan 01:10:00 (1 hour 10 minutes) | Web Job should run every configured time interval otherwise set Error alert | |
Duration Warning | integer | Longest allowed time to run otherwise set Warning alert | |
Duration Error | integer | Longest allowed time to run otherwise set Error alert |
Triggered Web Jobs Specific configuration
The Specific configuration is where you name a Web Job and configure individual thresholds.
- App Service Name - The name of the App Service where this specific web job is configured/running
- Web Job Name - The name of the specific web job
The rest of the properties are the same as already described in the global configuration.
TIP: It is much easier to perform specific configurations using the Edit threshold menu item available on the Actions button in the list of queues (Resources) with Monitor Views with [Remote Actions Option][Monitor View - Remote Actions Option] checked.
Continuos Web Jobs
From the Continuous tab, you can manage monitoring options for continuous Web Jobs.
ContinousWebJobsTab.png
- Enable monitoring, determine if Monitoring of Web Jobs for this configuration is enabled or not
Enabled whenChecked
or Disabled whenUnchecked
Add Azure Storage
Add Data Factory
Settings tab
From within the Settings tab, you provide some details that determine the operation behaviour of the Azure Agent.
- Environment
- Debug
- Culture Information
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
As 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.
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 Azure Agent Configuration
After the successful installation of the Azure 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 Azure Agent can be performed before the steps outlined below has been executed.
Configuration Steps
Add and configure a new Monitoring Agent Configuration
-
Connection information is available in the
README.txt
file in the installation folder
-
Use the Remote Configuration feature to configure the agent. Detailed at the beginning of this user guide.
Create one or more self-service enabled Monitor Views that include the selected Resources provided by the Azure Agent according to business needs.
Fine-tune specific settings directly on Resources using Remote Actions