🔍 Read the full analysis: How A Capacity Ledger Monitors SAP With A Read-Only Integration on Rymvard
Get monitors, keyboards and dev gear delivered free — and shop member deals
- Fast, free delivery on millions of items
- Access to Prime Big Deal Days deals on October 6–7
- Prime Video, Amazon Music and more included
TL;DR
Rymvard says its early-access capacity ledger gathers SAP system and HANA monitoring data through read-only interfaces, with fixed operations and query limits. The company tested the integration against a simulator modeling 200 hosts, not a customer SAP landscape.
Rymvard says its early-access capacity ledger monitors SAP landscapes through read-only connections, using a limited set of Host Agent operations and HANA monitoring queries rather than writing to production systems. The company says the integration currently runs against a simulator representing 200 hosts; it has not presented the screens or scenarios as results from a customer deployment.
A small collector at each site communicates with the SAP Host Agent over HTTPS and is restricted to four operations: ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem. Rymvard says the collector refuses other operations. A separate connection reads HANA monitoring views using a fixed list of six SELECT queries, with a monitoring user over TLS. Queries are limited to 60 seconds per system, and the integration handles no more than eight systems at a time.
The ledger can also read landscape information from SAP Focused Run, ServiceNow, SAP Solution Manager through its System Landscape Directory, and SAP LaMa, using read-only interfaces. Rymvard says it does not write to SAP. It matches customers and environments from available evidence: instances are associated with the system running on the same host, while systems that have not been declared are recorded as development systems with a confidence score of 0.5, rather than assigned to a customer by inference.
Rymvard says a value based only on a guess cannot replace a declared value, and an instance no longer listed by the SAP Host Agent on its host is removed from the ledger. Detailed records remain in the country where they were measured, while customer names are visible only to planners and administrators. The company describes the product as early access; prices are not published and are agreed with early-access partners.
Infrastructure Watch · Early Access
How a Capacity Ledger Monitors SAP With a Read-Only Integration
Rymvard describes a limited, observational connection to SAP systems and HANA monitoring data. Its disclosed test environment is a simulator modeling 200 hosts, not a customer landscape.
01 / Connection design
A bounded path into the landscape
The collector is described as a site-level component that gathers monitoring signals through named read interfaces. Rymvard says it does not write to SAP.
Site collector
A small collector runs at each site and connects over HTTPS.
Host Agent
Only ListInstances, ListDatabases, GetDatabaseStatus and GetComputerSystem are permitted.
HANA monitoring
A TLS monitoring user runs a fixed set of six SELECT queries.
Capacity ledger
Records are matched to systems and environments using available evidence.
02 / Guardrails and evidence
Limits are stated; field performance is not
The design describes controls and test scope. It does not establish performance or safety outcomes in a live customer estate.
Named reads only
Four Host Agent operations are allowlisted. The HANA side uses six fixed monitoring queries, with a 60-second limit per system.
Up to eight systems
The stated integration handles no more than eight systems at a time. The company has not published production performance results.
Simulator, 200 hosts
The simulator models Host Agent and HANA monitoring responses. It is a development test, not a reported customer deployment.
Illustrative product screens, an example estate, the simulator scale, and the stated integration boundaries.
Live customer installation, measured outcomes, participating customer count, and independent security review.
03 / Record matching
Uncertainty stays visible
Rymvard says the ledger uses declarations and observed host relationships to avoid presenting guesses as established customer data.
Evidence before assignment
Instances are associated with the system running on the same host. Undeclared systems are recorded as development systems with a confidence score of 0.5, rather than assigned to a customer by inference.
Declared values take precedence
The company says a value based only on a guess cannot replace a declared value. An instance no longer listed by the SAP Host Agent on its host is removed from the ledger.
Detailed records are said to remain in the country where they were measured; supported countries and retention periods are not specified.
Customer names are described as visible only to planners and administrators. Independent verification is not provided in the available description.
04 / Company statements
Read-only by design, according to Rymvard
These statements describe the product as presented by the company. They are not independent verification or live customer evidence.
“Nothing is ever written to SAP.”— Rymvard
The company says its integration is observational: a short allowlist of Host Agent operations, fixed HANA SELECT queries, and read-only interfaces to landscape sources. The disclosed simulator test cannot establish how those boundaries behave across customer configurations and operating practices.
05 / Open questions
What an evaluator still needs to know
Rymvard says the product is running and available through early access. Pricing is agreed with partners; no broader release schedule is announced.
Does Rymvard write to SAP?
Rymvard says no. The described Host Agent collector is restricted to four read operations, and HANA access uses six fixed SELECT queries.
Was the integration tested with customers?
The company describes testing against a simulator modeling 200 hosts. It has not reported a customer deployment or live estate results.
How does it handle unidentified systems?
Undeclared systems are recorded as development systems at 0.5 confidence. The company says guessed values do not replace declared ones.
What is known about availability?
The product is in early access. Customers have not been named, public pricing is unavailable, and a general availability date has not been specified.
Read-Only Design Limits Production Changes
For organizations considering infrastructure monitoring, the stated design addresses a practical concern: whether an external tool can change data or settings in a production SAP environment. Limiting access to named read operations and a short set of monitoring queries is intended to keep the integration observational. Rymvard says the collector refuses unlisted Host Agent operations and that the product does not write to SAP.
The rules for uncertain records also matter to capacity planning. If systems are not declared, the ledger records them as development systems at 0.5 confidence rather than guessing a customer assignment. This approach makes the uncertainty visible instead of presenting an inferred relationship as established data. Country-level storage of detailed records and restricted visibility of customer names may also be relevant to organizations managing sensitive infrastructure information, though the available description does not provide independent verification of those controls.
These details describe the integration’s intended boundaries, not evidence of performance or safety in a live customer estate. The simulator test provides a development and test setting, but cannot establish how the product behaves across the variety of configurations, access controls and operational practices found in customer SAP landscapes.
portable monitor for SAP system monitoring
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Simulator Test, Not Customer Deployment
Rymvard describes itself as a capacity ledger for data centers and says it has no SAP system of its own. It therefore built and tested the SAP connection against a simulator designed to respond like the SAP Host Agent and HANA monitoring views. The modeled landscape contains 200 hosts. This is the testing environment disclosed by the company, not a reported customer estate.
The company says the product is running and that the screens shown come from the product using an illustrative example estate. It also says the scenarios are illustrative and do not imply a particular customer, site or outcome. Rymvard has not named an early-access customer, reported a deployment result, or published pricing. The current announcement is consequently about the connection design and product status, rather than a verified customer implementation or measured business outcome.
““Nothing is ever written to SAP.””
— Rymvard
enterprise network monitoring tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Live Estate Validation Remains Unreported
Rymvard has not disclosed whether the integration has been installed in a customer’s live SAP environment, or provided results from such an installation. The simulator’s 200-host landscape is the only test scale specified; the company has not reported how the collector performs in production, how many customers are participating in early access, or what outcomes they have recorded.
The described safeguards are company statements. No independent security assessment, detailed documentation of the six HANA queries, or evidence about how the controls have been reviewed is included in the information available. It is also not specified which countries are supported for data storage, how long collected records are retained, or how early-access pricing is set. Those points remain open rather than established product capabilities.
As an affiliate, we earn on qualifying purchases.
Early Access Will Test Customer Use
Rymvard says the product is available through an early-access program, with pricing agreed individually with partners. The company has not announced a schedule for wider release, named participating customers, or specified a next product milestone. A next point of evidence would be a disclosed customer deployment, accompanied by details on the SAP landscape involved and how the integration performed under real operating conditions.
Organizations evaluating the product can request information from Rymvard at contact@rymvard.com. Until customer deployments or further technical documentation are reported, the stated operation limits, data-handling approach and simulator results should be treated as the company’s description of the product, not as independently verified field performance.
Source: Rymvard
As an affiliate, we earn on qualifying purchases.
Key Questions
Does Rymvard write data to SAP?
Rymvard says the integration is read-only and that it does not write to SAP. Its Host Agent collector is restricted to four listed read operations, and its HANA connection uses six fixed SELECT queries.
How was the SAP integration tested?
Rymvard says it tested the connection against a simulator that responds like the SAP Host Agent and HANA monitoring views, modeling a landscape of 200 hosts. The company has not described this as a customer deployment.
Is Rymvard available to customers?
The company says the product is in early access and is running. It has not named customers or published general availability dates. Pricing is agreed with early-access partners rather than listed publicly.
How does the ledger handle systems it cannot identify?
Rymvard says a system that nobody has declared is recorded as a development system with a confidence score of 0.5. It says the ledger does not assign such a system to a customer by guess, and guessed values do not replace declared ones.
Source: Rymvard
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
