Requirements

Ensure your environment satisfies all Trento Server, Trento Agent, network, cluster and SAP requirements before installation.

Trento Server requirements

Before deploying Trento Server, ensure your environment meets the following requirements:

Minimum hardware requirements

  • 4 GB of RAM.

  • 2 CPU cores.

  • 64 GB of storage. When using K3s, provide the storage under /var/lib/rancher/k3s.

  • 3 GB of PostgreSQL database space allocated per registered host (based on default retention period of 10 days).

Deployment-specific requirements

  • systemd deployment: Requires packages from SUSE Linux Enterprise Server for SAP applications 15 SP4 (or higher) or SUSE Linux Enterprise Server for SAP applications 16.0 repositories.

  • Kubernetes deployment: Cloud-native and OS-agnostic deployment. Supported environments include:

    • RKE2

    • A Kubernetes service in a cloud provider

    • Any CNCF-certified Kubernetes running on x86_64 architecture

    The Helm chart and the container images required for a Kubernetes-based deployment are available in SUSE public registry.

    The provided Helm chart deploys a basic, single-node instance intended to be used by customers without in-house Kubernetes expertise, or as a way to try Trento with a minimum of effort. Production-grade Kubernetes deployments require custom configuration and advanced Kubernetes knowledge.

Trento Agent requirements

Before installing and running Trento Agent, ensure your environment meets the following requirements:

  • Supported operating system: SUSE Linux Enterprise Server for SAP applications 15 (SP4 or higher) or SUSE Linux Enterprise Server for SAP applications 16.0.

  • Every host registered with Trento must have unique machine identifiers (IDs). If you clone a host, make sure to change the clone’s machine ID before starting the Trento Agent on it.

  • Every cluster registered with Trento must have a unique authentication key (authkey).

Trento Agent interacts with low-level system components in SUSE Linux Enterprise Server for SAP applications and maintains a minimal resource footprint to avoid impacting host performance.

Network requirements

Before deploying Trento, ensure your network allows the following inbound connectivity:

  • From any Trento Agent host to Trento Server at port TCP/80 (HTTP), or TCP/443 (HTTPS) if SSL is enabled.

  • From any Trento Agent host to Trento Server at port TCP/5672 (Advanced Message Queuing Protocol or AMQP).

  • From the user network to Trento Server at port TCP/80 (HTTP), or TCP/443 (HTTPS) if SSL is enabled.

  • If the Trento MCP Server is installed and enabled:

    • For a Kubernetes deployment, from the MCP client to the Trento Server ingress at TCP/80 or TCP/443. Internally, the MCP Server Pod uses TCP/5000 and TCP/8080 if the health check is enabled.

    • For a systemd deployment, from the user network to Trento MCP Server at TCP/5000.

  • Optionally: From the user network to Trento Server at ports TCP/4000, TCP/4001 and TCP/8080 (health checks for web, wanda and MCP, respectively).

  • From the Prometheus server, when it exists, to each Trento Agent host at the port used by the Node Exporter.

SAP requirements

To enable Trento to discover and monitor your SAP systems, ensure your SAP environments meet the following requirements:

  • An SAP system must run on a HANA database to be discovered by Trento. Additionally, the dbs/hdb/dbname parameter in the SAP system’s DEFAULT profile must be set to the correct database (tenant) name.

  • The Trento Agent must be installed in all the hosts that are part of the SAP system architecture, specifically:

    • The host running the ASCS instance.

    • The host running the ERS instance (if it exists).

    • All hosts running an application server instance.

    • All database hosts.

Cluster requirements

Ensure the cluster meets the following requirement:

  • All cluster nodes must be online during the initial discovery phase.

    After the cluster is discovered, all nodes can be stopped. Trento continues to monitor the cluster.