Message Templates ​

A message template is the custom text Pulse puts in the incidents a monitor raises, instead of a generic one. It is written once on the monitor and used every time that monitor opens an incident.

Where to Set One ​

MonitorWhere the message is written
CVE monitorThe incidentMessageTemplate column when importing from CSV
Condition monitorThe What happened field on the condition's Alert node, in the condition editor

A heartbeat is a data source, and the condition it alerts through is a condition monitor like any other — its own edit page has no message-template field, but Open in editor on that page opens the condition editor, where the same Alert node What happened field applies.

A condition can carry several Alert nodes, each with its own incident name and description — so one condition can raise distinctly-worded incidents for different failure modes. See Conditions.

Writing the Message ​

The message is shown exactly as you write it, in the incident and in the notification that raises it. It supports Markdown for emphasis, lists, and links — see the Markdown Reference.

Writing effective messages

  • Keep the message concise but informative.
  • Name the equipment the incident is about, so a responder knows where to go without opening Pulse.
  • Add context about what condition was violated and what to check first.
  • Use clear, non-technical language for operators. :::