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 — no SAP transaction access, no config changes, no token reveal. Granular 69-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 — 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 — space, workload and traces — with scope-aware filters that keep one tenant's data out of another's view. Built for landscapes with many HANA databases, not just one.

Request a demo Read the multi-tenant guide

The signals worth watching continuously

Space and growth

Tablespace and database space via DB02, tracked over time so a slow fill-up surfaces as a trend rather than a 2 a.m. outage.

Workload and response

Response-time and workload signals via ST03/ST04, so a degrading database is visible before users start raising tickets.

SYSTEMDB and tenants

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

Trace classification

Traces classified and filtered so the noise stays out of the way and the signal that matters is easy to find.

Multi-tenant, without leaking tenants

The hard part of monitoring MDC HANA is not collecting the metrics — it is showing them as one view while keeping the tenant boundary intact.

No cross-tenant leakage

Multi-tenant HANA is only useful to monitor if one tenant's operator never sees another tenant's data. Scope-aware filters enforce the boundary at query time, not by convention.

Discovery, not hand-maintained lists

Tenants and their databases are discovered rather than typed into a config file that goes stale the first time the landscape changes.

Allowlists over open access

What the monitoring layer is allowed to read is explicit. The default is least privilege, and the audit trail records what was accessed.

Database and application, side by side

A filling tablespace 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 of what to watch on a HANA database, and what to alert on.

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 — 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 signals you want to watch continuously, across many databases, in one place with alerting and history.

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 tablespace 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 show you the multi-tenant view and the isolation model — then you decide.

Request a demo SAP Basis monitoring