HANA instance reachability
SAPControl GetSystemInstanceList: probe ok, HDB instance rows, and green / yellow / red instance colors. That is the current HANA availability picture.
Built for people who understand SAP operations.
SAP HANA monitoring without another monitoring project
Install. Connect. Monitor.
SAP Basis HANA monitoring is instance and process health in the same landscape as the applications that sit on it. BasisPilot brings those HANA-related operational signals into a focused view, then moves from detection toward evidence and investigation — not another platform programme, and not a SQL warehouse.
Trial is a placeholder. Signup, verification, and entitlements are not implemented yet. The Interactive Demo is fictional and does not call an AI API.
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 HANA monitoring?
Operationally, SAP HANA monitoring means knowing whether the HANA instances that back your landscape are reachable, which are green versus yellow or red, and whether HDB processes are up — then relating that to the SAP applications that will feel it first.
Basis teams do not monitor HANA as a generic database hobby. They monitor it because S/4HANA, BW, and related systems stall when HANA is not healthy: DIA fills, jobs queue, dumps climb. A focused operations view keeps HANA health next to those application signals instead of sending you to a separate cockpit for every color change.
That is SAP HANA system monitoring as Basis runs it: landscape health first, then evidence when a signal repeats. It is not HANA Studio, not expensive-statement history, and not a SQL performance lab. BasisPilot is designed for SAP HANA environments and is not an SAP product, certification, or partnership.
Operations view
SAP HANA monitoring dashboard
A useful SAP HANA monitoring dashboard for Basis is the landscape picture: which HANA SIDs need attention, what color the instance last reported, and whether an incident already holds the evidence.
Command Center rolls HANA-PROD into the same health view as S/4, PO, and BW. Walk that fictional landscape in the interactive demo — including HANA-PROD in a degraded state. No live HANA connection.
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 →
Implemented today
What BasisPilot monitors for HANA
The sap_hana collector is SAPControl SOAP only. Enable it on the connector. This is the current set — not a HANA SQL roadmap presented as shipped.
HDB process state
SAPControl GetProcessList for hdb* processes. The collector reports how many HDB services are GREEN — not a full HANA cockpit process studio.
Host under HANA
Filesystem usage plus host CPU, memory, swap, and load from the connector host. Useful when the instance color is yellow and the box is under pressure. These are OS signals, not HANA SQL memory or CPU.
Related SAP application signals
Work processes, jobs, dumps, enqueue, updates, and ICM on the ABAP side of the same landscape. A HANA-yellow SID often shows up next to DIA or BTC pressure — correlation, not a guess.
Incidents from repeated samples
A single noisy color is not the product. The API opens an incident when the same HANA fingerprint stays warning or critical.
Stored evidence
Related observations stay on the incident. Investigation writes a bounded evidence pack and a templated explanation with seeded Notes/SOP citations.
Not collected: HANA SQL, expensive statements, alert inventory, table or index statistics, session lists, backups, replication, or in-database memory/CPU history. Host CPU and memory are OS samples from the connector host, not HANA database monitoring of SQL engine internals.
Don't just detect a problem. Understand it.
From signal to investigation
A yellow tile is a condition, not an explanation. SAP HANA health monitoring in BasisPilot is meant to carry the sample through incident, bounded evidence, and a readable investigation — so you are not reconstructing GetProcessList from scratch.
Investigate uses ingested observations. It does not query live HANA SQL. Optional AI investigation is off by default and is not part of the public demo.
Production landscapes
SAP HANA in production operations
SAP HANA production monitoring for Basis is usually one HANA SID (or a few) sitting under S/4, BW, or sidecar tenants. The operational question is whether that instance is reachable and whether HDB processes are GREEN — then what the application layer is doing at the same time.
When HANA is yellow, you still look at host pressure, DIA, BTC, and dumps. BasisPilot keeps those layers in one incident trail. It does not claim to prevent outages, guarantee uptime, or replace HANA cockpit for engine internals.
SAP HANA performance monitoring, in this product, means operational process and instance health plus correlated host samples — not statement latency, MVCC, or savepoint history. Those SQL collectors are not implemented.
Daily motion
How this fits a Basis workflow
You keep sapstartsrv, HANA cockpit, and ST04 where they already earn their keep. This loop is the operations picture around instance color and HDB process state.
01 MONITOR
Monitor
Watch HANA instance colors and HDB GREEN counts in landscape health.
02 IDENTIFY
Identify
A repeated yellow/red or process fingerprint becomes an incident.
03 INSPECT
Inspect
Open the HANA SID next to the ABAP systems that depend on it.
04 EVIDENCE
Evidence
Review stored SAPControl samples and correlated host rows.
05 INVESTIGATE
Investigate
Read the templated explanation and seeded catalog citations.
06 ACT
Act
A human approves the next advisory step. Live HANA change stays fail-closed.
BasisPilot does not automatically start, restart, or change HANA in production. Advisory proposals need a person. Execute stays refused unless flags are on.
Why BasisPilot
Traditional monitoring project vs BasisPilot
Traditional monitoring project
- A separate HANA stack beside the SAP operations picture
- Multiple tools, agents, and dashboard programmes before the first useful view
- Fragmented signals — cockpit here, SM* there, host somewhere else
- Investigation means jumping sources to rebuild what fired
BasisPilot
- Focused SAP operations view that includes HANA instance and process health
- Connector-based architecture: outbound HTTPS, credentials stay on the host
- Centralized landscape visibility with HANA SIDs next to ABAP systems
- Evidence-driven investigation on the incident, around existing Basis workflows
See how BasisPilot works · Review the security model · View pricing
Questions
SAP HANA monitoring FAQ
Direct answers from the current product — not a planned HANA SQL brochure.
What is SAP HANA monitoring?
SAP HANA monitoring is watching whether HANA instances and HDB processes are reachable and healthy, then relating that state to the SAP applications and hosts that depend on them — so a Basis team can investigate with evidence, not a disconnected console.
Why should SAP Basis teams monitor HANA?
ABAP work processes, jobs, and dumps often sit on HANA. If the HANA instance is yellow or an HDB process is not GREEN, the application picture is incomplete. Basis teams monitor HANA as part of the landscape, not as a separate database project.
What does an SAP HANA monitoring tool do?
In BasisPilot, the sap_hana collector uses SAPControl SOAP: instance list (probe, instance count, green/yellow/red) and HDB process GREEN counts. Repeated warning or critical samples become incidents with stored evidence. It does not open a SQL session.
Can BasisPilot monitor SAP HANA systems?
Yes. Enable the sap_hana collector on a connector host that can reach HANA sapstartsrv. HANA SIDs appear in the same landscape health picture as ECC, S/4HANA, PO/PI, and BW. BasisPilot is not an SAP product and is not affiliated with SAP.
Does BasisPilot require installing software inside HANA?
No. A Go connector runs on a host that can see SAP. It talks to HANA through SAPControl HTTP/SOAP. Nothing is installed inside the HANA database, and no HANA SQL client is used.
How does BasisPilot connect to SAP environments?
The connector registers and heartbeats over outbound HTTPS. SAP RFC and SAPControl credentials — including HANA sapstartsrv details — stay on that host. They are not sent to the BasisPilot API.
Does BasisPilot replace SAP Cloud ALM or Focused Run?
No. BasisPilot does not replace SAP Cloud ALM, SAP Focused Run, SAP Solution Manager, HANA cockpit, or a full observability suite. It is a focused SAP operations path for landscape health and investigation.
Can BasisPilot investigate HANA-related incidents?
Yes. Repeated HANA instance or process samples open an incident. Related host and SAP application rows can be correlated. Investigation writes a stored evidence pack and a templated explanation with seeded Notes/SOP citations. Optional AI investigation is off by default and is not part of the public demo.
Does BasisPilot automatically change SAP production systems?
No. Advisory next steps need a person. Live SAP or HANA change stays fail-closed unless you explicitly turn flags on. Automated production change is not the default path.
Can I explore BasisPilot before connecting my SAP environment?
Yes. The Interactive Demo walks a fictional landscape that includes HANA-PROD. It does not connect to live SAP or HANA systems and it does not call an AI API.
See BasisPilot with your SAP environment
Walk a fictional landscape that includes HANA-PROD. Nothing on this site connects to your HANA systems. Trial signup is planned and not live.
Read the resources · Start 14-day trial · Book a demo · SAP monitoring · SAP Basis monitoring