Installing the Nodinite Azure Logic Apps Logging and Monitoring agent
Info
Use this guide to learn how to install the Nodinite Azure Logic Apps Logging and Monitoring agent. Check the Prerequisites first; that page is the one home for software, Azure access, SQL Server rights, and firewall ports.
Understanding the installation
The agent is the bridge between your Azure subscriptions and Nodinite. After installation, the Monitoring Service talks to the agent to evaluate the state of your Logic Apps, and the agent posts Log Events to the Log API, so that your users can find them in Log Views and Monitor Views. How you install it depends on your Nodinite version:
IIS web site"] end subgraph V6["fa:fa-box Nodinite v6, legacy"] MSI["fa:fa-box MSI installer"] -->|"Installs"| WS["fa:fa-gears Agent
Windows Service"] end IIS --> DB["fa:fa-database Agent Database"] WS --> DB IIS --> MAC["fa:fa-monitor-waveform Monitoring Agent Configuration"] WS --> MAC style P fill:#2678BD,color:#fff style PS fill:#2678BD,color:#fff style IIS fill:#93d16d style MSI fill:#FFD525 style WS fill:#FFD525
Diagram: The recommended v7 path (blue and green) installs the agent as an IIS web site from a Portal-generated script. The legacy v6 path (yellow) uses an MSI installer and a Windows Service. Both end with an Agent Database and a Monitoring Agent Configuration.
Key components
| Component | Role |
|---|---|
| Portal | Holds your environments and generates the PowerShell installation scripts (v7) |
| Agent | Runs as an IIS web site (v7) or a Windows Service (v6) under a service account; see Windows User Rights |
| Agent Database | Stores run state, statistics, and resubmit retry counts; deployed with DacFX (SqlPackageExecutable) |
| Monitoring Agent Configuration | Tells the Monitoring Service where the agent is, so you can use Remote Configuration and Remote Actions |
v7 vs v6 installation
| Aspect | Nodinite v7 (Portal) | Nodinite v6 (MSI) |
|---|---|---|
| Status | ✅ Recommended | ⚠️ Legacy, deprecated |
| Installer | PowerShell script generated by the Portal | MSI file, run manually |
| Agent host | IIS web site with its own port | Windows Service |
| Many agents and environments | ✅ Yes, with consistent settings | ❌ No, one server at a time |
| Guide | Install Nodinite v7 | Steps below |
Nodinite version 7
Preferred Method: Portal-Based Scripted Installation
In Nodinite v7, agent installation is automated through the Portal-based scripted installation. This modern approach:
- ✅ Automates agent installation and configuration via PowerShell scripts
- ✅ Configures multiple agents simultaneously with consistent settings
- ✅ Eliminates manual MSI installations and reduces human error
- ✅ Centrally manages all environments from the Portal
Follow the Install Nodinite v7 guide to install agents using the Portal-based approach. The Portal generates PowerShell scripts that install and configure agents automatically across your infrastructure; you set the agent's IIS web site, port, and service identity in the Agents step. When the agent runs, configure it.
Nodinite version 6 (MSI-Based Installation - Legacy)
Use this MSI installation workflow only for legacy v6 environments.
Warning
The MSI-based installation method for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for the modern Portal-based scripted installation experience; see Updating Nodinite v7.
Before you begin
First, make sure you comply with the prerequisites.
Note
You must be a local administrator to have the right to install Windows Services.
Step 1: Start the installer
Double-click the MSI file to start the installation of the Nodinite Azure Logic Apps Logging and Monitoring agent.
The installer is a single MSI file; run it as a local administrator.
Step 2: Welcome screen
When the MSI file starts, the installer shows a Welcome screen:
The Welcome screen confirms which agent you are about to install.
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 3: Accept End User License Agreement
The Licensee is ultimately responsible for making sure Nodinite products are used according to the End User License Agreement. Make sure you have the assigned formal rights to install and perform modifications to the target environment before you continue installing any Nodinite products.
You must accept the terms in the License Agreement to continue.
Step 4: Custom setup
Select the components to install and select the destination path for the installation.
The Custom Setup dialog, where you can change the installation folder.
Note
Default settings are recommended.
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Step 5: Service Account Information
Enter the credentials for the Account (the service account) to run the Nodinite Azure Logic Apps Logging and Monitoring agent.
Enter credentials
- Domain: The name of the Domain the Server belongs to. If you use a local account, use the name of the server or a . (dot) as Domain
- User: The name of the account
- Password: The password for the account
Use a domain account (preferred) or a local named account with the Log on as a service right.
Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Insufficient privileges
The installer shows this error message when the account information you provide does not meet the Prerequisites:
The installer stops here until the account has the required rights.
If you get this message, the most common reason is that the account is not allowed to run as a service or is not a local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure to enter valid credentials!
Tip
Check the local event log if there are errors (both System and Application)
Step 6: Ready to install
Now that all preparations are done, click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.
Here's an example of the Ready to install dialogue.
Step 7: Completed setup
The last step of the installation gives either a success or a premature exit.
Successful installation example
A successful installation ends with the Completed dialog.
Failed installation example
A failed installation will render a premature exit.
Click the Finish button to Exit and quit the installer.
Step 8: Add Agent as a new Monitoring Agent Configuration
When the setup has been completed with success, your default text editor opens a file named 'README.txt'. This file contains the agent's connection details needed to add it as one of your Monitoring Agents. The agent [re]generates the file on each successful start.
The steps to add the Nodinite Azure Logic Apps Logging and Monitoring agent as a Monitoring Agent in the Web Client are in a shared article:
Step 9: Install database
The Nodinite Azure Logic Apps Logging and Monitoring agent uses an Agent Database (also called the Monitoring Database). You must specify the connection string to the SQL Server instance where you want to host this database. Make sure you meet the SQL Server rights before you perform the steps below.
- In the Remote Configuration, on the Settings tab, enter the connection string; see SQL Server Connection Strings.
- Provide a name for the Agent Database that follows your naming convention, for example
Nodinite_Agent_AzureLogicApps.
- Provide a name for the Agent Database that follows your naming convention, for example
- If the account running the Nodinite Azure Logic Apps Logging and Monitoring agent has the appropriate SQL Server rights, the agent installs the database automatically. If you are performing an update, the agent updates the database when there is a new version available.
If the account does not have the rights, or you do not have the DACFRAMEWORK installed, you may need to deploy the database manually.
- Restart the agent if you change the information regarding the Agent Database.
Then configure the agent: add your Subscriptions, Event Hubs, Logging, and Workflow Monitoring.
Support
Contact our Support for additional guidance if you fail to resolve the installation problem.
Note
Additional information to aid the troubleshooting may exist in the Windows Event Logs.
Frequently asked questions
Additional solutions to common problems and the FAQ for the Nodinite Azure Logic Apps Logging and Monitoring Agent exist in the Troubleshooting user guide.