Install. Connect. Monitor.

1. Install the connector

A customer-side Go agent runs on a host that can see SAP. It registers and heartbeats over outbound HTTP. SAP RFC and SAPControl credentials stay in that process or in local host files. They are not posted to the API.

2. Connect a system

You register a SID with configured metadata. Optional read-only discovery can fill identity from RFC_SYSTEM_INFO on an SDK-enabled agent. The dashboard labels configured vs discovered fields.

3. Monitor

Enable-listed collectors (filesystem, OS, SAPControl availability, work processes, jobs, syslog, enqueue, updates, ICM, HANA, dumps) post observations. The API opens incidents when the same fingerprint stays warning or critical.

Then understand it

Investigate builds a stored evidence pack. Explanation is templated from that pack. Catalog citations are seeded Notes/SOPs. Optional AI investigation is off by default and is not part of the public demo.