Understanding POS Terminal Health in Xilnex for Lark

Understanding POS Terminal Health in Xilnex for Lark

Overview

POS Terminal Health gives you real-time visibility into your POS terminals across all stores. Issues such as terminals going offline or running low on memory or disk space are detected before they interrupt sales operations, rather than only being discovered after a store manager reports them.

This article covers what you'll see once POS Terminal Health has been set up.

Notes
Before you begin 
Ensure that a POS Terminal Health base has already been created.
If you haven't set one up yet, see [Creating a Base in Xilnex for Lark] for the instructions.

What's inside your POS Terminal Health base

Your base contains two tables:

 Tables
 What it shows you
 POS Terminal Master
Records information for each POS terminal, including its online status, available memory, disk space, application version, API version, database version, and latest synchronization timestamp
 POS Incident Logs
Records terminal incidents automatically generated from the POS Terminal Master through automated workflows.

You may locate the table in the left navigation panel of the Lark Base.


How data gets there

Xilnex ClassicPOS pushes terminal status events to Lark in real time as they occur, so there's nothing to trigger manually.
The Last Synced timestamp on each terminal record is updated whenever a new event is received, allowing you to quickly determine whether the terminal information is up to date.

Reading the dashboard

Your POS Terminal Health base includes two dashboards:
  1. POS Terminal Dashboard

    Provides an overview of:

    • Terminal online and offline status
    • Low memory terminals
    • Low disk space terminals
    • Out-of-sync terminals
    • Software version distribution by store and terminal
  1. Incident Dashboard

    Provides an overview of:

    • Open incidents by severity
    • Incident resolution trends
    • Terminals with the most incidents
    • Stores with the most incidents

Automated alerts and summaries

  1. Offline Detection
    1. Flags a terminal as soon as it stops sending heartbeat events, allowing issues to be detected before users report them.

  2. Low Memory Detection
    1. Flags a terminal when its available memory falls below a healthy threshold, helping prevent performance degradation.

  3. Low Disk Space Detection
    1. Flags a terminal when its available disk space becomes critically low, allowing storage issues to be resolved before they cause system failures.

Each detection triggers an automated workflow that creates an incident record in POS Incident Logs, eliminating the need for manual monitoring.

Settings Permissions

This base is primarily intended for operations teams and IT administrators rather than individual store staff. Access permissions are configured by your IT administrator in Lark, just like any other base.

The following permission settings are recommended for POS Terminal Health:

  1. POS Terminal Master and POS Incident Logs should be locked by default. Since the data is synced from Xilnex and will be overwritten during the next synchronization on the next sync if changed. Reserve edit access for IT administrators or designated data stewards only.
  2. Store managers and operations teams should generally be granted View access so they can monitor terminal status without modifying synchronized records
  3. To allow individual store managers to view only their own store's data, configure row-level permissions as follows:

    1. Navigate to Advanced Permission


    2. Click on the [Turn On Advanced Permissions]

    3. Select the necessary table that need to be set permissions
    4. Navigate to [Record Permissions]

    5. Set the permission to [Records related to members themselves] and save to apply changes
Notes
Locking specific fields or records requires Lark's Advanced Permissions feature, which is available only on supported Lark plans. On workspaces without that plan, this level of control isn't available. You'll only be able to set broad view or edit access per table, not per field.
Info
Good to know
  1. Nothing to configure day to day. Once the base is set up, all will happen automatically.
  2. Like other bases, only data from after the base was created will appear. Nothing from before is backfilled.
  3. Data is synchronized every minute.