What is a Monitoring Agent?

Monitor your entire system integration chain, end to end, everywhere on any device using Nodinite

Resources Monitoring Monitoring Agent Configuration Monitoring Service Log Databases Web API Web Client Monitor View Roles User

Nodinite uses the concept of Monitoring Agents to monitor Resources on-premise, hybrid and in the cloud. These Resources can be of any type of service, endpoint or function in the system integration chain. The design goal here is to be able to monitor end to end and provide metrics , alerts and remote actions with relevant and up to date information to stakeholders. To further help organizations create personal independence, the documentation from the Repository Model including the use of Articles is tightly integrated and readily available.

Any number of Monitoring Agents can be installed on any number of hosts. In order to separate these from each other Nodinite keeps track of each of them by using a Monitoring Agent Configuration. Each entry point to exactly 1 Monitoring.

The Monitoring Service is responsible for the communication with the Monitoring Agent Configuration (Monitoring) using the provided connection details set on a Monitoring Agent Configuration.
Monitoring Agents **provides run-time information about Resources. Nodinite keeps track of changes and this data can be used for further analysis.

MonitorAgents
The list of supported agents grows over time. Special focus is currently put on developing support for ever evolving and maturing Azure technologies.

The Monitoring Agents are governed by the Monitoring Service through the concept of Monitoring Agents. A Monitoring Agent Configuration configuration holds the connectivity (whereabouts) information for a specific instance of the Monitoring Agent.

Information about installed Monitoring Agents, can be further explored from the Overview from within the Administration in the Web Client.

Any Technology, Any Device

A Monitoring Agent can be installed on-premise or in the cloud. The implemented design pattern is generic and provides a foundation for us, our customers and partners to extend and build their own Monitoring Agents. We provide Templates and SDK's for further custom development, please contact our support at support@nodinite.com if your are interested in exploring this topic further.

The Monitoring Agents we provide are usually Windows based (.NET) Service.

  • .NET Framework 4.0 or later running on-premise or in the cloud (.NET 4.6 or later is recommended for a full feature set)
    • Windows Server 2008-2016
  • Node.js based running on just about any device
    • Windows Server 2008-2016
    • Linux
    • Apple
    • IOT devices

AnyDevice

Installing and running

The Monitoring Agents must be installed and configured and eventually maintained over time. Whenever there's a new version available a Release note is created and you can get an email alert by logging on to the support page and opt to subscribe. The release note for each Monitoring Agent can be found with each topic on the support page.

Documentation wise the agents generally share the following structure:

  1. Prerequisites
  2. Install
  3. Configure
  4. Update
  5. Uninstall

In general terms further outlined in this document is:

  • Connectivity
  • Service account requirements
  • Diagnostics
  • Culture settings
  • Installation of multiple instances on same server

Connectivity

The Monitoring Agents must be able to communicate between installed agent and the Monitoring Service.

The Monitoring Agents are designed to conserve bandwidth and uses etag caching for great performance and less costs (money wise).

All Windows based agents supports the use of either:

  • TCP/IP (default) local or VPN access
  • Service Bus Relaying - use when Agents are installed in other networks where VPN or WAN links are not available.

TCP/IP

For local and VPN access. Is required with an authentication key to enable the Remote Configuration. See documentation for the usage of Port 8000.

Service Bus Relaying

Service Bus Relaying - run anywhere. This connectivity type is secure by default.

Service account requirements

The account running the Windows Service (Monitoring Agent instance) requires a Windows account and depending on technology additional access rights to cloud- and/or line of business systems (for example SQL, Azure subscriptions, MSMQ, NFS, FTP...).

  • Logon rights

    • On Windows, the account running the Monitoring Agent Service requires special rights, see Logon As A Service for more information.
  • Access rights

    • Depending on specific agent, see prerequisites within the documentation for each Monitoring Agent

Diagnostics

From the Monitoring Agents administration the diagnostic files can be easily downloaded without having to remote logon to servers using for example RDP.

DownloadDiagnostics

This zip file is typically sent to our support whenever there is a question or an incident.

Use the Remote Configuration modal to toggle the debug flag to increase verbosity level when logging (default unchecked).
debug flag

Culture settings

Many of the Monitoring Agents provides customization for formatting time related data.

Use the Remote Configuration modal to change the Culture Information.
CultureInformation

Installation of multiple instances on same server

This is an advanced topic and only applies of you install multiple instances of the same type of Monitoring Agent on the same server.

Any number of the same type of Monitoring Agent may be installed on the same Windows Server as long as the name from the EndPoint Section in the %MonitorAgent%.exe.config is unique. Name (preferred change) or Port must be changed.

Note: If you install multiple instances you cannot use the installer when updating other than the first installed service. Manual copy/past operations must then be performed from the first to the latter installations.

  1. Install the first Monitoring Agent according to documentation

    1. Remember while installing to add environment name to the installation folder, for example PROD
  2. Copy the folder and Rename to for example TEST

  3. Edit the %.exe.config file using notepad or notepad++ from with elevated privileges (start from administrative cmd prompt)

  4. Find the EndPoint xml element <endpoint

MultipleInstancesEndPoint

  1. Open Services.msc

    1. Copy the Service Name from the first Monitoring Agent to Notepad
    2. Rename the Environment part (for example PROD -> TEST) making this endpoint address unique
    3. Copy to clipboard/notepad instance for use in the next step
  2. Open an Administrative Command Prompt and use the following command as template to install the new Monitoring Agent (replace paths and environment)

sc create "%UNIQUE OTHER NAME OF Monitoring Agent FROM CLIPBOARD%" binpath="C:\Program Files (x86)\Integration Software\IM Monitoring Agent - Windows Server TEST\IM.MonitorAgent.WindowsServerHost.exe"
  1. Change The startup type in the Services MMC to Automatic (Delayed)

  2. Enter credentials

  3. Start the service

  4. The README.txt file in the run-time folder will now have the proper address for use as a Monitoring Agent Configuration

Note: Remember to copy (backup) the config file before updating the agent.


Next Step

Add or manage Monitoring Agent
Remote Configuration
Articles

Resources Monitoring Monitoring Agent Configuration Monitoring Service Log Databases Web API Web Client Monitor View Roles User