# Monitor ParticleDB

Check health, collect metrics and connect database failures to application behavior.

Source: https://particledb.ai/operations/monitoring/

## Health

```bash
curl --fail http://localhost:7173/health
```

A health response confirms that the endpoint responds. Also monitor application query errors and latencies.

## Metrics

Configure the metrics listener with `--metrics-addr` or the metrics port setting supported by your release. The metrics endpoint uses `/metrics` and is separate from SQL requests.

Keep the endpoint on a trusted network. Review the actual metric names and types before writing alerts; metrics can change across versions.

## What to watch

- Query errors and request latency.
- Connection count and connection failures.
- Memory pressure, resource rejections and disk capacity.
- Persistence and recovery failures.
- Particle execution failures where the runtime is enabled.

## Logs

Collect startup and operational errors, but redact credentials and private query data. Use stable request or run identifiers to connect application errors with database events.

[Deployment](/guides/deployment/) · [Troubleshooting](/guides/troubleshooting/)

## Related

[Documentation home](/docs/) · [Troubleshooting](/guides/troubleshooting/)
