What is it?
Monitoring feature in the MENU ecosystem is a connectivity issue tracking with self-resolving instructions that can be performed by Customers or their service partners. This informs them, in an automated way, of an issue that needs their attention and that may prevent them from receiving new orders (if the component that went offline is critical).
The goal behind it is solving the problem quickly and enhancing customer experience.
Components that are monitored are:
- POS Windows Service
- Order failure
Monitoring with all the components is set on a Venue level. Enabling/disabling Monitoring, as well as adding/removing alert recipients can be done by all user roles with the respective permissions for the Venue.
Critical vs. Non-Critical Components
Critical components are components that, when offline, prevent the Venue from receiving new orders.
Non-critical components are used by the Venue, but won’t prevent the Venue from receiving new Orders when offline.
Whether a component is critical or non-critical depends on the Venue’s integration type (e.g. how it receives Orders).
- For a Venue with Plain integration (e.g. receives orders via Tablet), if the Tablet goes offline, the Venue won't receive new Orders, therefore, the issue is critical
- For a Venue with POS integration, if the Tablet goes offline, the Venue will continue receiving orders through the POS integration, therefore, the issue is not critical
- For a Venue with POS integration (WS integration), if the POS Windows Service goes offline, that is critical
POS Windows Service
If a POS Windows Service does not send any pings to the Socket Server for more than 8 minutes, it will be deemed offline
If the POS Windows Service or the Socket Server gracefully close a connection, Monitoring will deem the Venue offline immediately
A Tablet will be deemed offline after it has not polled the API for more than 8 minutes
A Printer will be deemed offline after it has not polled the API for more than 8 minutes