Logging system within Brazil POS

9. september 2024


Erply Brazil POS has the Logging system.The logging system works by Logger microservice that is installed by default for every Brazil POS user. It stores all microservice data to the Erply Cloud system. Logger ms makes updates once a day. 


From version 4.51.40 the Brazil POS includes logging functionality as well. If it is enabled all steps made in Brazil POS will be also stored to the Erply Cloud system. This information will be accessible only for the ERPLY developers team for internal use.

This logging system can help to investigate, replicate and fix all sporadic and not reproducible issues reported by Brazil POS users. 

Note: the logging functionality requires logger microservice to be installed on the PC. The logger ms is installed by default with Installer starting from version 2.4.1.
In case you do not have this installed please follow steps below:

  1. Navigate to the Wizard posow.erply.com 
  2. Login with you Erply credentials (client code, username, password).
  3. Navigate to the Hardware -> Installer App -> Micro-service manager
  4. From the ADDNEW MICRO-SERVICE list select the “logger-ms”. Click Continue.
  5. Click on the ‘Install latest’.
  6. Press ‘Start’ green button.
  7. Go to the POS and refresh the POS page.

How to enable logging in the Brazil POS?

Login to the Brazil POS https://epos.erply.com/latest/ with valid credentials.
Navigate to the POS Settings -> Debug.
Enable “Enable logging using logger-ms” (this setting is register-based!)
Close POS settings.
Refresh the POS page. Once POS is loaded there will be a message on the top “Logs are being saved!”. It means that the logging system is enabled and running. 

Report the issue to Erply team

If you are experiencing some issues in the Brazil POS or any microservice installed on your device please contact Erply Support, describe the issue and include the following information:

  • Erply client code
  • POS version (example 4.51.39) 
  • POS ID (check in the Back Office -> Retail -> Registers -> # column)
  • Date and approximate time when the issue occurred