Dashboard Basics
The Hostly dashboard shows the most important information for a selected workspace and its services.
It represents two levels:
- the workspace as an administration, plan, and usage unit
- the individual service with its technical state and configuration
Workspace dashboard
The workspace dashboard summarizes information assigned to the selected workspace:
- existing services
- current state of the services
- resource usage
- available limits
- warnings for upcoming Free Tier limits
Because an account can contain multiple workspaces, the plan, usage, and limits always refer to the workspace currently being viewed.
Resource overview
Hostly currently distinguishes the following categories:
| Category | Unit | Meaning |
|---|---|---|
| Compute | Core hours | Actual CPU share used over time |
| RAM | GiB hours | Actual memory used over time |
| Persistent storage | GiB days | Reserved persistent storage over time |
| Egress traffic | TiB | Outgoing internet traffic |
| Services | Count | All created services that have not been deleted |
In the Free Tier, the dashboard shows warnings before a usage-based limit is reached.
Service details page
The service details page combines information about a single service. This includes:
- the public service domain
- the current service status
- the Docker image in use
- a health check
- the live logs
- the available lifecycle actions
Logs
When the service details page is opened, Hostly provides the last 50 lines from stdout and stderr. New output is then streamed directly into the frontend.
Logs currently cannot be searched, filtered, or downloaded. They can of course be selected and copied.
Logs are visible only while the service is running. During a pause, they are retained. During restart, stop, or deletion, they are lost.
Status and reachability
The Running status describes the active container process, but it does not guarantee that the application is publicly reachable. There can be many reasons for this, but the most likely cause is that the container is misconfigured or the application it contains is not working correctly.
Several pieces of information are therefore relevant for correctly assessing the technical state:
Service status
+ Health check
+ Logs
+ internal container port
+ application function