Track Status and Logs

Environment Status

A Velocity Environment is a group of Velocity Services that can be in different states. You can check the status of your Velocity Environment at any time using the following command:
veloctl env status
Watching environment exciting-friday-64 status...
Point in time: 2015-10-21T19:28:00Z
Service Status Version Public URI Tunneled
database Ready mysql:5.7
backend Ready ...6c6ed6e8d52388190 True
worker Ready ...91698f97536e95126
Overall status: Ready
Your environment is ready! To develop on your services with command <CMD>, please run:
veloctl env develop --service backend -- <CMD>
veloctl env develop --service worker -- <CMD>
The following columns appear:
Column Name
The service name
Pending / In Progress / Ready / Failed
The version of the service currently running
Public URI
If the service can be exposed, its public URI will appear
Will show if the service is currently developed on a local computer
(using env develop)

Tailing Logs

You can tail the logs from your Velocity Services using the following command:
# Tail all the logs in the environment
veloctl env logs
# Tail logs only from the 'backend' and 'worker' services
veloctl env logs --service backend --service worker
For additional options see the CLI Reference.

Overall Status

To better understand your connectivity to a Velocity Environment and the active debug sessions, you could leverage the following command:
veloctl status
veloctl version v0.2.0
Cluster connectivity (context: velocity-VELOACME): [OK]
Active Development Sessions
Environment Name Service name Command Process ID
sunday-shine website yarn start 40146
Active Tunnels
Local Address Remote Address backend:3002
Cluster connectivity will verify your local machine can reach your Velocity Context and your Velocity Environment, to eliminate any issue that can arise from bad connectivity.
Active Development Sessions is a list of the veloctl env develop sessions currently running on your machine. It helps you keep tabs on the Velocity Services you are running locally.
Active Tunnels is a list of connections that veloctl created from your local machine to your Velocity Context in order for your Velocity Services to reach their dependencies.