Built for people who understand SAP operations.
Install. Connect. Monitor.
Monitor SAP landscapes from one operations view. See the signals Basis already trusts, open work from repeated samples, and investigate with the evidence still attached. Designed for SAP Basis teams — not a generic observability platform.
The Interactive Demo is available now. Access to real SAP environments is opening in stages.
Production incident
S4-PROD
Dialog capacity is exhausted while the SAP instance remains reachable.
Investigate incidentWhat it means
SAP monitoring is watching application and system health across a landscape so a Basis team can see an operational problem while it is still a problem — not after users are already calling.
In practice that means instance availability, work-process pressure, background-job queues, dumps, enqueue and update backlogs, ICM, HANA process state, and the host underneath. The point is not to collect every possible metric. It is to notice the signals that change how you run the day, then keep enough context to investigate them.
BasisPilot is an SAP operations monitoring and investigation platform for teams that already operate SAP ECC, S/4HANA, HANA, NetWeaver, PO/PI, BW, and related landscapes. It is not an SAP product and is not affiliated with SAP.
Operations view
SAP dashboard monitoring should answer the questions a Basis lead asks at the start of a shift: which systems are healthy, which signals are stale, what is open, and what evidence sits under the problem.
The Command Center is that picture: landscape health, open work, and a path into the incident. Walk the same sequence in the interactive demo — fictional systems, no live SAP.
Production incident
S4-PROD
Dialog capacity is exhausted while the SAP instance remains reachable.
Investigate incidentSignals
A customer-side connector posts observations from enable-listed collectors. Collectors start off until you turn them on. This is the current set — not a planned roadmap.
Work-process overview (SM50-like), batch-queue pressure (SM37-like dispatcher view, not TBTCO history), syslog severity counts (SM21-like), enqueue pressure, update dispatch, ICM, and short-dump counts (ST22-like — counts, not dump text).
HANA instance and process health through SAPControl: instance colors and HDB process state. The connector does not open a SQL session or pull a HANA alert inventory.
Filesystem usage plus host CPU, memory, swap, load, and related process counts from the connector host. Useful when SAP looks healthy and the box is not.
Instance reachability via SAPControl GetProcessList. Landscape health rolls those samples into a picture of which systems need attention.
A single noisy sample is not the product. The API opens an incident when the same fingerprint stays warning or critical.
Related observations and sibling incidents stay on the problem. Investigation writes a stored evidence pack and a templated explanation with seeded Notes/SOP citations.
Job history via SM37 XBP / TBTCO and SM13 VBHDR update history are not collected yet. Live SAP Notes download is also later. For HANA instance and process health specifically, see SAP HANA monitoring. If you are comparing platforms, use the SAP monitoring-tool evaluation guide. For rollout and operating-model questions, see monitoring multiple SAP landscapes, the monitoring coverage model, and what happens after an alert. For a manual evidence checklist before repeating a canceled run, see the canceled background job guide.
Differentiation
A red tile is not the finish line. BasisPilot is built so a signal can become an incident, then an evidence pack, then a readable explanation — without switching through six transactions to reconstruct what happened.
Investigate builds a stored evidence pack from what was already ingested. It does not call back into live SAP. Explanation is templated from that pack. Catalog citations are seeded Notes and SOPs, not a live Notes download. Optional AI investigation is off by default and is not part of the public demo.
Production landscapes
Production SAP monitoring is about visibility you can act on: see the landscape, notice a repeated signal early, and keep incident context with the evidence instead of rebuilding it under pressure.
BasisPilot does not claim to prevent outages or guarantee uptime. What it does is keep the operational picture in one place so investigation starts from stored samples — availability, work processes, jobs, dumps, HANA process state, host pressure — rather than from a blank SM50 at 2 a.m.
Humans still approve advisory next steps. Real SAP change stays fail-closed unless you explicitly turn it on. That is the production posture: observe first, understand the incident, then decide.
For Basis teams
You already know where to look: SM50, SM37, SM21, ST22, SM12, SM13, SMICM, SAPControl, HANA process list, and the host. BasisPilot does not replace those transactions. It watches the same class of signals on a schedule and brings the repeats to you with context.
The daily user is the Basis or SAP operations engineer. Managed service providers who run multiple customer landscapes are a secondary audience — same connector motion, not a custom project per account. Buyers may be Basis leads or operations managers; the person who lives in the dashboard is still Basis.
Use it as the morning picture and the incident workspace. Keep Solution Manager, Cloud ALM, or your existing platform where they already earn their keep. For the Basis-specific workflow, see SAP Basis monitoring.
Why BasisPilot
How it works
A Go agent registers and heartbeats over outbound HTTPS. SAP RFC and SAPControl credentials stay in that process. They are not posted to the API.
Configured identity, then heartbeat. Optional read-only discovery can fill fields from RFC_SYSTEM_INFO on an SDK-enabled agent. No RFC password in the API.
Enable-listed collectors post observations. Repeated warning or critical samples become incidents you can investigate.
See how BasisPilot works · Review the security model · Explore the interactive demo · Read the DIA work process triage guide
Questions
Direct answers from the current product — not a planned brochure.
SAP monitoring is watching system and landscape health — availability, work processes, jobs, dumps, HANA pressure, and related signals — so Basis teams can see operational problems early and investigate them with evidence.
A useful SAP monitoring dashboard shows landscape health, the signals that matter, open incidents, and the evidence around a problem in one place — not six transactions and a pile of disconnected alerts.
A customer-side connector posts observations from enable-listed collectors: availability, work processes, jobs, syslog, enqueue, updates, ICM, HANA, dumps, plus host filesystem and OS signals. Repeated warning or critical samples become incidents.
Yes. The daily user is the Basis or SAP operations engineer. Managed service providers who run multiple customer landscapes are a secondary audience.
BasisPilot is designed for SAP ECC, S/4HANA, HANA, NetWeaver, PO/PI, BW, and related landscapes. It is not an SAP product and is not affiliated with SAP.
No. The intended path is install a connector, connect a system, and watch the first signals — not a months-long tool selection and dashboard programme.
A Go agent runs on a host that can see SAP and posts outbound HTTPS. SAP RFC and SAPControl credentials stay on that host. They are not sent to the BasisPilot API.
Yes. Ingest opens incidents from repeated signals, correlates related rows, stores an evidence pack, and writes a templated explanation with seeded Notes/SOP citations. Optional AI investigation is off by default and is not part of the public demo.
No. BasisPilot does not replace SAP Cloud ALM, SAP Focused Run, SAP Solution Manager, or a full observability suite. It is a focused operations path for landscape health and investigation.
Yes. The Interactive Demo walks a fictional SAP landscape. It does not connect to live SAP systems and it does not call an AI API.
Explore a fictional landscape and review the security model. Nothing on this site connects to your SAP systems.
