• English
  • Deutsch
  • Français
  • Italiano
  • Svenska
Book Now

Installation & deployment

otwatch is installed and configured by handel gmbh as part of the implementation project. This page describes the deployment options and what the customer provides.

On-premisesotwatchWindows / Linux, Docker or KubernetesOpenText platformcustomer networkread-onlyManaged serviceotwatchdedicated EU cloud environmentOpenText platformcustomer networkHTTPS, agreed accessHybridDashboards & alertingmanaged serviceCollectorcustomer networkoutbound only
Deployment options: on-premises, managed service or hybrid.

Deployment options

OptionRuns onTypical use
On-premises, standaloneOne Windows or Linux server (services or Docker containers), physical or virtual (VMware, Hyper-V)Small and medium environments, data must stay in the customer's network
On-premises, KubernetesCustomer's Kubernetes cluster, deployed via Helm chartsCustomers running OpenText or other workloads on Kubernetes
On-premises, distributedOne collector per site or network zone, central dashboards and alertingSeveral sites or segmented networks
Managed serviceDedicated, isolated cloud environment per customer in an EU regionNo customer infrastructure, operated fully by handel gmbh

All configuration (checks, alert rules, dashboards, infrastructure) is maintained as code and deployed via a pipeline, so DEV, QA and PROD environments are identical apart from parameters.

Sizing

Indicative values for Prometheus, Alertmanager and Grafana combined; the final sizing is defined in the project based on the number of nodes, metrics, collection interval and retention.

SizeEnvironmentResources
Small1–2 environments, up to 10 OpenText nodes2 vCPU, 4 GB RAM, 50 GB storage
MediumUp to 5 environments, up to 50 nodes4 vCPU, 8–16 GB RAM, 200 GB storage
LargeMore than 5 environments or 50 nodes, several sitesDistributed collectors, 8 vCPU and 32 GB RAM per collector, storage according to retention

Log collection (Loki) requires additional storage depending on log volume and retention.

Implementation steps

  1. Workshop: scope, environments, business transactions, thresholds, alert routing and reports.
  2. Provisioning of the otwatch environment (DEV/QA/PROD) as code.
  3. Accounts, network access and installation of agents and exporters on the OpenText systems.
  4. Configuration of checks, alert rules, dashboards, end-to-end tests and reports; validation in QA.
  5. Go-live in production, tuning of thresholds, knowledge transfer and handover.

Further reading

handel gmbh · otwatch documentation · Last updated 19 October 2026