AlertMagic - Alert Studio

Alert Studio is where an Integration's alerting configuration is created, edited, tested, and activated. Pick an Integration and a configuration version at the top of the page; everything below operates on that version.

Versions

Configuration is versioned. A Draft version can be edited freely and has no effect on live processing until it is activated - activation is the equivalent of setting it live, and only the activated version is used to process incoming notifications. The toolbar offers:

• Save - saves changes to the current draft version.
• Save (new version) - copies the current version into a new draft, which is the usual way to change a configuration that is already live.
• Activate - makes the selected version live. A version with invalid configuration (highlighted in red in the tree) cannot be activated.
• Import (new version) and Export - move whole configurations as JSON files, useful for backup, review, or copying between environments.

Each version is listed by its number, for example Version 30. A version can also be given a label on the Notes tab, which is shown after the number.

The Inputs tab

• Payload - a test payload, representing what the Alert Management System sends.
• Fields - read-only; the fields interpreted from the test payload, which expressions can then reference.
• Mocks - fixed responses that stand in for calls to external systems (such as am_lookup and am_setProperties) so configuration can be developed without touching the real AMS or IMS.
• Variables - the Integration Variables available for substitution using the {{variable_name}} format.
• Snippets - reusable pieces of expression text, local to the version, substituted the same way.
• Cached Snippets - like snippets, but calculated: the expression is evaluated once and the result reused per alert notification per incident spec, which saves repeated work such as remote lookups.

The Configuration tab

Three panes: a summary of the inputs on the left, the configuration tree in the middle, and the editor for the selected node on the right. The toolbar above the tree adds, clones, deletes, and reorders items. The tree contains:

• Deduplication - whether repeated notifications are collapsed, with optional field transformations that normalise values before comparison.
• Incident Specs - the heart of the configuration: each spec has a condition, an incident query, an alert signature, mappings, comments, actions, and optional problem specs. Specs are processed in tree order.
• Maintenance Windows - scheduled periods during which notifications are suppressed entirely; the Add button opens a creation wizard with friendly scheduling presets.

Invalid items are highlighted red in the tree, and edited items amber. The indicator at the top right of the page shows whether the version has unsaved changes.

The Testing tab

In-app tests evaluate a chosen expression from the configuration (a condition, query, mapping, or a maintenance window's condition) against a test payload and compare the result with an expectation. Tests can simulate a specific current time, which makes time-dependent configuration such as maintenance windows provable before activation. Tests are saved with the version and can be re-run at any time.

The Notes tab

Free-form notes for the version - what changed, why, and anything the next editor should know.

Version Label - an optional short label, entered above the notes and shown after the version number, for example Version 30 - Customer fix. It can be up to 120 characters (coming in version 4.7; 60 characters before that), and appears in the version lists once the version is saved. Keep longer explanations, such as ticket references or the reason for a change, in the notes. Like the notes, it can only be changed while the version is a draft.