Every SID's Basis transactions, in one browser tab.
SM50, SM37, ST22, SM21, SM12, SM59, DB02 and ST03 across your whole landscape, live and cross-system, and without a SAPGUI session per host. Alerts route to the on-call who can act, routine operations run through sapcontrol and runbooks from the UI, and every privileged action is on the audit trail.
What you stop doing by hand
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 instances through sapcontrol and runbooks from the UI, with each action permission-checked and recorded against operator and source IP.
An attributed action history
A queryable record of who did what to which system, exportable for compliance reviews and retained 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.
DIA/BTC/UPD/ENQ/SPO work-process state across every SID, so you spot a WP stuck in PRIV mode or a runaway before the dispatcher queue backs up.
Released, active and cancelled jobs with runtime history and threshold alerts when a job overruns its window.
A cross-system runtime-error explorer showing short text, frequency and trend, so a spike surfaces before the helpdesk does.
The system log tailed and filtered across every SID at once, not one instance at a time.
Lock-table entries per system, with orphaned locks drillable by user or object.
Logged-on users and sessions per application server, with idle and abandoned ones easy to spot.
RFC connection and authorization probes, so a broken destination surfaces before the job that depends on it does.
Tablespace and HANA volume pressure with fill trends, in the same view as everything else.
Dialog response-time and workload trends over time, broken down by task type, top transaction and top user, rather than 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, leaving 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
Common questions
Does this replace SAPGUI?
How does Farrenio reach my SAP systems?
Which transactions are covered?
Can a service desk triage without production access?
Is this only for one SAP system?
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 and give you a straight answer on fit.