- 3 minutes to read

Add or Manage Application

Applications are automatically populated and synced from Resources. The Application Name is read-only — it is derived from the source system by the Monitoring Agent and cannot be changed in Nodinite. The only property you configure manually is the Link. Open an Application from the Applications Overview with Action → Edit.

Understanding the Application Page

Field or panel Editable Source and purpose
Name ❌ No Set by the Monitoring Agent; the business system, for example a BizTalk Application or a subscription path
Description ❌ No Set by the Monitoring Agent when the source system provides one
Monitoring Agent ❌ 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, shown as an external link icon in Monitor Views; Test Link opens it in a new tab
Mapify / Mermaid buttons – Show the Application and its relations in Mapify Rendering (requires a Mapify license) or Mermaid Rendering
Delete button – Deletes the Application; restore it later from the Applications Overview (Show Deleted)

Application page with read-only Name and Description, the Monitoring Agent panel, the editable Link field with Test Link, and the Mapify, Mermaid, and Delete buttons (7.10)
Only the Link field is editable; 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 Application Name is set automatically by the Monitoring Service when it syncs Resources from a Monitoring Agent. The value reflects the identity of the system in the source platform:

  • A BizTalk Agent uses the BizTalk Application name (e.g. OrderProcessing)
  • A Windows Agent uses the server display name (e.g. WINSERV01)
  • An Azure Agent uses the subscription and resource group path (e.g. Production Subscription / Integration RG)

For Azure and other hierarchical platforms the name uses / as a path separator. This is intentional — it allows Mapify to build a virtual navigation tree from the path segments, and allows Monitor Views to filter across part of a hierarchy by matching on a shared prefix.

Note

If a Resource has no Application assigned, it will not appear under any Application entry. This is valid — Category alone is sufficient for a Resource. In practice, 99%+ of Resources have an Application.

The Link property is the only field you can set on an Application. Use it to point end-users to external documentation, a dashboard, a runbook, or any relevant web page for the system represented by this Application.

When a Link is configured, the Application name becomes clickable inside Monitor Views and displays an icon to indicate the external reference.

Monitor View Live Monitor tab where the Application column shows an external link icon next to the INT001 Orders Application name (7.10)
An Application with a Link set shows the external link icon next to its name in the Monitor View.

  • 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 (e.g. Azure Monitor, Datadog)

Next Steps