Health and logs on the Deployment page
Where each application runs, which version it is, whether it is answering, and what happened at each attempt. Every figure says when it was measured.
The Deployment page shows where each application runs, which version it is, whether it is answering, and what happened at each attempt. You need no monitoring tool of your own.
One place or several
Each place where an application runs is called a destination. Open one destination, or bring several together in a Harbor to see them side by side. A Harbor is for looking. Installing is still done one destination at a time, each with its own confirmation.
What you can read
- The version that is running, and when it was installed.
- Whether the application is answering.
- How hard the application and its database are working: processor, memory and storage.
- Requests, errors and response time.
A measurement appears only where LobLogix can actually take it.
Every figure says where it comes from
Each figure carries its source and the time it was measured. A figure LobLogix did not receive is shown as unknown. It is never shown as zero, and never as healthy.
A release that was verified yesterday tells you about yesterday. Read the current figures for today.
What is kept from each attempt
The output of the build, of the changes to stored records and of the start, for every attempt, including the ones that failed. See If a release goes wrong.
What this is not
It is not an uptime commitment. The alpha has none. Monitoring of live applications, in production, comes after the alpha. See If you pause your subscription.