Prerequisites for the Azure Logic Apps Logging and Monitoring agent
This page describes the prerequisites for successfully installing and running the Azure Logics Apps Log and Monitoring Agent.
Instances of this agent can be installed on-premise using TCP/IP for local network access and/or in the cloud/off-site using Service Bus Relaying (see also the external link for additional information MicrosoftServiceBusRelayingLink) as long as the Log API can be accessed on the configured port.
Our recommendation is to that you keep this agent close to Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)
The Azure Logics Apps Log and Monitoring Agent is a Windows Service and is usually installed on the Nodinite application server.
Windows 2012 R2
|.NET Framework||.NET Framework 4.5 or later|
Cloud technologies are evolving fast and Microsoft deprecates older versions of their API's now and then. Nodinite will always support the API's supported by Microsoft. This means you need to update Nodinite and our Azure Logics Apps Log and Monitoring Agent from time to time.
Make sure to subscribe to our Release Notes
- The agent uses the Azure REST API to read logged events with tracked properties and can modify the state of your logic apps. Therefore the agent needs access rights. Carefully read and follow the instructions detailed in the Azure Applications Access user guide.
You must enable some Diagnostic Settings. You must do this, for each Logic App, where you want Logging. This setting is managed in the Azure Portal
Do use Powershell scripts to automate this requirement, part of your DevOps routine.
the EventHub must exist, and you must create Add SAS Policy:
The connection string is available in the portal, copy and paste.
The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.
- Local named account or domain account (preferred).
- Access and run-time rights
- Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.
The Azure Logics Apps Log and Monitoring Agent has both inbound and outbound communication:
- Between the Monitoring Service and the Azure Logics Apps Log and Monitoring Agent
- Between the Azure Logics Apps Log and Monitoring Agent and Azure Management API
- Between the Azure Logics Apps Log and Monitoring Agent and the Log API
The following ports must be allowed on the Windows server where the agent is installed and running:
|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 'Option 1' or 'Option 2' as documented next:
|8000||RPC||Communication initiated by the Monitoring Service|
Use Service Bus Relayed connections when Nodinite and the agent are on totally different networks.
Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.
The following Ports must be open for outbound communication with '*.servicebus.windows.net' from both on-premise and off-site:
|443||HTTPS||Secure outbound traffic|
|5671, 5672||Secure AMQP|
|9350 - 9354||Net.TCP|
|443||HTTPS||Secure outbound traffic with the Azure REST API. - Safelist the Azure portal URLs on your firewall or proxy server|
|80||HTTP||default for HTTP)|
|443||HTTPS||default for HTTPS)|