---
title: "Document Engine monitoring"
canonical_url: "https://www.nutrient.io/guides/document-engine/knowledge-base/monitoring/"
md_url: "https://www.nutrient.io/guides/document-engine/knowledge-base/monitoring.md"
last_updated: "2026-05-14T21:57:26.840Z"
description: "Document Engine monitoring guide for Nutrient Document Engine SDK with detailed instructions and code examples."
---

# Monitoring Document Engine

Document Engine behaves like a normal Docker container, so depending on the deployment infrastructure, it can be monitored with the [stats](https://docs.docker.com/engine/reference/commandline/stats) and [ps](https://docs.docker.com/engine/reference/commandline/ps) tooling for memory, CPU, and disk usage. The image definition also includes a [HEALTHCHECK parameter](https://docs.docker.com/engine/reference/builder/#healthcheck) so that it’s automatically monitored by Docker itself.

API endpoints are described in the documentation. In general, it’s important to keep an eye on the number of HTTP responses in the 500 and 4xx ranges, which can be done from the application that interacts with Document Engine.
---

## Related pages

- [hash_mismatch error](/guides/document-engine/knowledge-base/hash-mismatch-error.md)
- [How to fix 'Unknown CA' SSL errors in document uploads](/guides/document-engine/knowledge-base/remote-url-certificates.md)
- [Remote document storage](/guides/document-engine/knowledge-base/remote-document-storage.md)
- [Signing service not available](/guides/document-engine/knowledge-base/signing-service-not-available.md)
- [How to convert an XLSM file to PDF using Document Engine](/guides/document-engine/knowledge-base/xlsm-to-pdf-conversion.md)
- [Fix PDF download issues with NGINX reverse proxy](/guides/document-engine/knowledge-base/unable-to-download-pdf-with-nginx-reverse-proxy.md)