Does the agent need inbound network access to my SAP hosts?

No. The agent is outbound-only. It polls Farrenio over HTTPS for its config and pushes metrics the same way. No new firewall rules, no exposed ports on your SAP boxes.

Can my service desk see alerts without touching production?

Yes. The service_desk role is read-only on alerts and incidents, with no SAP transaction access, no config changes and no token reveal. Granular 92-permission RBAC means you can carve out exactly what each team sees.

How long does a proof of concept take?

A 30-minute call to scope. We typically have one production SID streaming live metrics within an hour of agent install, and the rest of the landscape follows as fast as you can roll out the package.

SAP HANA database monitoring

Watch HANA across every tenant, without crossing the line.

SYSTEMDB and tenant databases as one operational view covering space, memory, workload and traces, with scope-aware filters that keep one tenant's data out of another's view. Built for landscapes running many HANA databases, not just one.

Request a demo Read the multi-tenant guide

The signals worth watching continuously

Space and growth

Data and log volume fill via DB02, trended with days of headroom, because a full log volume stops the database rather than merely slowing it.

Workload and response

Response time and used-memory pressure via ST03/ST04, so a database drifting toward its allocation limit shows well before an OOM or a wave of tickets.

SYSTEMDB and tenants

SYSTEMDB and each tenant database read as one operational view across the SYS_DATABASES schema, without flattening the boundary between them.

Trace classification

Traces classified and filtered so routine chatter stays out of the way and the entries that actually matter are easy to find.

Multi-tenant, without leaking tenants

The hard part of monitoring MDC HANA is not collecting the metrics. It is reading across SYSTEMDB and every tenant as one view while keeping the tenant boundary intact.

No cross-tenant leakage

Multi-tenant HANA is only worth monitoring if one tenant's operator never sees another tenant's data. Scope-aware filters enforce that boundary in the read path itself, at query time, not by convention.

Discovery, not hand-maintained lists

Tenant databases are discovered from SYSTEMDB, not typed into a config file that goes stale the first time the landscape changes.

Allowlists over open access

What the monitoring layer may read, namely the M_* system views and nothing more, is explicit. The default is least privilege, and the audit trail records what was accessed.

Database and application, side by side

A filling data volume and a long-running job are often the same incident seen from two angles. Farrenio puts HANA signals next to the SAP Basis transactions, SM50, SM37, ST22 and the rest, so you are not correlating across two tools at the moment it matters. Alerts route by severity and escalation policy, and every privileged action is written to an audit trail.

Go deeper

Blog

Monitoring multi-tenant HANA without breaking SYSTEMDB isolation

Discovery, trace classification, allowlists and scope-aware filters, in detail.

Blog

HANA performance monitoring: the signals that matter

A practical shortlist for a HANA database: alert on the few things with little warning, trend the rest.

Topic

SAP Basis monitoring

The application half: SM50, SM37, ST22 and related transactions, cross-system.

Capability

Security and audit

How credentials are protected and how access is scoped and recorded.

Common questions

How does Farrenio see HANA?

Through the same outbound-only collector agent that covers the rest of the SAP host. There is no inbound connection into your database, since the agent pushes telemetry out to the platform.

Can you monitor multi-tenant (MDC) HANA safely?

Yes, that is the point of the design. SYSTEMDB and tenant databases appear as one view, but scope-aware filters keep each tenant's data from leaking to another. The blog post on multi-tenant HANA walks through how.

Does this replace HANA Studio or the cockpit?

No. For deep database administration you still use the native tools. This is the operational overlay: the handful of signals worth watching continuously across many databases, in one place, with alerting and history behind them.

How does this relate to SAP Basis monitoring?

HANA is the database half; SM50/SM37/ST22 and the rest are the application half. Farrenio puts both in one view so a slow job and a filling data volume are visible side by side. See the SAP Basis monitoring page.

See your own HANA databases in one view.

Point the collector at a non-production HANA and review the data with us. We will walk you through the multi-tenant view and the isolation model, then you decide.

Request a demo SAP Basis monitoring