- 4 minutes to read

Prerequisites for the Nodinite Dynamics 365 Monitoring Agent

This page describes the prerequisites for successfully installing and running the Nodinite Dynamics 365 Monitoring Agent.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-heart-rate Dynamics 365 Monitoring agent) end subgraph "Dynamics 365" roAzureAPI(fal:fa-cloud Microsoft API)---roLA(fal:fa-clouds Your instance) roNI --> |SDK| roAzureAPI end

Instances of this agent should be installed close to Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)

Verified Topic
Software Requirements
What Dynamics 365 instance Rights does the Dynamics 365 Monitoring agent require?
What Windows User Rights does the Dynamics 365 Monitoring agent require?
What Firewall settings are required for the Dynamics 365 Monitoring agent?
What SQL user rights does the Dynamics 365 Monitoring agent require?

Software requirements

The Nodinite Dynamics 365 Monitoring Agent is a Windows Service and is usually installed on the Nodinite application server.

Product
Windows Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.5.2 or later

Supported Versions

Cloud technologies are evolving fast and Microsoft deprecates older versions of their APIs and SDKs every now and then. Nodinite will always support the APIs SDKs supported by Microsoft. This means you need to update Nodinite and our Dynamics 365 Monitoring Agent from time to time.

Make sure to subscribe to our Release Notes

What Dynamics 365 instance Rights does the Dynamics 365 Monitoring agent require?

See the list of SDK/API calls

What Windows User Rights does the Dynamics 365 Monitoring agent require?

The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.

What Firewall settings are required for the Dynamics 365 Monitoring agent?

The Nodinite Dynamics 365 Monitoring Agent has both inbound and outbound communication:

  1. Between the Monitoring Service and the Dynamics 365 Monitoring Agent
  2. Between the Dynamics 365 Monitoring Agent and Dynamics 365 API (using the SDK)
  3. Between the Dynamics 365 Monitoring Agent and the Monitoring Database
graph LR subgraph "Nodinite Application Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roMonitoringService --> |8000| roNI(fal:fa-heart-rate Dynamic 365 Monitoring agent) end subgraph "Dynamics 365" roNI --> |443| roBTDTADb(fal:fa-hand-holding-usd Instance) end subgraph "Nodinite SQL Instance" roNI--> |SQL,DTC,RPC,DNS |roDBMonitoringDatabase(fal:fa-database Monitoring database) end

1. Between the Monitoring Service and the Dynamics 365 Monitoring agent

The following ports must be allowed on the Windows server where the agent is installed and running:

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file)

And further with local network installation (if you install on local machine then no traffic is outside the machine):

Local network

Port Name Inbound Outbound TCP UDP Comment
8000 RPC Communication is initiated by the Monitoring Service

2. Between the Dynamics 365 Monitoring agent and Dynamics 365 instance

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic with the Dynamic 365 APIs using the SDK

3. TCP Ports between Dynamics 365 Monitoring agent and SQL Server instance with monitoring database

The Monitoring agent requires outbound ports to be opened. Since Nodinite is highly configurable, the actual ports in use may differ from what's being exampled here.

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide
88 Kerberos Review 'Microsoft Kerberos' user guide
135 DTC/RPC This port is shared between many Windows Services
1433/... SQL Server instance ports (multiple) Depends on policies and settings on target environment. Please review the How to configure RPC dynamic port allocation to work with firewalls user guide

What SQL user rights does the Dynamics 365 Monitoring agent require?

The service account running the Dynamics 365 Monitoring Agent must have the following rights assigned:

Nodinite Dynamics 365 Monitoring database

To improve performance all operations initiated from the Web Client/Web API when asking the Nodinite Dynamics 365 Monitoring Agent for data will use a SQL based Monitoring Database.

  • db_owner (required to apply DACPAC updates)

List of API Calls

API Call Privilege Purpose
RetrieveOrganizationsRequest System User account Registered users and logon history
RetrieveVersionRequest
RetrieveDeploymentLicenseTypeRequest prvReadLicense
DeviceRegistrationRequest
RetrieveLicenseInfoRequest prvReadLicense
QueryExpression - Audit.EntityLogicalName, Columns: objectid, createdon, operation, action, userid Audit
QueryExpression - Workflow.EntityLogicalName, Columns: createdon, name, description, statecode, category, workflowid, activeworkflowid Workflow
QueryExpression - Solution.EntityLogicalName, Columns: solutionid, uniquename Solution
QueryExpression - SdkMessageProcessingStep.EntityLogicalName, Columns: createdon, name, description, statecode, introducedversion, mode Processing step

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite Dynamics 365 Monitoring Agent exists in the Troubleshooting user guide.

Next Step

Install Dynamics 365 Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration