Skip to content

ts status

Show the health, version, and topology of the targeted server.

Usage

text
ts status
ts status --server=<url>
ts status --local

Description

The first command to run against a server you are not sure about. It reports whether the server answers at all, what it considers its own health, and where it thinks its Portal, API, and hub live.

The topology matters more than it looks. Each service reports the address it publishes to the others, so a service showing an address you did not expect — a bare hostname where you configured a domain, say — explains a whole class of "it works locally but not from outside" problems without any further digging.

--local reads the install on this machine directly over loopback, which answers a different question: not "can I reach it" but "is it running here."

Examples

bash
# The stored default server
ts status

# Somewhere else, without changing the default
ts status --server=https://turbo.example.net

# The install on this box
ts status --local

# Health as a field, for a monitoring script
ts status --format=json

Output

text
Server:  http://127.0.0.1:8082
Health:  Healthy
Domain:
Portal:  http://build01.example.net:9090
API:     http://build01.example.net:9090
Hub:     http://build01.example.net:9090/hub

An empty Domain means no domain has been configured, so the server is publishing raw hostnames. That is fine on a dev box and usually wrong in production — see ts settings.

Exit Codes

0 when the server answers and reports itself healthy. -3 when it cannot be reached, or when it answers but reports itself unhealthy — in both cases something is wrong with the server rather than with your request.

  • ts config — Set the default server this uses.
  • ts settings — The domain and other global settings.