Categories
Organize your monitoring landscape by resource type with Nodinite Categories. Group related Resources—like BizTalk Send Ports, Azure Service Bus Queues, or Windows Services—for simplified management, targeted alerting, and role-based access control.
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 - Apply settings to all Resources in a Category at once
- ✅ Role-based access - Grant teams access to specific Categories without exposing everything
- ✅ Custom documentation - Link external resources for Category-specific guidance
How Categories Organize Resources
All BizTalk Send Ports] MV2[fal:fa-display Monitor View:
Azure Queues Only] CAT1 --> | Includes | MV1 CAT3 --> | Includes | MV2 end style CAT1 fill:#e1f5ff style CAT2 fill:#e1f5ff style CAT3 fill:#fff4e1 style CAT4 fill:#e8f5e9 style MV1 fill:#f3e5f5 style MV2 fill:#f3e5f5
Diagram: Categories enable technology-based organization—monitor all resources of a specific type across your entire landscape
A Category is used to group related Resources from Monitoring Agents in Monitor Views.
Origin of Category Names
Category names are automatically populated from Resources during the sync operation of the Monitoring Service. The Resources come from the Monitoring Agents. Category names are read-only — they reflect the resource type as classified by the Monitoring Agent and cannot be renamed manually.
| Agent type | Example Category names |
|---|---|
| BizTalk Agent | Send Ports, Receive Locations, Orchestrations, Hosts |
| Azure Logic Apps Agent | Logic App |
| Azure Service Bus Agent | Service Bus Queue, Service Bus Topic |
| Windows Agent | Windows Services, Scheduled Tasks |
| SQL Agent | SQL Jobs, SQL Databases |
| Generic / custom | Any string returned by the Monitoring Agent |
Some Monitoring Agents support custom Category names configured per agent — check the individual agent documentation for details.
Every Resource is assigned exactly one Category. There is no hierarchy or nesting within Categories — they are flat labels that classify the technical type of a Resource.
Category as the Mapify Leaf Label
In Mapify, the Category is displayed as the resource type label on each leaf node of the navigation tree. When navigating the Application path hierarchy, the Category tells you what kind of resource you are looking at:
Production Subscription (Application Segment – level 0)
└── Integration RG (Application Segment – level 1)
└── OrderProcessor ← Resource Name
Category: Logic App ← shown as type label
This makes it easy to distinguish a Logic App from a Service Bus Queue or a Windows Service at a glance, even deep in a large integration landscape.
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 | Auto-populated from the Monitoring Agent | Auto-populated from the Monitoring Agent |
| Supports custom naming | Some agents, yes | No |
| Used for | Filtering by type, Monitor Views, Expected State rules | End-to-end system monitoring, Mapify tree grouping |
| Mapify role | Leaf node type label | Tree node hierarchy |
A single Resource always has exactly one Category and at most one Application. Together they give you two independent axes for navigating and filtering your integration landscape.
Expected State Rules by Category
One of the most powerful uses of Categories is applying Expected State overrides to an entire type of Resource at once. For example:
- Set all
Receive Locationsin a BizTalk Application to Expected: Stopped during a maintenance window - Mark all
SQL Jobsof a certain type as Expected: Disabled when a migration is in progress
This avoids having to configure each Resource individually and reduces alert noise during planned changes.
You can add a link to provide additional external documentation by adding a Link to further reading about the Category.
Example of the Website link field for Category external documentation.
Next Step
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