Ping endpoints

Health-check endpoints for servers and the Dashboard.

Each Zato component offers an HTTP ping endpoint - a dedicated address that external monitoring tools can use to discern when the component is operational.

Component	TCP port	URL Path	Method	Expected result
Server	17010	`/zato/ping`	GET	200 OK with a JSON pong
Dashboard	8183	`/`	GET	302 redirect to `/zato`

To ping a server:

$ curl -XGET http://localhost:17010/zato/ping
{"pong":"zato","zato_env":{"result":"ZATO_OK","cid":"7cc657097fa0114017beeed6","details":""}}
$

To ping an instance of Dashboard - it answers with a redirect to its login page:

$ curl -I http://localhost:8183/
HTTP/1.1 302 Found
Location: /zato

All the other ports an environment listens on are in the default ports reference.

The whole subject - probe examples for Kubernetes and Docker Compose, and the difference between pinging Zato and having Zato ping the systems it calls - is under health checks.

Learn more

Production checklist What to confirm before an environment takes real traffic

Audit log Every request, response and error, and what you can do with them afterwards

Alerting Rules over the audit log, and the seven ways an alert reaches you

Health checks Have Zato ping your outgoing connections instead of waiting for traffic to fail

Logging What is written where, and how to ship it to Splunk, Loki, Elastic or Datadog

GitOps with enmasse Keep the whole environment in git as YAML and import it anywhere