Search…
Check Status & Logs

Environment Status

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 status command:
1
veloctl env status
Copied!
1
Watching environment exciting-friday-64 status...
2
3
Point in time: 2015-10-21T19:28:00Z
4
5
Service Status Version Public URI Tunneled
6
database Ready mysql:5.7
7
backend Ready ...6c6ed6e8d52388190 https://backend-exciting-friday-64.awesomedev.com True
8
worker Ready ...91698f97536e95126
9
10
Overall status: Ready
11
12
Your environment is ready! To develop on your services with command <CMD>, please run:
13
14
veloctl env develop --service backend -- <CMD>
15
veloctl env develop --service worker -- <CMD>
Copied!
The following columns appear:
Column Name
Description
Service
The service name
Status
Pending / In Progress / Ready / Failed
Version
The version of the service currently running
Public URI
If the service can be exposed, its public URI will appear
Tunneled
Will show if the service is currently developed on a local computer
(using env develop)

Tailing Logs

You can tail the logs from your services using the veloctl env logs command:
1
# Tail all the logs in the environment
2
veloctl env logs
Copied!
1
# Tail logs only from the 'backend' and 'worker' services
2
veloctl env logs --service backend --service worker
Copied!
For additional options see the CLI Reference

Overall Status

To better understand your connectivity to the environment and the active debug sessions, you could leverage the veloctl status command:
1
veloctl status
Copied!
1
veloctl version v0.2.0
2
3
Cluster connectivity (context: velocity-VELOACME): [OK]
4
5
Active Development Sessions
6
Environment Name Service name Command Process ID
7
sunday-shine website yarn start 40146
8
9
Active Tunnels
10
Local Address Remote Address
11
127.0.0.1:3002 backend:3002
Copied!
Cluster connectivity will verify your local machine can reach Velocity's cluster and your environment, to eliminate any issue that can arise from bad connectivity.
The Active Development Sessions is a list of the veloctl env develop sessions currently running on your machine. It helps you keep tabs on the services you are running locally.
Active Tunnels is a list of connections that veloctl created from your local machine to the cluster in order for your services to reach their dependencies.
Last modified 1mo ago