You will notice that when you enter the monitor App, the information of your VM 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:

• Promises: all promises of all services on all computers.
• Software Instances: all instances (hosting subscriptions) of all services on all computers.
• Hosting Subscriptions: all services from all computers (similar to Rapid.Space Dashboard).
• Monitor Configurations: all data sources (instances), loaded from master.
• Syncronisation: update the monitor data by querying all services and crawling data.
• OPML Import / Export: used to import and export the current configuration.

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 XXX Understanding SlapOS Promises).

Note, that the Monitor reports detailed instance status but does not provide any management functions such as handling of tickets. This has to be done in the Rapid.Space Master Dashboard which in turn only displays the global status of an instance (green, orange, red). Also note that the Monitor works autonomously from the Rapid.Space Master, so even if the Master is down, the Monitor will continue working.

Finally, as the Monitor was not accessed for a specific computer or instance, it will show the global network status. Clicking on one of the red/yellow/green computer or instance buttons will load the monitor with a scope set on the respective computer/instance.

You can use the Filter button in the subheader and the search field to filter the list of promises.

One common use case for the filter is to display only erroring promises by filtering for the status field with exact match ERROR. This helps to keeping track of what to fix only. If you have no idea how to fix it, feel free to contact us by adding a ticket(XXX final links) from your Rapid.Space console.