- 3 minutes to read

Add or Manage Application

Applications are created and kept up to date by the Monitoring Service from what each Monitoring Agent reports. The Name and Description are read-only, and there is no way to add an Application by hand: the page has no Add button, and the Web API has no create endpoint. The only property you set is the Link. Open an Application from the Applications Overview with Action › Edit.

Walkthrough: open INT001: Orders, type the Link to its Knowledge base Article, Save and close, then click the external link icon in the Monitor View's Application column to open the Article in a new tab (7.12)
Set the Link once, and everyone who watches a Monitor View with the Application column gets a shortcut to the runbook.

Understanding the Application Page

Field or button Editable Source and purpose
Name ❌ No Set by the Monitoring Agent; the business system, for example a BizTalk Application or an Azure subscription path
Description ❌ No Set by the Monitoring Agent when the source system provides one
Monitoring Agent card ❌ No Links to the Monitoring Agent configuration the Application comes from, with its addresses
Link ✅ Yes Your address for documentation, a dashboard, or a runbook (Can be an address where you can find more information about the Application); Test Link opens it in a new tab
Mapify / Mermaid – Show the Application and its relations in Mapify Rendering (needs the Mapify product key) or Mermaid Rendering
Delete – Marks the Application as deleted; restore it from the Applications Overview (Show Deleted)
Save / Save and close / Cancel – Save the Link and stay, save and return to the list, or leave without saving

Application page for INT001: Orders with read-only Name and Description, the Monitoring Agent card, the Link card with Test Link, the Mapify, Mermaid, and Save buttons, and the Delete, Save, Save and close, and Cancel footer (7.12)
Only the Link is editable; the Name and Description come from the Monitoring Agent.

Sensitive Data Warning

Warning

Never store passwords, API keys, tokens, private keys, or full connection strings in the Link. Monitoring context can appear in alert notifications sent by Alarm Plugins.

Application Name

The Monitoring Service sets the Application Name when it syncs Resources from a Monitoring Agent. The agent decides the name; Nodinite doesn't change it. Examples from a test environment:

  • The BizTalk Server Monitoring Agent uses the BizTalk Application name, for example INT001: Orders, Lab.Orders, or BizTalk.System.
  • The Windows Server Monitoring Agent uses the server name, for example localhost or DC01, or a path such as NODINITE01/Windows Server/DEMO.
  • The Azure Monitoring Agent uses a path with no spaces around /: subscription and resource group, sometimes followed by the resource that groups them, for example <subscription>/default-storage-northeurope/NodiniteFunctionApps.

How names are matched, kept, and restored is on Applications.

Note

A Resource has at most one Application, and an Application is optional. A Resource without one simply doesn't appear under any Application; it still has its Category if the agent reports one.

The Link is the only field you set on an Application. Use it to point users to documentation, a dashboard, a runbook, or an Article about the system the Application represents.

When a Link is set, the Application name in a Monitor View stays plain text, and a separate external link icon appears right after it. Clicking the icon opens the Link in a new tab. The icon shows in every Monitor View that displays the Application column, which the default columns do. In a Resource's history details, the Application name itself is the link.

Monitor View Contoso: Order intake where the Application column shows an external link icon after INT001: Orders on both rows (7.12)
The external link icon after the Application name opens the Link in a new tab.

  • The Knowledge base Article for the integration or business system
  • Azure Portal URL scoped to the relevant resource group
  • Confluence or SharePoint page for the business system
  • Operational runbook for the integration
  • System health dashboard (for example Azure Monitor or Datadog)

Next Steps