How to enable Service Bus Relaying connections for Nodinite Log and Monitoring Agents

Easily connect and manage Nodinite Monitoring Agents anywhere—on-premise, in the cloud, or hybrid environments—using Microsoft Azure Service Bus Relaying. This guide empowers you to:

✅ Securely connect distributed Monitoring Agents across any network
✅ Optimize costs and performance with built-in caching and configuration tips
✅ Follow step-by-step setup for Service Bus Relaying and firewall rules
✅ Troubleshoot connectivity and security issues quickly

What is Service Bus Relaying?
The Service Bus relay service from Microsoft enables the Nodinite Monitoring Service to communicate with Nodinite Monitoring Agents. These agents can run in Azure datacenters, your on-premises enterprise, or even remote customer and partner sites.

Service Bus Relaying enables secure, scalable communication between distributed Monitoring Agents and the central Monitoring Service.

In essence, you can install and host Nodinite Monitoring Agents anywhere and everywhere! Simply install and configure the agent for Service Bus Relaying to unlock seamless integration.

Costs and pricing information

Running Nodinite Monitoring Agents with Service Bus Relaying incurs costs based on:

• Number of installed agents using Service Bus Relaying
• Synchronization interval set in Monitoring Agent Configuration
• State changes in exposed Resources—error-prone environments may cost more
  • For custom-coded Monitoring Agents, ensure LogText only changes when necessary
• Caching—All Nodinite Monitoring Agents support ETAG caching to reduce costs and boost performance
• Number of Remote Actions executed

Note

Using Service Bus Relay requires an Azure account with a valid credit card and will incur costs.

Example: Azure Service Bus Relaying pricing overview For the latest pricing, see here.

How to configure the Monitoring Agents to use Service Bus Relaying

This section covers the general steps for configuring any [Monitoring Agent][] to use Service Bus Relaying.

✅ Prerequisites

• Local Configuration
• Monitoring Agent Configuration

Prerequisites

• Firewall
• Azure Subscription with a valid credit card
  • Account must have at least Contributor role
• Namespace—endpoint address must be unique; for multiple agents, use separate Namespaces or adjust the endpoint address and Service URI accordingly
• Shared Access Signature security Key—see MDSN for details

Local Configuration

Each Monitoring Agent has a local configuration file (.config) with a commented Service Bus Relaying section. Remove the comments and enter your Service Bus Namespace details.

Important

This manual step requires RDP access and local admin rights. Restart the Monitoring Agent after editing. The README.txt will display the URI for use in Monitoring Agent Configuration.

1. behaviorExtensions
2. endpointBehaviors
3. webHttpRelayBinding
4. endpoint

Example: Monitoring Agent configuration file for Service Bus Relaying

1. behaviorExtensions

Uncomment the behaviorExtensions section.

Uncommenting behaviorExtensions in the config file

2. endpointBehaviors

Uncomment this section and update keyName and key as per your Azure portal setup.

3. webHttpRelayBinding

Uncomment this section.

4. endpoint

Uncomment this section and update ServiceBusNameSpace as per your Azure portal setup.

Create/select the Service Bus relay namespace in Azure

Monitoring Agent Configuration

In Monitoring Agent Configuration, update:

• Service URL
• Enable Authentication and set the Authentication Key

Settings tab

Enter the Service URL for the installed Monitor Agent (from Readme.txt or the <endpoint address ... in %Monitoring Agent%.exe.config).

Service URL in Monitoring Agent Configuration

Security tab

A Service Bus Relay connection string format:

SharedAccessKeyName=%SharedAccessKeyName%;SharedAccessKey=%SharedAccessKey%;AuthenticationKey=%AuthenticationKey%

Security tab for Service Bus Relay connection

Update these fields:

1. SharedAccessKeyName—copy from Azure Portal (default: RootManageSharedAccessKey)
   
   SharedAccessKeyName in Azure Portal
2. SharedAccessKey—copy from primary or secondary key
   
   SharedAccessKey in Azure Portal
3. AuthenticationKey—provided by the Nodinite Monitoring Agent (from local Readme.txt)

Firewall

Open these outbound ports to '*.servicebus.windows.net' from both on-premise and off-site locations:

• What is an on-premises data gateway?

Troubleshooting

To debug connectivity, enable WCF diagnostics logging. See Microsoft docs.

Add the following <system.diagnostics> section to the local config file (.config):

Important

The Windows Service Account running the Agent must have write access to the log folder (e.g., C:\Temp\WCFlog). Ensure the folder exists!

...
<configuration>
  <system.diagnostics>
    <sources>
      <Monitoring Agent Configuration name="System.ServiceModel"
              switchValue="Information, ActivityTracing"
              propagateActivity="true" >
        <listeners>
             <add name="xml"/>
        </listeners>
      </Monitoring Agent Configuration>
      <Monitoring Agent Configuration name="System.ServiceModel.MessageLogging">
        <listeners>
            <add name="xml"/>
        </listeners>
      </Monitoring Agent Configuration>
      <Monitoring Agent Configuration name="myUserTraceSource"
              switchValue="Information, ActivityTracing">
        <listeners>
            <add name="xml"/>
        </listeners>
      </Monitoring Agent Configuration>
    </sources>
    <sharedListeners>
        <add name="xml"
             type="System.Diagnostics.XmlWriterTraceListener"
             initializeData="C:\Temp\WCFlog\Error.svclog" />
    </sharedListeners>
  </system.diagnostics>
</configuration>
...

Contact our Support for additional guidance if you cannot resolve the problem.

Tip

Additional troubleshooting information may be available in the Windows Event Logs.

Next Step

Add or manage Monitoring Agent

Related Topics

Monitoring Agents
Monitoring Service
Microsoft Service Bus Relaying
Service Bus Relaying Pricing