FAQ

Short answers to the questions we hear most often.

Access and data

How does otwatch access our systems?

Read-only, with dedicated technical accounts. Content Server and Intelligent Viewing are accessed via OAuth2 through OTDS. See Security & data protection.

Does otwatch see our documents?

No. otwatch collects metrics, status information and, if agreed, log lines, never document content. End-to-end tests only use dedicated test documents.

Where is our data stored?

On-premises in your network, or in a dedicated environment in an EU region. Each customer has its own environment.

Installation and effort

Does monitoring put load on our systems?

The load is small: short read-only queries at a fixed interval. End-to-end tests behave like a single additional user.

Which OpenText versions are supported?

All OpenText Extended ECM releases from 22.x onwards. We recommend the annual x.4 releases.

Integration

We already have a monitoring tool. Why otwatch?

otwatch knows OpenText from the inside: agents, workflow locks, queues, index partitions and archive volumes. Alerts can be forwarded to your existing monitoring or ITSM platform.

Does it work with ServiceNow, Jira or Teams?

Yes. See Integrations & API.

Are we locked in?

No. otwatch is based on open-source standards; configuration and dashboards remain readable and transferable.

Operations

How fast do alerts arrive?

Critical checks run every 15–60 seconds; an alert is raised once a fault persists for the defined duration, typically within a few minutes.

What happens during our maintenance?

Notifications are suppressed for the planned window; metrics are still recorded. See Maintenance windows.

Does otwatch use AI?

No. Anomaly detection and root cause analysis are rule- and statistics-based and therefore transparent.

handel gmbh · otwatch documentation · Last updated 19 October 2026