Metrics Collector microservice is collecting and storing information about the user’s register machine.
It provides a unique ID for every Hardware machine that allows ERPLY to identify customer’s hardware machines in order to collect information about the machine’s specifications, performance etc.
The Metrics microservice is installed by default along with Logger microservice while installing the Installer app on every machine from Installer 2.4.0 version.
Metrics Collector ms collects and sends the following information to the cloud:
- average CPU* usage over the last 5 minutes (default);
- RAM* usage as a percentage;
- Total amount of RAM in MB(megabytes);
- Operation System version;
- CPU architecture;
- Used disk space as a percentage;
- ERPLY service response time;
- POS version;
- Browser version;
- List of ERPLY services;
- ERPLY service configurations and ERPLY certificate information;
- Small diagnostics of the operation of ERPLY services (service status or why it didn't start);
- Computer name;
- Host id.
CPU* - Central Processing Unit - is the primary component of a computer that acts as its “control center.” The CPU, also referred to as the “central” or “main” processor, is a complex set of electronic circuitry that runs the machine’s operating system and apps. The CPU interprets, processes and executes instructions, most often from the hardware and software programs running on the device.
RAM* - random-access memory - RAM is used as a short-term memory storage for a computer’s central processing unit (CPU).
The collected information is used by the ERPLY support team for a more detailed view of the client’s register machine setup.
From 4.51.54 Brazil POS version when Metrics collector microservice is running and it is detected that receipt printing took longer than 5 seconds, a detailed list of measurements will be sent to the Metrics collection service, explaining how much time each step took.
Following steps are recorded:
- waiting for CAFA to load
- printing via browser via Actual Report templates
- printing via browser via receipt link
- printing via Microservice by document id
- printing via Microservice with PatchScript
- rendering Actual Report html for printing MS
- total print time
- fetching Actual Reports dataset
- creating receipt data
- creating PatchScript via receipt-printout-api or creating from POS in case latter is not running
- fetching payment info