Custom Metadata in Alerts: Looking Good When It Matters
The Power of Qualified Information
When integrations fail at 3 AM, qualified information in your alerts isn't a luxury; it's a business necessity. Nodinite Alarm Plugins carry Custom Metadata from your Repository Model into your alerts: the Custom Metadata of each changed Resource, and of each Integration assigned to the Monitor View. The default templates of the Email Alarm Plugins already show all of it (except Markdown and Mermaid Diagram values), and the HTTP Webhook payload includes it. The first person who reads the alert knows who to call and what to do.
- ✅ Owner and Emergency Contact in the alert
- ✅ SLA level and business impact to prioritize correctly
- ✅ Runbook and architecture links for immediate action
- ✅ Full metadata in the HTTP Webhook JSON payload for Jira, ServiceNow, and Slack automation

Animated walkthrough: the Resource Print Spooler has Responsible Team set to Warehouse IT. When it stops, the Monitor View Contoso: Label printing sends its alert through an Email with Options Alarm Plugin. The default template lists the Resource's Custom Metadata under its row, and the assigned Integration INT002: Invoices with its Owner and SLA under Affected Integrations.
The Cost of Unqualified Alerts
- 45 minutes hunting for "Who owns this?"
- Emergency calls to the wrong team
- SLA violations while searching for runbooks
- Customer-facing incidents where you look unprepared
- Reputation damage: "They don't even know their own systems"
The Value of Metadata-Enriched Alerts
- 2 minutes to engagement (Owner + Emergency Contact in alert)
- Escalation starts with the right person (Owner and Emergency Contact are in the alert)
- Runbook link in the alert → immediate action
- SLA context → prioritize correctly
- LOOKING GOOD: Professional, prepared, in control
See how it works: Email alerts with XSLT transformation | HTTP Webhook alerts with JSON payload | Before vs After comparison | Configuration guide
Sensitive Data Safety Rule
Alert enrichment is powerful, but it also increases data exposure risk if teams store secrets in user-editable text fields.
Warning
Anything placed in descriptions or Custom Metadata can be propagated into alerts. Never put passwords, API keys, tokens, private keys, or full connection strings in these fields.
Fields to Treat as Non-Secret
- Description fields on Resources, Categories, and Applications
- Custom Metadata values used for Owner, SLA, escalation, and runbook context
- Content transformed by XSLT and sent through Email Alarm Plugins
- Content serialized in HTTP Webhook JSON payloads
Safe Pattern
- Keep only operational context in alerts: owner, SLA, runbook URL, business impact
- Store credentials in secret managers or vault solutions, not in Nodinite text fields
- Use neutral references in metadata, for example
SecretRef=SqlProdConnection - Review every alert template and webhook consumer for accidental secret leakage
Alert Enrichment Architecture
assigned to the Monitor View
Owner: Henrik
SLA: Gold"] roResource["fa:fa-server Resource
Responsible Team: Warehouse IT
Runbook Link"] roMonitoring["fa:fa-bell Monitoring Service
State Change Detected"] roAlarmPlugin["fa:fa-bolt Alarm Plugin
Email / HTTP Webhook"] roEmail["fa:fa-envelope Email Alert
XSLT Transforms XML
Owner + SLA + Contact"] roWebhook["fa:fa-webhook HTTP Webhook
JSON Payload
Custom Metadata Included"] roTeam["fa:fa-users Operations Team
Qualified Alert Received
2-Minute Engagement"] roJira["fa:fa-ticket Jira/ServiceNow
Auto-Create Ticket
Metadata Pre-Filled"] roResource -.->|"State Change
Error/Warning"| roMonitoring roIntegration -->|"Its own values"| roAlarmPlugin roMonitoring ==>|"Trigger Alert
with the Resource's values"| roAlarmPlugin roAlarmPlugin ==>|"XSLT Transform"| roEmail roAlarmPlugin ==>|"JSON Payload"| roWebhook roEmail ==>|"Enriched Alert"| roTeam roWebhook ==>|"Enriched Alert"| roJira style roIntegration fill:#93d16d,stroke:#3F827B,stroke-width:3px style roResource fill:#FFD525,stroke:#E47528,stroke-width:3px style roMonitoring fill:#2678BD,stroke:#2678BD,stroke-width:2px,color:#fff style roAlarmPlugin fill:#2678BD,stroke:#2678BD,stroke-width:3px,color:#fff style roEmail fill:#9E59BB,stroke:#9E59BB,stroke-width:2px,color:#fff style roWebhook fill:#9E59BB,stroke:#9E59BB,stroke-width:2px,color:#fff style roTeam fill:#93d16d,stroke:#3F827B,stroke-width:3px style roJira fill:#93d16d,stroke:#3F827B,stroke-width:3px
The changed Resource (yellow) brings its own Custom Metadata, and each Integration assigned to the Monitor View (green) brings its own. The Monitoring Service (blue) hands both to the Alarm Plugins, which turn them into enriched alerts (purple) for operations teams and external systems (green). Dashed lines show state changes, double lines show alert delivery. Systems, Services and Endpoints aren't in the alert, and nothing is inherited along relations.
How Custom Metadata Enriches Alerts
Email Alerts (XSLT Transformation)
The Email Alarm Plugins (Email and Email with Options) receive an XML structure containing:
- Monitor Views with their changed Resources, each with its own Custom Metadata
- The Integrations assigned to each Monitor View, each with its own Custom Metadata
- Resource health status and timestamps
Only these two kinds of items carry Custom Metadata into the alert. Systems, Services, Endpoints and other related items aren't in it, and nothing is inherited along relations: to name an owner in the alert, put the field on the Resource, or assign the Integration to the Monitor View.
The default templates of both plugins already show it: under each Resource row comes a Custom Meta Data / Value(s) table, and under Affected Integrations each Integration gets the same table. They skip Markdown and Mermaid Diagram values. You need a custom stylesheet only to change the layout. Stylesheets (XSLT) can turn this XML into formatted HTML emails with:
- Owner and Emergency Contact - "Call Henrik at +1-555-0123, escalate to Michael if no response in 15 minutes"
- SLA Level - "[GOLD SLA] 4-hour response required"
- Business Context - "Department: Finance, Process: Month-End Invoice Processing"
- Compliance Tags - "GDPR + PCI DSS data flows affected"
- Runbook Link - "Emergency Procedure: [View PDF]"
- Architecture Diagram - "System Architecture: [View Diagram]"
Learn how to customize XSLT | Configure the Email with Options plugin
Example Alert
SUBJECT: [GOLD SLA] Finance Integration Failed: Order-to-Cash
Integration: Order-to-Cash Payment Processing
Owner: Henrik (henrik@company.com, +1-555-0123)
Emergency Contact: Michael (michael@company.com, +1-555-0199)
Department: Finance
SLA: Gold (4-hour response, 99.9% uptime required)
Business Impact: $50M annual revenue stream affected
Compliance: GDPR + PCI DSS data flows
Runbook: [Emergency Recovery Procedure]
Architecture: [System Diagram]
ACTION REQUIRED:
1. Call Henrik immediately (+1-555-0123)
2. If no response in 15 minutes, escalate to Michael
3. Follow runbook for database failover
4. Notify Finance VP if downtime exceeds 30 minutes
Details:
Failed at: 2025-02-03 03:42:15 EST
Error: Database connection timeout (SQL Server)
Affected Systems: Payment Gateway, Order Management
Pending Transactions: 127 orders ($342,500 value)
The Same Alert Without Metadata
SUBJECT: Monitor View State Changed
A resource in Monitor View "Payment Processing" changed state to Error.
Details: Database connection timeout
[End of email]
Result: With metadata, your team looks professional, prepared, and in control. Without metadata, you look disorganized.
Configure Email alerts | Compare Email vs Email with Options | Explore XSLT customization
HTTP Webhook Alerts (JSON Payload)
The HTTP Webhook Alarm Plugin sends JSON payloads to external systems:
- Jira, ServiceNow, Freshdesk (incident management)
- Slack, Teams, PagerDuty (team notifications)
- Power Automate and other workflow tools (workflow automation)
- Custom integrations (data warehouses, dashboards, SMS providers)
Custom Metadata in the JSON Payload
The webhook JSON is the whole alarm object with PascalCase names, without the Users list. Custom Metadata sits in two places:
| Item | XSLT input (Email, Email with Options) | JSON (HTTP Webhook) |
|---|---|---|
| Changed Resource | /AlarmObject/MonitorViews/MonitorView/ChangedResources/Resource/CustomMetaDatas/CustomMetaData |
MonitorViews[].ChangedResources[].CustomMetaDatas[] |
| Integration of the Monitor View | /AlarmObject/MonitorViews/MonitorView/Integrations/Integration/CustomMetaDatas/CustomMetaData |
MonitorViews[].Integrations[].CustomMetaDatas[] |
Each CustomMetaData holds CustomMetaDataId, Name, Description, WebSite, DataType, and CustomValues: a list of CustomValue elements in the XML, an array in the JSON. Each value has CustomValueId, Value, Description and WebSite. A Select or Check Box gives one value per picked value. DataType is the type's name in the XML (TextField, Select, CheckBox, ...), so a template can test DataType = 'Markdown', and its number in the JSON (0 Text Field, 3 Select, 5 Check Box, ...).
A shortened example; the real payload has more properties:
{
"MonitorViews": [
{
"Name": "Contoso: Label printing",
"ChangedResources": [
{
"Name": "Print Spooler <Spooler>",
"StatusCode": { "StatusCode": 1, "Name": "Warning" },
"CustomMetaDatas": [
{ "Name": "Responsible Team", "DataType": 3, "CustomValues": [ { "Value": "Warehouse IT" } ] }
]
}
],
"Integrations": [
{
"Name": "INT002: Invoices",
"CustomMetaDatas": [
{ "Name": "Owner", "DataType": 3, "CustomValues": [ { "Value": "Henrik Berg" } ] }
]
}
]
}
],
"IsRecurring": false
}
The HTTP Webhook page describes the rest of the payload.
What You Can Do with This Data
The receiving system does this work, in your webhook consumer's own logic. Nodinite sends the alert to the Alarm Plugins set on the Monitor View; it doesn't read Custom Metadata to decide where an alert goes. Your consumer can:
- Auto-create a Jira ticket with Owner, SLA, Emergency Contact pre-filled
- Route to the correct Slack channel based on Department metadata
- Calculate SLA breach time using SLA Level metadata
- Include the runbook link in the ServiceNow incident
- Tag the compliance team if GDPR/HIPAA data is affected
- Send an SMS to the Emergency Contact for critical failures
Configure the HTTP Webhook plugin | Learn about webhook authentication
Example Jira Ticket Created by a Webhook Consumer
Your consumer maps the payload's Custom Metadata to Jira fields, for example Owner to Assignee:
Summary: [GOLD SLA] Finance Integration Down: Order-to-Cash Payment Processing
Priority: Critical (Gold SLA = 4-hour response)
Assignee: Henrik (from Owner metadata)
Labels: Finance, GDPR, PCI-DSS, Payment-Processing
Description:
Integration: Order-to-Cash
Owner: Henrik (henrik@company.com, +1-555-0123)
Emergency Contact: Michael (+1-555-0199)
SLA: Gold (4-hour response required)
Business Impact: $50M annual revenue stream
Error: Database connection timeout
Affected Systems: Payment Gateway Database
Emergency Procedure: [Runbook Link]
Architecture: [Diagram Link]
Escalation: If not resolved in 4 hours, breach Gold SLA.
If no response from Henrik in 15 min, call Michael.
Technical Integration: How Metadata Flows to Alerts
XSLT: Customize Email Alert Presentation
Email Alarm Plugins use XSLT to transform XML alarm data into HTML emails. Learn about Stylesheets, or read the full Alarm Plugin Object reference.
Example XSLT Snippet to Display Custom Metadata
The default templates already list all Custom Metadata; write your own only to change the layout. The paths are in the table under Custom Metadata in the JSON Payload, and the Alarm Plugin Object page shows the whole XML structure.
<!-- The changed Resources, each with its own Custom Metadata -->
<xsl:for-each select="/AlarmObject/MonitorViews/MonitorView/ChangedResources/Resource">
<h2><xsl:value-of select="Name"/></h2>
<p>Responsible Team:
<xsl:value-of select="CustomMetaDatas/CustomMetaData[Name='Responsible Team']/CustomValues/CustomValue/Value"/>
</p>
</xsl:for-each>
<!-- The Integrations assigned to the Monitor View, each with its own Custom Metadata -->
<xsl:for-each select="/AlarmObject/MonitorViews/MonitorView/Integrations/Integration">
<h3><xsl:value-of select="Name"/></h3>
<table>
<tr>
<td>Owner:</td>
<td><xsl:value-of select="CustomMetaDatas/CustomMetaData[Name='Owner']/CustomValues/CustomValue/Value"/></td>
</tr>
<tr>
<td>SLA Level:</td>
<td><xsl:value-of select="CustomMetaDatas/CustomMetaData[Name='SLA Level']/CustomValues/CustomValue/Value"/></td>
</tr>
<tr>
<td>Compliance:</td>
<td>
<!-- A Check Box gives one CustomValue per ticked value -->
<xsl:for-each select="CustomMetaDatas/CustomMetaData[Name='Compliance Tags']/CustomValues/CustomValue">
<xsl:value-of select="Value"/><xsl:if test="position() != last()">, </xsl:if>
</xsl:for-each>
</td>
</tr>
</table>
<p>
<strong>Emergency Procedure:</strong>
<a href="{CustomMetaDatas/CustomMetaData[Name='Runbook URL']/CustomValues/CustomValue/Value}">View Runbook</a>
</p>
</xsl:for-each>
Result: A professional, branded HTML email with all business context visible at a glance.
Real-World Impact: Before vs After
Before Custom Metadata in Alerts
Alert Received Before
SUBJECT: Monitor View State Changed
A resource changed state to Error.
Resource: PaymentDB
Monitor View: Production Servers
What Happens Next Before
- 3:00 AM: Alert received → "Who owns this?"
- 3:05 AM: Search SharePoint for integration documentation
- 3:15 AM: Call general support line → "We don't know, let me check"
- 3:30 AM: Finally reach Henrik's mobile → "I'm on vacation, call Michael"
- 3:45 AM: Michael answers → "What's the runbook?" → Another 10 minutes hunting
- 4:00 AM: Start troubleshooting (1 hour wasted)
Customer perception: "They don't even know who owns their own systems. Unprofessional."
After Custom Metadata in Alerts
Alert Received After
SUBJECT: [GOLD SLA] Finance Integration Failed: Order-to-Cash
Integration: Order-to-Cash Payment Processing
Owner: Henrik (henrik@company.com, +1-555-0123)
Emergency Contact: Michael (michael@company.com, +1-555-0199)
Department: Finance
SLA: Gold (4-hour response, 99.9% uptime)
Runbook: [Emergency Recovery Procedure]
ACTION: Call Henrik. If no response in 15 min, call Michael.
What Happens Next After
- 3:00 AM: Alert received → Call Henrik immediately
- 3:02 AM: Henrik answers → Opens runbook from alert → Starts recovery
- 3:16 AM: Issue resolved (16 minutes total)
Customer perception: "They were on it instantly. Professional, prepared, in control."
Business Impact
- Time to engagement: 45 minutes → 2 minutes (95% faster)
- Time to resolution: 60 minutes → 16 minutes (73% faster)
- SLA compliance: Breach → Met
- Reputation: Damaged → Enhanced
Ready to set up alert enrichment? Follow the configuration guide below to define Custom Metadata fields, assign them to Integrations, and configure Alarm Plugins. The Ownership Clarity scenario shows the full incident timeline.
Configuration Guide
Step 1: Define Custom Metadata Fields
In the Web Client, open Repository → Custom Metadata and follow Add or manage Custom Metadata. Create these fields:
- Owner (Select: Henrik, Sarah, Ahmed, Michael)
- Emergency Contact (Text: Phone number)
- SLA Level (Select: Gold, Silver, Bronze)
- Department (Select: Finance, HR, Operations, IT)
- Compliance Tags (Check Box: GDPR, HIPAA, PCI DSS, SOX)
- Runbook URL (Link: URL to runbook document)
Learn more: Custom Metadata Overview | Entity Coverage | Rich Data Types
Step 2: Assign Metadata to Integrations
Open Add or manage Integration and assign values, for example:
- Integration: "Order-to-Cash"
- Owner: Henrik
- Emergency Contact: +1-555-0123
- SLA Level: Gold
- Department: Finance
- Compliance Tags: GDPR, PCI DSS
- Runbook URL:
https://docs.company.com/runbooks/payment-failover.pdf
Then make sure the values reach the alert: assign the Integration to the Monitor View that alerts (the Integration's Monitor Views card), or put the fields on the monitored Resource itself (Administration → Monitor Management → Resources, the Resource's Custom Metadata panel). An Integration that isn't assigned to the Monitor View isn't in its alerts.
Learn more: Integrations | Systems | Services | Mandatory Fields
Step 3: Configure Alarm Plugins
For Email Alerts
Navigate to Administration → Settings → Alarm Plugins → Email with Options:
- Keep the default template: it already shows the Custom Metadata. Upload your own XSLT stylesheet only for a custom layout
- Configure recipients (operations team, on-call engineers)
- Test the alert → verify Owner, SLA, and Emergency Contact appear in the email
For HTTP Webhook Alerts
Navigate to Administration → Settings → Alarm Plugins → HTTP Webhook:
- Configure the webhook URL (Jira, ServiceNow, Slack, custom endpoint)
- Custom Metadata is included in the JSON payload automatically
- Test the webhook → verify the JSON includes the Custom Metadata
Learn more: Compare all Alarm Plugins | Event Log for SCOM integration
Step 4: Assign Alarm Plugins to Monitor Views
Navigate to Administration → Monitor Management → Add or manage Monitor View:
- Select the Monitor View (e.g., "Payment Systems")
- Assign Alarm Plugins: Email with Options, HTTP Webhook
- Configure alert recurrence (e.g., Error: resend every 15 minutes)
- Test the Monitor View → verify the alerts include Custom Metadata
Learn more: Monitor Views | Resources | Time Intervals for alert recurrence
Next Steps
- Add or manage Custom Metadata – Create Owner, SLA, Emergency Contact fields
- Add or manage Alarm Plugin – Configure Email with Options or HTTP Webhook
- Alarm Plugin Object – Customize XSLT to display Custom Metadata in emails
Related Topics
- Show who to call in alerts – The business-user task for owner and emergency contact in alerts
- Custom Metadata Overview – Hub page for all Custom Metadata features
- Entity Coverage – Where Custom Metadata applies
- Ownership Clarity – Scenario: metadata-driven incident response
- Email with Options – Advanced email alerts with XSLT (recommended)
- HTTP Webhook – JSON webhook for external systems (Jira, ServiceNow, Slack)
- Event Log – Windows Event Log for SCOM integration
- Alarm Plugins Overview – Compare all alarm plugin types
- Alarm Plugin Object – Complete XSLT reference with Custom Metadata examples
- Stylesheets – Transform alarm data into business-friendly formats
- Monitor Views – Group resources for targeted alerting
- Time Intervals – Configure alert recurrence intervals
- Resources – Monitored components and health checks