- 3 minutes to read

Show who to call in alerts

An alert that only says "a resource changed state to Error" sends people hunting for the owner at 3 AM. When your integrations carry an Owner, an Emergency Contact, and a Runbook link in Nodinite, the alert can show them, and whoever reads it knows who to call and what to do.

  • ✅ Put the owner and emergency contact in front of the person who gets the alert
  • ✅ Hand responders the runbook link and SLA level straight away
  • ✅ Keep the contact details current in one place

When you need this

Your team gets alerts about the order integration, but the person on call always has to ask around for who owns it and where the recovery steps are. You want the answer in the alert itself.

What you need

  • Custom Metadata fields for the contact details, for example Owner, Emergency Contact, SLA Level, and Runbook URL (a Link field), scoped to Integrations or Resources. See Add or manage Custom Metadata.
  • Permission to edit the Integration or Resource in your Role.
  • An alert that shows Custom Metadata. Your administrator sets this up once: an Alarm Plugin such as Email with Options on the Monitor View, with an email layout (Stylesheet) that displays these fields, or an HTTP Webhook that passes them on to your ticketing or chat tool. Ask your administrator which fields the layout shows.

Do it

  1. In the Repository menu, open Integrations and click the Integration you get alerts about. For a monitored component, open the Resource instead.
  2. Click Edit and scroll down to the Custom Metadata fields.
  3. Fill in Owner, Emergency Contact, SLA Level, and Runbook URL.
    Custom Metadata fields on the Edit tab of a repository entity
    Custom Metadata values on the Edit tab, where you keep owner and contact details up to date.
  4. Click Save.

When the owner or on-call number changes, update it here. The next alert uses the new value; there is no separate alert list to maintain.

What you'll see

The next alert for that Integration or Resource includes the values, laid out the way your administrator's email layout or webhook presents them, for example:

Integration: Order-to-Cash
Owner: Henrik
Emergency Contact: Michael, +1-555-0199
SLA Level: Gold
Runbook: https://docs.company.com/runbooks/order-to-cash

If it doesn't work

  • The alert doesn't show your values: the email layout or webhook decides which fields are shown. Ask your administrator to add them; the details are in Alert Enrichment.
  • The alert goes to the wrong people: who receives an alert is set on the Monitor View's Alarm Plugins, not on the Integration. Ask your administrator.
  • Never put passwords, API keys, or connection strings in Custom Metadata: anything in these fields can travel in alerts. Use a neutral reference instead, see the sensitive data safety rule.
  • Still stuck? See Support.

Next Steps