NS ERP Workstation & NSPOS Normal State Monitoring Statistics
Monitoring Statistics NSPOS 2020.1.X and Later
The following are the monitoring statistics included in NSPOS 2020.1.X and later. The table the statistic name and a description of the content each statistical value provides. 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 2020.1.X and Later. |
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. |
|
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 the PA-DSS guide corresponding to the register's NSPOS release. |
|
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. Note: Not available in NSPOS 2020.1.1. |
|
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. |
Monitoring Statistics NSPOS 2018.2.X – 2019.1.X
For releases 2018.2.X through 2019.1.X, workstation monitoring in NetSuite ERP provides the following statistics about each register. Normal state monitoring from an NSPOS register is not available for the 2018.2.X and 2019.1.X releases.
Note the AutoUpdater last connection date. 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 |
Value |
|
Last Connected to Server |
Last date / time register connected with the cloud server for synchronization. |
|
Offline |
Register network connection status. Selected means register is offline. |
Available on the NetSuite ERP RA-Workstation Record Only
|
Name |
Property |
Value |
|
AutoUpdater |
Version |
AutoUpdater version installed on the register. |
|
AutoUpdater — The AutoUpdater provides automatic upgrades of major NSPOS components. |
LastTimeConnection |
Last time AutoUpdater connected to the server. 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 |
Name |
Should match the register terminal’s Computer Name that can be seen in the system information. |
|
ComputerSystem |
TotalPhysicalMemory |
Size of physical memory. Should meet or exceed the minimum hardware specifications listed in the NSPOS Administrator Guide > NSPOS System Requirements. |
|
ComputerSystem |
SystemType |
Terminal hardware type, such as x64-based PC or x86-based PC. |
|
Database |
DatabaseOwnerId |
ID of database used by the NSPOS register. For standalone or Server with POS registers, value is the database ID of the register. For POSClient registers, value is the database ID of the connected Server with POS register database. |
|
Database |
LocationId |
ID of the location in which the register is running. Use to verify that the register is assigned to the correct location. |
|
OperatingSystem |
LastBootUpTime |
Date and time the operating system (OS) was last restarted. |
|
OperatingSystem |
Caption |
Name of the operation system (OS), such as Microsoft Windows 10. Should match one of the systems supported in the PA-DSS guide corresponding to the register's NSPOS release. |
|
OperatingSystem |
Version |
Operating system version running on the register. |
|
OperatingSystem |
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 |
Version |
NSPOS release installed on register. Important for customizing registers, making upgrades and performing troubleshooting. |
|
Processor |
Name |
Register’s processor type. |
|
RaposDb — The Rapos database contains the register’s basic NSPOS information, including location, customer, promotion and transaction data. |
RowSize |
Current space reserved for the application using this database. Should not exceed 10 GB. See RowSize and DbSize in NSPOS 2018.2.X – 2019.1.X. |
|
RaposDb |
Version |
Rapos database application version on register. |
|
RaposDb |
DbSize |
Amount of data saved to the database. Should be monitored to ensure value is below 10 GB maximum. See RowSize and DbSize in NSPOS 2018.2.X – 2019.1.X. |
|
RaposInventoryDb — Also called the “Item” database, the RaposInventory database handles all item-related data, including item name, description, UPC, price, price level, and location-specific selling points. |
RowSize |
Current space reserved for the application using this database. Should not exceed 10 GB. |
|
RaposInventoryDb |
Version |
RaposInventory database application version on register. |
|
RaposInventoryDb |
DbSize |
Amount of data saved to the database. Should be monitored to ensure value is below 10 GB maximum. |
|
RaposReplicationDb — Rapos Replication database handles the synchronization process between the register and the server. |
DbSize |
Amount of data saved to the item database. Should be monitored to ensure value stays below the 10 GB maximum. |
|
RaposReplicationDb |
RowSize |
Current space reserved for the application using this database. Should not exceed 10 GB. |
|
RaposReplicationDb |
Version |
RaposReplication database application version on register. |
|
Replication Push Agent — Application performing synchronization tasks for the RaposReplicationDb. |
Version |
Version of push agent used to perform synchronization tasks. |
|
ReplicationStatistics |
XmlFilterToProcess |
Amount of data to be processed from or to the register. Should be zero. |
|
ReplicationStatistics |
XmlInboxConflicts |
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 observe a rapid increase in the number of conflicts, a few conflicts should not be taken as cause for immediate concern. |
|
ReplicationStatistics |
XmlInboxToApply |
Number of unprocessed records downloaded and waiting to be processed. Should be zero. |
|
ReplicationStatistics |
UnsentTransactions |
Number of transactions being held on the register prior to sending. Should be zero, although total might be skewed by “control” transactions. |
RowSize and DbSize in NSPOS 2018.2.X – 2019.1.X
You should review the RowSize and DbSize values for each database type to ensure volumes stay below the maximum limit of 10 GB.
-
RowSize – The space reserved by the database application to manage saved information. For example, an empty database might be allocated 1 GB (gigabyte) to start. When data exceeds 1 GB, it allocates another GB of space, changing the RowSize to 2 GB.
A database might contain 9.1 GB of data (DbSize), but the RowSize will show the reserved space as 10 GB. Because RowSize is a space-allocation indicator only, it should not be flagged as an immediate problem if it shows 10 GB.
-
DbSize – Represents the actual volume of data saved to the database. It should be monitored to ensure it stays below the 10 GB maximum. Problems can occur when data is close to 10 GB, and will occur if data requirements exceed the 10 GB maximum reserved by the RowSize.
Ensure each DbSize (database size) value stays below 10 GB.