NS ERP Workstation and NSPOS Normal State Monitoring Statistics
The following are the monitoring statistics included in NetSuite Point of Sale (NSPOS). The table includes the statistic name and a description of the content provided. Some statistics are available only in NetSuite ERP or at an NSPOS register.
|
Name |
NetSuite ERP (only) NSPOS (only) or Both |
Value Content |
|
Last Update from Replication Cloud |
Both |
Last date / time register connected with the cloud server for synchronization. |
|
Replication Status |
NetSuite ERP |
Register network connection status. Online, Offline, or Terminated. See Workstation/Register Statuses in NSPOS |
Note the AutoUpdater last time connection time/date stamp. Use this date prior to a new release to ensure the AutoUpdater application is functioning and can load new releases and fixes to your registers. The date should be the current date or, if reviewed early in the morning, yesterday’s date.
|
Name |
NetSuite ERP NSPOS or Both |
Property |
Value |
|
AutoUpdater |
NetSuite ERP |
Version |
AutoUpdater version installed on the register. |
|
AutoUpdater |
Both |
LastTimeConnection |
The AutoUpdater provides automatic upgrades of major NSPOS components. Last time AutoUpdater connected to the cloud. Can be used prior to a new release to ensure AutoUpdater is running and can load the upgrade to the register. The date displayed should be the current date or, if reviewed early in the morning, yesterday’s date. |
|
ComputerSystem |
NetSuite ERP |
Name |
Should match the register terminal’s Computer Name that can be seen in the system information. |
|
ComputerSystem |
NetSuite ERP |
TotalPhysicalMemory |
Size of physical memory. Should meet or exceed the minimum hardware specifications listed in the NSPOS Administrator Guide > NSPOS System Requirements. |
|
ComputerSystem |
NetSuite ERP |
SystemType |
Terminal hardware type, such as x64-based PC or x86-based PC. |
|
Database |
Both |
Version |
To be released with the NSPOS 2024.1.10 e-fix |
|
Database |
NetSuite ERP |
Uploaded / Count |
To be released with the NSPOS 2024.1.10 e-fix |
|
Database |
NetSuite ERP |
Not Uploaded / Count |
To be released with the NSPOS 2024.1.10 e-fix |
|
OperatingSystem |
NetSuite ERP |
LastBootUpTime |
Date and time the operating system (OS) was last restarted. |
|
OperatingSystem |
NetSuite ERP |
Caption |
Name of the operating system (OS), such as Microsoft Windows 10. Should match one of the systems supported in Appendix: PCI SSF Information for NSPOS. |
|
OperatingSystem |
NetSuite ERP |
Version |
Operating system (OS) version running on the register. |
|
OperatingSystem |
NetSuite ERP |
CurrentTimeZone |
The time zone used by the register, displayed as an offset in minutes from Greenwich Mean Time (GMT). GMT is also called Coordinated Universal Time (UTC). The number can be positive, negative, or zero. |
|
Point of Sale |
Both |
Version |
NSPOS release installed on register. Important for customizing registers, making upgrades and performing troubleshooting. |
|
Processor |
NetSuite ERP |
Name |
Register’s processor type. |
|
RaposDb |
NetSuite ERP |
DbSize |
Amount of data saved to the database. This monitor does not trigger an alert. |
|
RaposReplicationDb — Rapos Replication database handles the synchronization process between the register and the cloud. |
NetSuite ERP |
DbSize |
Amount of data saved to the item database. This monitor does not trigger an alert. |
|
Records to be processed |
Both |
Records to be processed |
Total number of records waiting to be downsync'd from the server to the register. |
|
Records to be processed (NetSuite ERP) To be processed (NSPOS) |
Both |
|
Number of each record type that is waiting on the server to be processed by the register. |
|
RTOPS |
NSPOS |
LastTimeConnection |
RTOPS is the replication agent application performing synchronization tasks for the RaposReplicationDb. Statistic lists the last date / time register connected with the cloud server for synchronization. |
|
Replication Statistics |
NetSuite ERP |
Conflicts |
Number of conflicts on the register. For example, if a price update for an item fails, it will show as a conflict. Should be zero, but a certain number of conflicts can be expected due to compromises between replication data filtering per store and replication performance. Unless you view a rapid increase in the number of conflicts, a few conflicts should not be taken as cause for immediate concern. |
|
Unsent Transactions |
Both |
|
Number of transactions being held on the register without upsync to the server. Should be zero, although total might be skewed by “control” transactions. |