Status history
The Status history of a lab records how its state changed over time. Because a data lab is compute that the Space starts, stops and configures, its status evolves through a series of events (running, stopped, starting, and so on). This page lists those events in chronological order so you can trace exactly when the lab entered each state and who triggered the change.
What the table shows
Each row is one status event. The table has the following columns:
By default the events are sorted with the most recent first. You can sort the list by any column by clicking its header.
Lab statuses
The status of a lab reflects both the state of its server (the machine in the cloud, which drives billing) and the state of the lab itself. The possible statuses are:
- LAB_RUNNING — the server and the lab are both running.
- SERVER_STARTING — the server is starting up in the cloud.
- SERVER_RUNNING — the server is running but the lab is not yet started (server not configured).
- SERVER_CONFIGURED — the server is started and the lab manager is running.
- SERVER_STOPPING — the server is stopping in the cloud.
- SERVER_STOPPED — the server is stopped in the cloud (billing is stopped).
- NO_SERVER — no server is currently associated with the lab.
- ERROR — the lab is in an error state.
Filtering the history
You can narrow the list of events using the search filters:
- Status — show only events for a single lab status.
- Creation date — restrict events to a range of start dates.
- End date — restrict events to a range of end dates.
