# 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 | 11223 | `/zato/ping` | GET | 200 OK with a JSON confirmation |
| Dashboard | 8183 | `/` | GET | 302 redirect to `/zato` |

To ping a server:

```text
$ curl -XGET http://localhost:11223/zato/ping
{"is_ok":true, "cid":"20260921-180542-8418-c1e5d65e18f62730a"}
$
```

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

```text
$ 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](https://zato.io/docs/admin/ports.html).

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](https://zato.io/docs/admin/health-checks.html).

## Learn more {#learn-more}

- [Production best practices](https://zato.io/docs/admin/production-best-practices.html) - What to configure before an environment takes real traffic
- [Audit log](https://zato.io/docs/admin/audit-log/) - Every request, response and error, and what you can do with them afterwards
- [Health checks](https://zato.io/docs/admin/health-checks.html) - Have Zato ping your outgoing connections instead of waiting for traffic to fail
- [Logging](https://zato.io/docs/admin/logging.html) - What is written where, and how to ship it to Splunk, Loki, Elastic or Datadog
- [GitOps with enmasse](https://zato.io/docs/admin/enmasse.html) - Keep the whole environment in git as YAML and import it anywhere