- 3 minutes to read

Know when orders stop coming in

The worst way to learn that orders stopped arriving is a customer calling on Monday about Friday's orders. Nodinite counts the orders that are logged and tells you — in a Monitor View and by alert — when the number drops below what's normal, or when an expected confirmation never came back. That is proactive monitoring: you act before anyone complains.

  • ✅ See at a glance whether orders are flowing normally
  • ✅ Get an alert the moment the flow drops below your threshold
  • ✅ Know it before your customers do

When you need this

Orders normally come in all day. Today it's quiet — is it just a slow day, or has something broken between the web shop and the ERP? You want to know without waiting for someone to complain.

What you need

  • Access to a Monitor View that includes the order-flow check. Your administrator sets this up using the Non-Events monitoring in Nodinite, which watches a Log View and raises a state when the count of logged orders falls outside a threshold (for example, fewer than 50 orders in the last hour on a weekday), or when a confirmation isn't logged in time. Your administrator creates the Monitor View and assigns it to your Role.
  • If you want alerts, ask your administrator to include you as a recipient; alerts are sent through Alarm Plugins (email, Teams, and more).

Do it

  1. In the sidebar, open Monitor Views and click the one that covers orders.
  2. Find the order-flow resource in the list. Its icon and colour tell you the state; the description next to it says what was measured.
    Monitor states
    Example of resources in a Monitor View with different states.
  3. Check the bar chart directly under the filters for the overall picture: how many resources are OK, warning, or error right now.
    Monitor View Live Monitor tab with the status-code bar chart under the filters, showing Unavailable (2), Error (188), Warning (81), and OK (547) of 818 Resources (7.12)
    Example of the state summary under the filters of a Monitor View.
  4. To see whether this has happened before, open the history and pick a time span (Show last 7 days, 4 weeks, …).
    Monitor View History tab of Contoso Orders with the time span, the Timeline bar of Connection Error, Error, and Nothing to Monitor, and the state changes by date time (7.12)
    Example of the history for a Monitor View.

What you'll see

  • OK (green): the number of orders is within the expected range.
  • Warning (yellow) or Error (red): too few — or too many — orders were logged in the evaluated interval, or an expected confirmation is missing. The description states the actual count against the threshold.

If you're a recipient, the same information arrives as an alert, so you don't need to keep the page open.

If it doesn't work

  • You don't see a Monitor View for orders: ask your administrator to add one to your Role, or to set up the Non-Events check if it doesn't exist yet.
  • The state is red but orders look fine to you: the threshold may be set for a busier period (a holiday, for example). Tell your administrator — thresholds and excluded dates are configured in the Non-Events settings.
  • You want alerts but get none: your administrator selects which Alarm Plugin entries (and so which recipients) a Monitor View uses — see Alarm Plugins.
  • Still stuck? See Support.

Next Steps