---
title: "Monitoring PageSeeder"
source: https://dev.pageseeder.com/guide/installation/monitoring_pageseeder.html
description: "This document explains how to use PageSeeder's dbmonitor health check endpoint to verify that core infrastructure components (servlet container, web server, and database) are functioning and communicating properly."
last_updated: 2026-09-08T11:43:07+10:00
tokens: ~391
---

# Monitoring PageSeeder

Unless prevented by firewall or other network security, the [dbmonitor](../../api/services/dbmonitor_get.md) URL is publicly accessible on any PageSeeder server. Receiving the standard response doesn’t mean the system is free from problems, but not getting it guarantees problems exist. This is a health check to determine whether the most basic aspect of the system is functioning.

The content of the *dbmonitor* response is as follows:

```xml
<monitor message="Connected to database and accessed a group OK"/>
```

Getting this response signals that PageSeeder’s key infrastructure components (servlet container, web server and database) are alive and communicating.

To access the [dbmonitor](../../api/services/dbmonitor_get.md) on PageSeeder version 6 and higher:

```text
http://[server]/ps/api/dbmonitor
```

Before version 6:

```text
http://[server]/ps/servlet/com.pageseeder.DBMonitor
```

e.g. [https://eval.pageseeder.com/ps/api/dbmonitor](https://eval.pageseeder.com/ps/api/dbmonitor)

This URL will work with the IP address instead of the server name. Getting a result from the IP address could mean problems with the DNS records, SSL certificates or firewall rules.

https://\[internal\_network\_IP\]/ps/api/dbmonitor

https://\[public\_IP address\]/ps/api/dbmonitor

If you are not sure about the general setup of your PageSeeder server, verify it with an external testing service like one of the following:

[https://www.ssllabs.com](https://www.ssllabs.com/)

[https://www.hardenize.com/](https://www.hardenize.com/)