This tutorial will show you how to monitor your ORS and access radio / core networks logs (and more) on the Rapid.Space panel.
To investigate potential errors with the services or to get statistics you can use our monitoring app. Please go to your service page (by clicking on the service in the service section) and find the "monitor-setup-url" connection parameter, as shown on the screenshot. If the parameter is not present, please wait for 20 minutes after starting the service.
You will notice that when you enter the monitor App, the information of your ORS has been filled in automatically and started synchronisation. Once synchronisation finishes, the Monitor will load and display the list of Promises for your hosting subscriptions.
Before we get into the promise list, let's have a look at the App. The Monitor has a multiple-functions side panel:
For instance you can click on "Software Instances" and then on the enb instance to get statistics regarding eNB.
Here you can see the monitor page for the enb instance. On this page you can see the list of promises for this instance. Each promises checks a specific part of the instance is working correctly. Promises will appear orange or red if they are failing, which can help you investigate why your ORS is not working properly. Promises will also give you useful data.
Promises in Rapid.Space are executables doing arbitrary tasks and exiting with exit code 0 ("it works") or greater ("it doesn't work"). Everything in Rapid.Space is based on such Promises in order to automate the management of a Rapid.Space network. In case a Promise fails (eg. a computer not responding), a ticket will be created on the Rapid.Space Master in order for a user to follow up with this failing promise (more info in Understanding SlapOS Promises).
Please click on the "access private files" link to access the ORS logs.
Next you can go the log folder.
Here are some useful entries from the log folder:
To learn how to interpret the logs, please refer to How To Interpret ORS Logs.
After navigating to the monitor folder and then the promise folder, you will find logs from the promises. For instance, the "check-rx-saturated" JSON log will contain data about the RF levels from the RX antennas, which can be used to adjust rx_gain.
The sample values should ideally be below -10, if they are too high then the reception will be saturated which can prevent the ORS from correctly receiving radio.