Macros are deprecated. Use Interpolations instead.
Even more, you can automatically stop an SAP Instance or an SAP System at the beginning of a Maintenance Window and start it again at the end of it.
Availability Data is recorded even if the monitoring is turned off. And if a system is down during the Maintenance Windows, the downtime is considered as "planned" and does not count for the Service Level Report.
A Maintenance Window can be thought of as a container for Schedules indicating when to turn monitoring off (and on) for a Dynamic Group or a Static Group of Servers, SAP Systems, Databases, and Business Services.
A Schedule is a recurrent or non-recurrent event with a start time and a duration reflecting one or more periods of time. One or more Schedules can be assigned to a Maintenance Window, forming the following relation:
A particular System can be affected by multiple Maintenance Windows, thus Schedules may overlap.
Monitored systems in Avantra run with a Monitor Level, which determines the checks and actions that can be performed on the respective systems.
Monitor Levels have been introduced with the SAP system auto creation feature (see Defining SAP Systems automatically and enable a system to be monitored without credentials, by just applying the adequate checks to it.
Monitor Levels are provided automatically by the corresponding agent monitoring the system. The agent calculates the Monitor Level of a system based on the configuration and system data and then performs the corresponding checks.
There are three Monitor Levels for systems in Avantra:
No credentials have been configured for the system so far.
At least some (or all) required credentials have been configured.
Auth. & Deployed
Credentials have been configured and Avantra modules have been installed on the target system (i.e Avantra Transport has been installed).
Certain Monitoring Parameters allow the definition of exceptions. If you, for instance, define usage thresholds for a tablespace with a Monitoring Parameter, the defined value is valid for all tablespaces of the system. If you want to override this setting on a per-tablespace level you can define the so-called Monitoring Exception Parameter for the particular tablespace.
Monitoring Exception Parameters can be defined in Monitoring Parameter Sets as well.
Monitoring parameters are the mechanism for you to configure how your systems are monitored. They are how you set configuration of how the agent runs, how checks are executed, thresholds for checks (when does a check go critical or warning) and much more. All Monitoring Parameters have a carefully chosen default value. As soon as you add a new system, Avantra uses these defaults. You may change these defaults by defining a parameter and by modifying its values. Monitoring Parameters can be defined for a single system, or for collections of systems using Monitoring Parameter Sets. You can also define your own Custom Monitoring Parameters for use within Custom Checks and automations.