Skip to main content

Filtering & Tracing

The POS Monitoring tool provides powerful filters to help you find exactly the traces you need — whether you're debugging a specific order or monitoring overall endpoint health.

Basic Filters

These filters are always visible on the dashboard:

FilterDescription
From / ToDate and time range
VenueFilter by a specific restaurant
RMSFilter by reservation system (e.g. Zenchef, SevenRooms)
POSFilter by POS system (your system)
Flow TypeDirection of communication (see below)
StatusAll, Success, or Failed

Flow Type Filter

Isolate communications by direction:

Flow TypeDescription
AllShow all communication flows
Mozrest to POSMozrest sending requests to your endpoints (create order, get tables)
POS to MozrestYour POS sending webhooks to Mozrest (order updates, closures, voids)
RMS to MozrestThe RMS sending reservation events to Mozrest
Mozrest to RMSMozrest forwarding POS data back to the RMS

Click Advanced Search to reveal additional filters for tracing specific orders:

FieldDescription
POS Order IDYour order identifier
POS Check NumberThe check number for a specific transaction
RMS Reservation IDThe reservation identifier from the RMS
RMS Reservation ReferenceThe reservation reference number

Tracing an Order End-to-End

When you need to follow a specific order through the entire RMS → Mozrest → POS chain:

  1. Get the identifier — the order ID or check number from your POS.
  2. Open Advanced Search and enter it in the appropriate field.
  3. Review all matching traces — you'll see the full chain: the RMS event arriving at Mozrest, Mozrest calling your endpoint, and your response.
  4. Click into individual traces to inspect payloads, responses, and errors.

Example

A venue reports that an order was created but has wrong data:

  1. Enter the POS Check Number in Advanced Search.
  2. Find the Mozrest → POS trace — click into it to see the exact payload Mozrest sent.
  3. Check the request body — does it contain the correct table, party size, and guest details?
  4. Check your response — did your endpoint return the expected order ID and check number?

This tells you immediately whether the issue is in the data Mozrest sent (RMS/Mozrest side) or in how your POS processed it.