Track status and tail logs
An environment is a group of services that can be in different states. You can check the status of your environment at any time using the
veloctl env statuscommand:
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 https://backend-exciting-friday-64.awesomedev.com 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:
You can tail the logs from your services using the
veloctl env logscommand:
# 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
To better understand your connectivity to the environment and the active debug sessions, you could leverage the
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
Local Address Remote Address
Cluster connectivitywill verify your local machine can reach Velocity's cluster and your environment, to eliminate any issue that can arise from bad connectivity.
Active Development Sessionsis a list of the
veloctl env developsessions currently running on your machine. It helps you keep tabs on the services you are running locally.
Active Tunnelsis a list of connections that
veloctlcreated from your local machine to the cluster in order for your services to reach their dependencies.