Release Notes

Configuring the Microsoft Dynamics 365 Monitoring Agent for use with Nodinite

This guide teaches how to configure the Nodinite Microsoft Dynamics 365 Monitoring Agent

Note: The Monitoring and the remote configuration is available if you first install and create the initial Monitoring Agent Configuration for the Microsoft Dynamics 365 Monitoring 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 Dynamics 365 (CRM) instances.

Dynamics 365 instance

The Dynamics CRM tab holds an array with one or more Dynamics 365 instances.

Add your Dynamics 365 instances to Monitor

• Press the Add button to add one (or more) configuration entries(s):
  
  Example configuration, 1 accordion per configuration

• Repeat this step for each of your Azure subscriptions to Log and/or Monitor with Nodinite

Click the Accordion to expand and manage the configuration.

Connection Tab

From within the Connection tab, you can perform the configuration and provide connectivity details for the Dynamics 365 instance to monitor.

Add connectivity information

For each connection, the following properties can be set:

• Name - Display name is used to create the Application within the Monitor Views. A change of this property requires an update of Monitor Views for this server.
• Uri - Address to the API for the instance of Dynamics 365
• User name - User name for the account to login with Dynamics
• Password - Password for the account to login with Dynamics

Workflows/Processing steps

From within the Workflows/Processing steps tab, you can perform the configuration for monitoring workflows and processing steps.

Configuration options for Workflows/Processing steps

• Enable monitoring of workflows - When checked, the agent will monitor CRM workflows in Dynamics 365. This option is enabled by default
• Include Draft workflows - When checked, the agent will include workflows in state draft from Dynamics CRM. This option is enabled by default
• Evaluate time for jobs in status waiting for resources - When checked, the agent will evaluate longest allowed time waiting before raising a Warning or Error alert, This option is enabled by default
• Evaluate time for jobs in status suspended waiting - When checked, the agent will evaluate longest allowed time waiting before raising a Warning or Error alert, This option is enabled by default
• Evaluate failed workflows as error - When checked, the agent will evaluate any failed workflow as Error, This option is enabled by default
• Evaluate failed processing step as error - When checked, the agent will evaluate any failed processing step as Error, This option is disabled by default
• Warning Time Span - The longest allowed time span before Warning alert (days.hours:minutes:seconds e.g. 7.12:30:59)
• Error Time Span - The longest allowed time span before Error alert (days.hours:minutes:seconds e.g. 7.12:30:59)
• History Time Span - The longest back in time to check for system job runs to list in the history for workflows (days.hours:minutes:seconds e.g. 7.12:30:59). This setting will have impact on the size for saved data.
• History Size - The max number of system job runs to list in the history for workflows

Specific workflows

You can fine-tune configuration for specific workflows. These are easier to manage directly on the listed Resource from with Monitor Views.

Click the Add button to configure a named workflow.

Specific processing steps

You can fine-tune configuration for specific processing steps. These are easier to manage directly on the listed Resource from within Monitor Views.

Click the Add button to configure a named processing step.

User audit thresholds

From within the User audit thresholds tab, you provide some details that determines the operation behaviour of the Microsoft Dynamics 365 Monitoring Agent.

• Enable monitoring of inactive users - When checked (enabled), the agent will monitor user logins in Dynamics CRM. This option is enabled by default
• Warning Time Span - The longest allowed time span before Warning alert (days.hours:minutes:seconds e.g. 7.12:30:59)
• Error Time Span - The longest allowed time span before Error alert (days.hours:minutes:seconds e.g. 7.12:30:59)
• History Time Span - The longest back in time to save user operations audit history, the last record for each user will still be saved (days.hours:minutes:seconds e.g. 7.12:30:59). This setting will have impact on the size for saved data.

Specific users

License thresholds tab

From within the License thresholds tab, you provide some details that determines monitoring for license related information for the monitored Microsoft Dynamics 365 Monitoring Agent instance.

• Evaluation Type - The type of Evaluation for the license
  • Used
  • Free
  • None
    
• Warning Limit - The max number of used licenses before a Warning alert is triggered
• Error Limit - The max number of used licenses before an Error alert is triggered

Settings tab

From within the Settings tab, you provide some details that determines the operation behaviour of the Microsoft Dynamics 365 Monitoring Agent.

• Environment
• Debug
• Culture Information
• Monitor Agent Database Connection String - Connection String to the database where the Monitor Agent can store information

Server=localhost;Database=Nodinite_MonitorAgent_DynamicsCRM;Integrated Security=SSPI;Connection Timeout=60

Installing and updating the Monitoring database is described in the following shared user guide

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.

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 Microsoft Dynamics 365 Monitoring Agent Configuration

After the successful installation of the Microsoft Dynamics 365 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 Microsoft Dynamics 365 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 Microsoft Dynamics 365 Monitoring Agent according to business needs.

   • Add or manage Monitor View

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

Related

Install Dynamics 365 Monitoring Agent
Monitoring Agents
Applications