Use case · Consultancies and MSPs
Several customers, each in its own installation
If you run SAP systems for several companies, SUPtime keeps each one's data apart by design: one installation per customer, not a filter over a shared database.
Isolation
Why one installation per customer
One database for several customers leaves the separation to every single query. Here the separation is the boundary of the installation.
Data apart by design
A customer's credentials, alerts and history live only in their installation.
A small server
A Linux server with 2 vCPU and 4 GB of RAM covers about ten systems.
No agents
On the customer's systems you only need a read-only RFC user, plus an optional HANA user.
Operations
Organize the systems, alert the right people
Landscapes
They group systems and give alert rules their scope.
Rules on three levels
For one system, a landscape or all of them, with recovery notifications and a cooldown.
Emails that say whose system it is
Landscape and customer, ABAP and database SIDs, release and kernel, rule and first occurrences.
Roles
View-only access for people who only need to look.
Evidence
What you can hand to your customer
NIS2/DORA report
A Word document with a signature line, regulatory references, raw evidence and the run hash.
Audit trail
Logons, system changes and credential access in a hash-chained log.
Export
CSV and Excel of logs, jobs, database load and a full report.
Declared limits
What it does not do
Better to know before you offer it to your customers.
- A single dashboard across customers: each one has its own installation.
- White-labeling and automated SLA reports.
- Integrations with ITSM ticketing systems.
- Alert emails in Italian: they are in English.
Running SAP systems for several customers?
Let's talk about installing it for each of them and what their systems need.