Logs and control
Read deployment and container logs, and start, stop or restart a workload.
Each application has two logs: a deployment log for each release, and an application log for the running container.
Read deployment logs
Section titled “Read deployment logs”Open the application and choose Deployments. Select a deployment to see the build or pull, container creation, health check, and swap stages.
Use this log when:
- An image could not be pulled or a repository could not be built.
- A candidate container failed to start.
- A health check prevented a rolling deployment from swapping traffic.
- A deployment stopped or was superseded before completion.
Read application logs
Section titled “Read application logs”Open Logs on the application to read the current container’s standard output and standard error. Use this log when a deployment completed but the process later reports an error, stops serving requests, or behaves unexpectedly.
Control the running workload
Section titled “Control the running workload”Use the application action menu to start, stop, or restart the current container. A restart is appropriate when the configuration has not changed and the process needs a clean start. If you changed variables, volumes, ports, labels, source, or resource limits, deploy instead so Serversinc creates a container from the new definition.
The next deployment replaces the container, so make lasting changes on the application, not the container.