It's complicated.
Have you tried monitoring your HANA multi-tenant environment? It's harder than it sounds. In prior posts, we wrote about:
There are previously mentioned issues connecting the SAP HANA Administration Console to the tenant database because specific ports are required. There's not much documentation about connecting to a tenant for monitoring. Although most SAP Business Suite on HANA systems use DBACOCKPIT or Solution Manager (see our SAP Monitoring Tools Overview), it is typically connected to a single default tenant or automatically chosen during SAP installation.
It took a little detective work, but we've unraveled the mystery of how to connect locally, and remotely via hdbsql and HANA studio to each tenant. Otherwise, other monitoring tools can't be used, and we're left with tools like HANA Cockpit that only shows the first tenant as seen below (The indexserver on port 30003).
When creating a tenant, HANA assigns a port to the new hdbindexserver, however, that port is not used for SQL connection via ODBC or JDBC but a different port. We found that while you're on the actual HANA server as <sid>adm, you can connect without specifying the port, as HANA figures out from the instance number (-i option) and the database (-d option). Thus, this is Method 1 for determining these ports after the connection.
Run “sapcontrol –nr <instance#> -function GetProcessList” to find the tenant (DBNAME)
Get the process ID (PID)
Run “HDB info” to find the corresponding hdbindexserver matching the PID (from step 2)
Find the port and add 1 to get the SQL port used for ODBC or JDBC connection
NOTE: If the <SID> was converted from SingleDB then the first tenant would be at port 30015
In a multi-tenancy (MDC) HANA environment each tenant has its own indexserver, but all of them share a single sapstartsrv responsible for the startup and shutdown as well as common services like the daemon. It would be ideal to monitor all tenants from a single console, which today exists in the studio via System Monitor, but it's not a centralized configuration so each HANA administrator needs to set up their workspace accordingly using the method we described above. Likewise, and even more complex would be to setup individual tenant connections to the Solution Manager. What are you using today and how is your experience?
For third-party monitoring of HANA multi-tenant environment, we provide the HANA Management Pack for SCOM which supports centralized operations monitoring of such HANA environment, or for a FREE Demo or Trial of IT-Conductor cloud-based HANA monitoring.