Create a Monitor

A monitor watches your catalogs and channels and alerts you when something needs attention. The fastest way to create one is to tell Aimée what you want to keep an eye on; you can also build one by hand. Both paths end in the same place — a monitor you can open, adjust, pause, or archive at any time. If monitors are new to you, start with Monitoring your catalogs and channels.

The quick way: describe it to Aimée#

1. Open Monitoring in the top navigation.
2. Type what you want to watch for into the box — for example "email me when any catalog's product count drops more than a quarter between imports" — or click one of the suggestion chips below it, like Product count drops sharply or Feed hasn't updated in a while.
3. Aimée opens in the side panel, looks at your actual catalogs and recent imports to suggest sensible thresholds, and builds the monitor with you. Nothing is active until it's published, and Aimée asks before publishing.

You can refine in the same conversation: change the threshold, add an email recipient, narrow it to specific catalogs.

The manual way: build it yourself#

1. On the Monitoring page, click Create manually. A new monitor opens; name it at the top of the page.

2. Under Watching, the two boxes read as a sentence — Check what the monitor reacts to on what it watches:

   • Check — after each catalog import, after each channel run, when an event is reported, or on a schedule.
   • on — All catalogs, Selected catalogs…, All channels or Selected channels…. The import and channel-run checks decide catalogs vs. channels for you, so they only offer their own two. With Selected catalogs… or Selected channels…, pick them from the list that appears — it is grouped by project. Catalog and channel names often repeat from one project to the next, so wherever the monitor names one that shares its name with another, it puts the project in front: Nordic Outdoor › Main catalog.

3. Under Condition, pick what to compare and set the thresholds — for example Product count change % is less than -25, or Hours since last successful import is greater than 24. A statistic with a fixed set of values, such as Run status, is set with is or is not and a value picked from its list rather than typed. The monitor triggers when the condition holds, and clears again on its own when it stops holding. A number you type as the value reads the same in every catalog: a dot or a comma is the decimal separator, so 1,50 becomes 1.5 when you leave the box, and 1.000 becomes 1. Thousands separators and units are not read — type 1000, not 1 000 or 12 kr — and the condition says so under it.

   • No condition is allowed too: leave the condition empty and the monitor matches every check — every import, every channel run or every matching event. Under an empty condition the page tells you what that means for this monitor, for example "No condition — every import triggers this monitor, so it triggers on the first one and stays triggered. Add a condition if it should clear again." A monitor that reacts to events is the exception: it clears again once none of the events it watches is open.
   • A scheduled check always needs a condition. Without one it would trigger once on everything it watches and never again, so publishing it is refused: "A scheduled check needs a condition to check — without one the monitor triggers once on everything it watches and never again. Add a condition before publishing."
   • Two kinds of change sit side by side for some numbers, and they answer different questions. Out-of-stock change counts products — five more than last time. Out-of-stock % change (points) follows the share of the feed instead: if 10% of your products were out of stock and now 15% are, that's a change of 5 points. On a small group the share is the steadier signal, because going from 2 products to 4 is a 100% jump that usually isn't worth an email.
   • Per-field statistics live in the same picker, as options with a gap in them: choose Fill rate % of… and type the field right there (price, gtin, …). On a monitor watching one catalog or channel, its real field names are offered as chips; watching several, type the name as it appears in your feeds — capitalisation doesn't matter.

4. Under Then, build the list of what happens. A new monitor starts with an empty list, so you choose what it does; + Add action adds the next one, any row's first box swaps it for a different action, and any row can be removed. A monitor needs at least one action — with none, the page says "Add at least one action — an alert, an email, a webhook or hold the publish." and publishing is refused until you add one:

   • Raise an alert — optional, and at most one per monitor. Warning or Error, shown on the dashboard and the affected catalog or channel. Leave it out if an email is all you want: the monitor still knows where it's triggered, it just doesn't show an alert. With no condition, on an import or channel-run check, the alert never clears: it sits on every catalog or channel the monitor watches, and each of them shows as needing attention until you pause the monitor or add a condition — the row says so before you publish. You can write your own alert text or leave it empty for an automatic summary. The text picks values the same way the condition does: choose the observed number, the affected catalog or channel, or a link back into the app from the picker rather than typing anything by hand — a value that can't be filled in is left in the alert exactly as written.
   • Send an email — pick team members and other addresses, and optionally write your own title and body. On a monitor that raises no alert, the Alert level value isn't offered for the wording — there is no alert to have a level. You can add this one more than once: each row is its own email, with its own recipients and its own wording, so one monitor can send a plain-language note to the store owner and a technical one to a shared team inbox (see Email alerts and verified addresses).
   • Hold the publish — for import and channel-run checks only: affected channels keep their previous feed live until the monitor clears (see Hold a channel's publish). While it's on the list, the alert is always an Error — and even without Raise an alert, a held publish raises an Error alert carrying the Publish button, so a hold is never hidden.
   • Send a webhook — sends a JSON message to another system, such as your CRM or a ticketing tool, at an https address you enter. Each webhook picks its events: Matched (every check where the condition holds: every import, channel run or event — not on a schedule), Triggered and Cleared. Send test beside the address checks it before you publish. Like email, you can add up to 10 (see Send monitor events to a webhook).

   The order of the rows doesn't matter — every action runs when the monitor triggers.

5. Press Publish. Nothing is checked until you do — edits stay a draft, and every published version is kept in history.

Publishing can come back with a note rather than an error. That happens when something the monitor refers to can never be filled in — a misspelled statistic, a per-field statistic naming a field the watched catalog or channel doesn't actually have, or the alert text referring to itself. The monitor still publishes; the note tells you that condition will never match, or that the wording will show up exactly as you typed it, so you can fix it. When a monitor watches all catalogs or channels, field names aren't checked at all — different catalogs carry different fields, so there's nothing honest to compare against. A monitor with no condition that raises an alert — or holds the publish, which raises one — also publishes with a note: its alert never clears, so every catalog or channel it watches shows as needing attention until you pause it or add a condition, and a hold holds every publish it watches, so until you pause it, remove the hold or add a condition, a feed only goes out through Publish on the alert. A monitor that does both gets one note, the hold's, which covers the alert too. The Then rows say the same before you publish.

Start from a catalog or channel#

On a catalog or channel page, the Add a monitor button in the top toolbar creates a monitor already scoped to that one catalog or channel and opens it for you to finish — handy when a specific feed has been giving you trouble.

Tips#

• One monitor can watch everything. A monitor on all catalogs checks each catalog separately and raises a separate alert per catalog — you don't need one monitor per feed.
• Pausing is instant. The on/off switch takes effect immediately and clears the monitor's open alerts — no publish needed. Use it when a monitor gets noisy while you fix the underlying problem.
• Watch it after publishing. A monitor's Alerts tab shows its current alerts (including any you archived) — when a problem clears, its alert disappears along with it, so the tab reflects what's wrong now rather than a permanent history. The history is on the Activity tab: every time the monitor triggered or cleared, with the emails and webhooks it sent each time. The status line at the top of the monitor says the same thing at a glance: All clear, or Triggered on the catalogs or channels it's currently firing on. A monitor without Raise an alert has nothing on its Alerts tab — the status line is where you see what it's triggered on. To judge a threshold, keep an eye on the monitor for the first imports or channel runs after you publish it, and loosen it if it's noisy — or re-tighten it later if it stays quiet.