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 Basis monitoring & support

Every SID's Basis transactions, in one browser tab.

SM50, SM37, ST22, SM21, SM12, SM59, DB02 and ST03 across your whole landscape — live, cross-system, and without a SAPGUI session per host. Alerts route to the right on-call, routine operations run from the UI, and every privileged action is recorded.

Request a demo See the Basis use case

Transactions

9 cross-SID

SM50 · SM37 · ST22 · more

Access model

69-permission RBAC

Six built-in roles

Audit retention

up to 365 days

Exportable CSV / PDF

What "Basis monitoring" should actually mean

One web view across every SID

Cross-system SM50, SM37, ST22 and related transactions in the browser. No SAPGUI session per system, no jumping between hosts to answer one question.

Live, not refreshed-by-hand

The view updates on its own as new telemetry arrives from the collector agents. What you see is the current state of the landscape.

Trends, not just snapshots

Work-process utilisation, job runtimes and dump frequency tracked over time, with threshold-based alerts when a metric drifts.

Alerts that route to the right people

Severity, escalation policies and channel fan-out, scoped per customer or per system. The signal reaches the on-call who can act on it.

Codified routine operations

Start, stop and restart through runbooks and sapcontrol from the UI. Every action is recorded with the operator and source IP.

An attributed action history

A queryable record of who did what to which system — exportable for compliance reviews, with retention up to 365 days.

The transactions, on the web

Each is surfaced cross-system, so one question is answered once for the whole landscape instead of once per SID.

SM50Work processes

Live work-process state across every SID in scope, without a SAPGUI session per system.

SM37Background jobs

Job status, runtimes and failures, with history and threshold alerts on long-runners.

ST22ABAP dumps

A cross-system dump explorer with trend lines on dump frequency.

SM21System log

System-log entries surfaced and searchable alongside the rest of the estate.

SM12Lock entries

Outstanding locks visible per system for quick triage.

SM04User sessions

Logged-on users and sessions per application server.

SM59RFC destinations

RFC connection checks so broken destinations surface before a job does.

DB02Database health

Tablespace and database space signals in the same view as the rest.

ST03Workload analysis

Response-time and workload trends over time, not just a point-in-time snapshot.

How it reaches your systems

Outbound-only agent

A collector runs on each SAP host. It polls the platform for config and pushes telemetry — no inbound holes into your landscape.

Consolidated view

Telemetry from every SID lands in one place, attributed per system and per customer.

Encrypted credentials

SSH and SAP credentials are encrypted at rest. The security page covers the model in full.

Attributed actions

Every privileged action is written to an audit trail with operator and source IP.

Go deeper

Blog

A web-based alternative to SM50, SM37 and ST22

Why operating SAP through SAPGUI gets expensive across many SIDs, and what a web-native alternative covers.

Blog

How AI is changing SAP Basis monitoring in 2026

Where machine assistance genuinely helps a Basis team — and where it is still hype.

Topic

SAP HANA database monitoring

The database half of the picture: HANA signals, tenant isolation, and what to watch.

Capability

Security and audit model

How Farrenio handles SAP credentials, role-based access, and the audit trail of privileged actions.

Common questions

Does this replace SAPGUI?

No — it removes the need to open SAPGUI for routine cross-system Basis work. For deep configuration you still use SAPGUI. For "what is the state of the landscape right now", the web view is faster and works across every SID at once.

How does Farrenio reach my SAP systems?

Through an outbound-only collector agent on each SAP host. The agent polls the platform for its configuration and pushes telemetry over the same channel — no inbound firewall holes into your landscape. The security page covers credential handling.

Which transactions are covered?

SM50, SM37, ST22, SM21, SM12, SM04, SM59, DB02 and ST03 today, surfaced cross-system in one view. The list grows — the roadmap page tracks what is next.

Can a service desk triage without production access?

Yes. A read-only service_desk role sees alerts, incidents and short dumps with no SAP transaction access and no configuration changes. Role-based access is enforced by a 69-permission matrix.

Is this only for one SAP system?

No. It is built for many SIDs and, for service providers, many customers — with per-customer data isolation enforced at every query.

Put it in front of your own SIDs.

Install the collector on a non-production system and review the data with us. We will scope a short trial together — honest answer on fit, no pressure.

Request a demo See pricing