Availability and instance health
SAPControl GetProcessList for instance reachability. Landscape health rolls those samples into which systems need attention.
Built for SAP Basis teams.
SAP Basis monitoring without another monitoring project
Install. Connect. Monitor.
SAP Basis operations still mean availability, work processes, jobs, dumps, HANA, and the host. BasisPilot brings those signals, incidents, and evidence into a focused operations workflow — so you can monitor the landscape and understand a problem without standing up another platform programme.
Trial is a placeholder. Signup, verification, and entitlements are not implemented yet.
Command CenterBasisPilot Demo Organization
Open incidents
3
Systems
6
Landscape
Critical
Attention
S4-PROD
No free DIA work processesCritical
S4-PROD · wp_dia_free · sap_work_processS4-PRODCritical2 open · DIA free
HANA-PRODDegraded1 open · HDB yellow
PO-PRODHealthyStable probes
BW-PRODDegraded1 open · BTC queue
QAHealthyStable probes
DEVHealthyStable probes
S4-PROD · DIA free
Same systems as the Interactive DemoOpen demo →
What it means
What is SAP Basis monitoring?
SAP Basis monitoring is how a Basis team keeps a current picture of system health and operational state — not a one-off health check, and not a months-long monitoring implementation.
The work is familiar: is the instance up, are DIA processes free, is the BTC queue climbing, are dumps rising, is enqueue or update dispatch stuck, is ICM unhappy, is HANA yellow, is the host swapping. The problem is that those answers usually live in different transactions, hosts, and tools.
A SAP Basis monitoring tool should bring the repeats to you with enough context to investigate. BasisPilot is built for that Basis operations motion. It is not an SAP product and is not affiliated with SAP.
Signals Basis already owns
What Basis teams need to monitor
SAP Basis system monitoring is useful when it covers the same class of signals you already trust — then opens work from repeated samples instead of every noisy tick.
Work processes and jobs
SM50-like work-process overview and SM37-like batch-queue pressure (dispatcher/BTC rows, not TBTCO job history).
Dumps, syslog, locks, updates, ICM
ST22-like dump counts (not dump text), SM21-like syslog severity counts, enqueue pressure, update dispatch, and ICM. Same class of signals Basis already uses.
HANA process health
HANA instance colors and HDB process state through SAPControl. No SQL session and no HANA alert inventory.
Host underneath SAP
Filesystem usage plus host CPU, memory, swap, load, and process counts from the connector host — when the instance looks fine and the box is not.
Incidents with evidence
Repeated warning or critical fingerprints open an incident. Related observations stay with the problem so investigation does not start from a blank SM50.
Collectors start off until you enable them. Job history via SM37 XBP / TBTCO and SM13 VBHDR update history are not collected yet.
Landscape, not a single SID
From one system to SAP landscape visibility
SAP health monitoring for Basis is rarely one SID. You need to see which systems are healthy, which signals are stale, and where attention belongs — a SAP monitoring dashboard that rolls system samples into landscape health.
Command Center is that picture: landscape rollup, systems needing attention, and a path into the incident. Walk the same fictional landscape in the interactive demo. For the broader monitoring topic, see SAP monitoring.
Command CenterBasisPilot Demo Organization
Open incidents
3
Systems
6
Landscape
Critical
Attention
S4-PROD
No free DIA work processesCritical
S4-PROD · wp_dia_free · sap_work_processS4-PRODCritical2 open · DIA free
HANA-PRODDegraded1 open · HDB yellow
PO-PRODHealthyStable probes
BW-PRODDegraded1 open · BTC queue
QAHealthyStable probes
DEVHealthyStable probes
S4-PROD · DIA free
Same systems as the Interactive DemoOpen demo →
Don't just detect a problem. Understand it.
From signal to investigation
A red tile is not Basis work finished. The product path is signal, then incident, then evidence, then a readable explanation — so the next person can pick it up.
Investigate uses what was already ingested. It does not call back into live SAP. 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 SAP operations
SAP production monitoring for Basis teams
Production SAP monitoring is operational: see the landscape, notice a repeated signal early, and keep incident context attached so investigation does not start under pressure from a blank screen.
BasisPilot does not prevent outages, guarantee uptime, or promise a deployment time. What it does is keep the Basis picture in one place — availability, work processes, jobs, dumps, HANA process state, host pressure — so you can investigate from stored samples. For the HANA-specific operations view, see SAP HANA monitoring.
Humans still approve advisory next steps. Governed live change is off unless you explicitly turn it on. Observe first. Understand the incident. Then decide.
Daily motion
How BasisPilot fits a Basis workflow
You keep SM50, SM37, SM21, ST22, SM12, SM13, SMICM, SAPControl, and the host. This is the operations loop around those signals — not a replacement for the transactions.
01 MONITOR
Monitor
Watch landscape health and the collectors you enabled.
02 IDENTIFY
Identify
A repeated warning or critical fingerprint becomes an incident.
03 INSPECT
Inspect
Open the affected SID — not six transactions to reconstruct state.
04 EVIDENCE
Evidence
Review the stored pack: related rows and sibling incidents.
05 INVESTIGATE
Investigate
Read the templated explanation and seeded Notes/SOP citations.
06 ACT
Act
A human approves the next advisory step. Live SAP change stays fail-closed.
Automated live remediation is not the default path. Advisory proposals need a person. Execute against SAP stays refused unless flags are on.
Why BasisPilot
Traditional monitoring project vs BasisPilot
Traditional monitoring project
- Tool selection and dashboard work treated as an infrastructure programme
- Signals split across SM*, host tools, and a separate HANA view
- Alerts without an evidence pack or a next step
- Investigation means switching context to rebuild the story
BasisPilot
- Install a connector. Connect a system. Watch the first signals.
- Focused SAP Basis operations view — not a generic observability suite
- Centralized operational signals from enable-listed collectors
- Evidence-driven investigation on the incident. Credentials stay on the host.
See how BasisPilot works · Review the security model · View pricing
Questions
SAP Basis monitoring FAQ
Direct answers from the current product — not a planned brochure.
What is SAP Basis monitoring?
SAP Basis monitoring is watching the operational health of SAP systems — availability, work processes, jobs, dumps, enqueue, updates, ICM, HANA process state, and the host — so a Basis team can see abnormal state and investigate it with evidence.
What should an SAP Basis team monitor?
The signals that change the day: instance reachability, work-process pressure, batch-queue pressure, syslog severity, enqueue and update backlogs, ICM, short-dump counts, HANA instance/process health, and host CPU, memory, swap, and filesystem usage.
Can BasisPilot monitor SAP production systems?
Yes. Production is the intended operations use case: see landscape health, notice a repeated signal, and keep evidence with the incident. BasisPilot does not claim to prevent outages or guarantee uptime.
Which SAP environments does BasisPilot support?
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.
Does BasisPilot require additional monitoring infrastructure?
No extra monitoring platform programme is required. A customer-side connector posts outbound HTTPS from a host that can see SAP. That is still a host to install and collectors to enable — not “zero infrastructure.”
How does the BasisPilot connector work?
A Go agent registers and heartbeats over outbound HTTPS. SAP RFC and SAPControl credentials stay on that host. They are not sent to the BasisPilot API. Enable-listed collectors then post observations.
Does BasisPilot provide investigation and evidence?
Yes. Repeated warning or critical samples open an incident. Related rows are correlated, a stored evidence pack is written, and a templated explanation sits with seeded Notes/SOP citations. Optional AI investigation is off by default and is not part of the public demo.
Does BasisPilot replace SAP Cloud ALM or Focused Run?
No. BasisPilot does not replace SAP Cloud ALM, SAP Focused Run, SAP Solution Manager, or a full observability suite. It is a focused SAP Basis operations path for landscape health and investigation.
Is BasisPilot a SAP Basis monitoring tool?
Yes. The daily user is the Basis or SAP operations engineer. The product brings landscape health, operational signals, incidents, and evidence into one operations workflow — not a generic observability stack.
Is there an interactive demo?
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.
See BasisPilot with your SAP environment
Walk a fictional landscape first. Nothing on this site connects to your SAP systems. Book a conversation when you want to talk about your landscape.
Read the resources · Start 14-day trial · Book a demo · SAP monitoring