Categories
Organize your monitoring landscape by resource type with Nodinite Categories. A Category groups related Resources, like BizTalk Send Ports, Azure Service Bus queues, or Windows Services, for simplified management, targeted alerting, and role-based access control.

A Category is a resource type that one Monitoring Agent reports; use it to find and filter every Resource of that type.
Why Use Categories
- ✅ Logical organization - Group Resources by technology type (queues, services, APIs, databases)
- ✅ Targeted monitoring - Create Monitor Views for specific resource types
- ✅ Simplified management - Find and filter every Resource of one type at once in the Resources Overview
- ✅ Role-based access - Give teams a Monitor View filtered on their Categories and assign it to their Roles without exposing everything
- ✅ Custom documentation - Link external resources for Category-specific guidance
How Categories Organize Resources
All BizTalk Send Ports] MV2[fa:fa-display Monitor View:
Azure Queues Only] CAT1 -->|"Includes"| MV1 CAT3 -->|"Includes"| MV2 end style MA1 fill:#3F827B,color:#fff style MA2 fill:#3F827B,color:#fff style MA3 fill:#3F827B,color:#fff style CAT1 fill:#2678BD,color:#fff style CAT2 fill:#2678BD,color:#fff style CAT3 fill:#2678BD,color:#fff style CAT4 fill:#2678BD,color:#fff style MV1 fill:#9E59BB,color:#fff style MV2 fill:#9E59BB,color:#fff
Green Monitoring Agents report Resources, each Resource belongs to a blue Category, and purple Monitor Views include whole Categories, so you can monitor all Resources of one type across your entire landscape.
A Category is used to group related Resources from Monitoring Agents in Monitor Views. On a Monitor View's Resources tab you can include or exclude all Resources of one or more Categories; see Add or manage Monitor View.
Origin of Category Names
Categories come only from the Monitoring Agents. You can't add a Category by hand: the Categories Overview has no Add button, and the Web API can list, get, edit (the Link), delete, and restore Categories, but not create them. Name and Description are read-only; only the Link can be changed.
On every sync of a Monitoring Agent (its polling interval, at least 30 seconds), the Monitoring Service does this:
- Takes what the agent reports. The agent sends a list of Categories, each with a Name and Description, and its Resources, each pointing at one of those Categories. The Name and Description you see are the agent's; Nodinite gives every Category its own id.
- Matches by name, per Monitoring Agent. The match ignores upper and lower case. Two agents can each report
Receive Location, which gives two rows in the list. A change in case or in the Description updates the existing Category. - Marks a Category deleted when the agent stops reporting it. The row and its Link are kept, and nothing is removed for good. When the agent reports it again, it's restored automatically with the same Link.
- Undoes a manual Delete while the agent still reports the Category: the next sync restores it. Delete only matters for a Category the agent no longer reports, and step 3 already handles those.
- Repairs agent errors, and writes a Log Audit warning for each:
- a Category without a name becomes Missing Category Name;
- a duplicate name from the same agent becomes <name> Duplicate;
- a Resource that points at a Category the agent didn't report gets Missing Category.
| Agent | Example Category names |
|---|---|
| BizTalk Server Monitoring Agent | Receive Location, Send Port, Send Port Group, Orchestration, Host Instance, Pipeline, Application, Health Check, Tracking, Suspended instance(s) (resumable) |
| Windows Server Monitoring Agent | Windows Service, Windows Scheduled Task, Disk, CPU, IIS - Application Pool, X509 Certificate - Local Machine |
| Azure Logic Apps Monitoring Agent | Logic App |
| Message Queueing Monitoring Agent | Service Bus Queue |
| Database Monitoring Agent | SQL Jobs, SQL Size Checks, SQL Instance (from that agent's documentation) |
| Any other agent | Whatever string the Monitoring Agent reports |
A Resource has at most one Category. An agent may report a Resource without one. There is no hierarchy or nesting within Categories: they are flat labels that classify the technical type of a Resource.
Categories in Mapify
In Mapify, a Category is a node of its own, of type Category. It is linked to its Resources, its Monitoring Agent, the Monitor Views that include it, and the Articles that link to it. Mapify is a relation graph: it doesn't show Categories as labels in a tree.
Open a Category there from the Categories Overview: the row's Action menu has Show in Mapify (with a Mapify product key) and Show in Mermaid. The Category page itself has no Mapify button.
Categories vs Applications
Both Categories and Applications group Resources, but they answer different questions:
| Category | Application | |
|---|---|---|
| Groups by | Technical resource type | Business system or platform hierarchy |
| Example | Logic App |
Production Subscription / Integration RG |
| Set by | The Monitoring Agent | The Monitoring Agent |
| Used for | Filtering by type in Monitor Views and the Resources Overview | End-to-end system monitoring |
| Mapify role | A node linked to its Resources, Monitoring Agent and Monitor Views | A node linked to its Resources, Monitoring Agent and Monitor Views |
A single Resource has at most one Category and at most one Application. Together they give you two independent axes for navigating and filtering your integration landscape.
Categories and Expected State
Expected State is configured per Resource, not per Category. Categories help you find the Resources to configure: filter the Resources Overview on a Category, for example Receive Location or Windows Service, to list every Resource of that type, then set the Expected State on each one that is intentionally stopped or disabled. For a planned window that covers whole Monitor Views, use Maintenance Mode instead.
Link to Category Documentation
You can add a link to provide additional external documentation by adding a Link to further reading about the Category. Monitor Views then show an external link icon after the Category name, and a Resource's history details make the Category name itself the link.

The Link is the only editable property of a Category.
Next Steps
Add or manage Categories
Add or manage Resource
Add or manage Monitoring Agent
Add or manage Monitor View
Related Topics
Categories Overview
Monitor Views
Monitoring Agents
Resources
Applications
Resources Overview
Mapify
Permission Set for Monitor Views
Working with a Monitor View