- 5 minutes to read

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.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-heart-rate Azure Logic Apps Logging and Monitoring agent) end subgraph "Azure Cloud / Subscriptions" roAzureAPI(fal:fa-cloud Microsoft Azure API)---roLA(fal:fa-clouds Your Logic Apps) roNI --> |REST| roAzureAPI end

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)

Verified Topic
Software Requirements
What Azure User rights does the Azure Logic Apps Logging and Monitoring agent require?
What Windows User Rights does the Azure Logic Apps Logging and Monitoring agent require?
What Firewall settings are required for the Azure Logic Apps Logging and Monitoring agent?

Software Requirements

The Azure Logics Apps Log and 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 or later

Supported Versions

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

What Azure User rights does the Azure Logic Apps Logging and Monitoring agent require?

  • 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.

Logging

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

Enable Logging

Do use Powershell scripts to automate this requirement, part of your DevOps routine.

the EventHub must exist, and you must create Add SAS Policy:

Add SAS Policy

Option Name
Manage
Send
Listen

The connection string is available in the portal, copy and paste.

What Windows User Rights does the Azure Logic Apps Logging and 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 Azure Logic Apps Logging and Monitoring agent?

The Azure Logics Apps Log and Monitoring Agent has both inbound and outbound communication:

  1. Between the Monitoring Service and the Azure Logics Apps Log and Monitoring Agent
  2. Between the Azure Logics Apps Log and Monitoring Agent and Azure Management API
  3. Between the Azure Logics Apps Log and Monitoring Agent and the Log API
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-heart-rate Azure Logic Apps Logging and Monitoring agent) roMonitoringService --> |8000/443| roNI roLogAPI(fal:fa-cloud-download Log API) end subgraph "Azure Cloud / Subscriptions" roAzureAPI(fal:fa-cloud Microsoft Azure API)---roLA(fal:fa-clouds Your Logic Apps) roNI --> |443| roAzureAPI roNI --> |80,443| roLogAPI end

1. Between the Monitoring Service and the Azure Logic Apps Logging and 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 'Option 1' or 'Option 2' as documented next:

Option 1 (Local network)

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

Option 2 (Cloud/Hybrid)

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:

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic
5671, 5672 Secure AMQP
9350 - 9354 Net.TCP

2. Between the Azure Logic Apps Logging and Monitoring agent and Azure Management API

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic with the Azure REST API. - Safelist the Azure portal URLs on your firewall or proxy server

3. Between the Azure Logic Apps Logging and Monitoring agent and the Log API

When Logging is enabled the Azure Logics Apps Log and Monitoring Agent requires one of the following outbound TCP ports to be open for access the Log Api (configurable)

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP)
443 HTTPS default for HTTPS)

Note: If the Azure Logics Apps Log and Monitoring Agent and the Log API is on the same server you should stick with http for performance and information is not outside the server


Frequently asked questions

Common problems and FAQ for the Azure Logics Apps Log and Monitoring Agent can be found in the troubleshooting page.

Next Step

Install the Azure Logic Apps Logging and Monitoring agent

Add or manage a Monitoring Agent Configuration
Monitoring Agents
Administration
Monitoring Agents