Infrastructure
Storage used by the organization against the contracted storage, what takes the space, and how far back each kind of data goes.
Infrastructure shows the capacity the organization uses on Integration Mapper.
Storage
Section titled “Storage”The size of each environment’s tables in the database, indexes included, every environment together. Backups and the server itself are not part of it.
| Figure | Meaning |
|---|---|
| In use now | The size right now |
| Contracted | The storage in the contract, and the share in use |
| Highest this month | Storage is billed on the highest size reached in the month, recorded every 15 minutes |
| Above contract | How much the highest size passed the contract |
Going over the contracted storage only raises a warning; nothing stops.
The table splits the size by kind of data and environment. Audit revisions have no retention yet: every captured design version stays, so it keeps growing.
Integration Mapper runs on shared infrastructure, so processor and memory are not split per organization and are not shown.
Retention
Section titled “Retention”For each environment, the oldest record still kept and the retention set for it:
| Data | Retention set in |
|---|---|
| Monitored messages | Settings → Monitoring → General |
| ExceptionSubprocess details | Settings → Monitoring → General |
| Trace captures | Settings → Monitoring → Trace & Payload |
| Audit revisions | No expiry |
- Each environment deletes what is older than its retention at every Monitoring sync, so the oldest date moves forward on its own.
- days of data shows how far back the data really goes. Monitored messages and ExceptionSubprocess details only reach as far back as the first load: SAP keeps message logs for 30 days.
Storage by month
Section titled “Storage by month”The highest size of each month, with the storage contracted then.