Alerts if a Blocked Transaction wait time is high.
Alerts if the SAP HANA database becomes unreachable.
Alerts if an Expensive Statement has high CPU time, memory usage, or duration.
Alerts if CPU utilization on the host is high.
Alerts if the memory used by an instance as a percentage of its allocation limit is too high.
Alerts if the physical memory usage is too high.
Publishes SAP HANA native alerts to Foglight.
Alerts if the service's usage of its effective memory allocation is too high.
Alerts if a SQL plan's resource utilization is high.
Alerts if the SAP HANA System becomes unreachable through the system database.
Alerts if the percentage of disk used on a volume is too high.
Identifies internal statistics server problem.
Determines what percentage of total physical memory available on the host is used. All processes consuming memory are considered, including non-SAP HANA processes.
Determines what percentage of each disk containing data, log, and trace files is used. This includes space used by non-SAP HANA files.
Identifies inactive services.
Identifies services that have restarted since the last time the check was performed.
Determines the percentage CPU idle time on the host and whether or not CPU resources are running low.
Determines whether or not the 'active' parameter in the 'mergedog' section of the system configuration file(s) is 'yes.' mergedog is the system process that periodically checks column tables to determine whether or not a delta merge operation should be executed.
Determines what percentage of allocated shared memory is being used by the name server on a host.
Determines whether the 'lock_wait_timeout' parameter in the 'transaction' section of the indexserver.ini file is between 100,000 and 7,200,000.
Determines the number of records in non-partitioned column-store tables. Current table size may not be critical. Partitioning need only be considered if tables are expected to grow rapidly (a non-partitioned table cannot contain more than 2,147,483,648 (2 billion) rows).
Determines the growth rate of non-partitioned columns tables.
Identifies internal database events.
Determines whether or not there have been any alerts since the last check and if so, sends a summary email to specified recipients.
Determines whether or not there have been any medium and high priority alerts since the last check and if so, sends a summary e-mail to specified recipients.
Determines whether or not there have been any high priority alerts since the last check and if so, sends a summary e-mail to specified recipients.
Determines what percentage of the maximum number of permitted SQL connections are open. The maximum number of permitted connections is configured in the "session" section of the indexserver.ini file.
Identifies volumes that are not assigned a service.
Determines the number of records in the partitions of column-store tables. A table partition cannot contain more than 2,147,483,648 (2 billion) rows.
Determines how long ago the last savepoint was defined, that is, how long ago a complete, consistent image of the database was persisted to disk.
Determines the size of the delta storage of column tables.
Determines whether or not the disks to which data and log files are written are full. A disk-full event causes your database to stop and must be resolved.
Determines how many days until your license expires. Once your license expires, you can no longer use the system, except to install a new license.
Determines whether or not the database is running in log mode "legacy." Log mode "legacy" does not support point-in-recovery and is not recommended for production systems.
Determines whether or not the database is running in log mode "overwrite". Log mode "overwrite" does not support point-in-recovery (only recovery to a data backup) and is not recommended for production systems.
Determines whether or not all volumes are available.
Determines whether or not a data backup exists. Without a data backup, your database cannot be recovered.
Determines whether or not the most recent data backup was successful.
Determines the age of the most recent successful data backup.
Determines whether or not the most recent log backups for services and volumes were successful.
Identifies long-running SQL statements.
Determines what percentage of the effective allocation limit is being consumed by individual columnstore tables as a whole (that is, the cumulative size of all of a table's columns and internal structures)
Determines whether or not there is a problem with the activation of an in-memory DataStore object.
Identifies long-running/idling cursors. The threshold is based on M_INIFILE_CONTENTS.VALUE where KEY = "idle_cursor_lifetime".
Determines what percentage of its effective allocation limit a service is using.
Determines what percentage of licensed memory is used.
Determines what percentage of the effective allocation limit is being consumed by the main storage of individual column-store tables.
Identifies new runtime dump files (*rtedump*) have been generated in the trace directory of the system. These contain information about, for example, build, loaded modules, running threads, CPU, and so on.
Identifies long-running serializable transactions.
Identifies long-running uncommitted write transactions.
Identifies long-running blocking situations.
Determines the number of diagnosis files written by the system (excluding zip-files). An unusually large number of files can indicate a problem with the database (for example, a problem with trace file rotation or a high number of crashes).
Identifies large diagnosis files. Unusually large files can indicate a problem with the database.
Identifies new crashdump files that have been generated in the trace directory of the system.
Identifies new pagedump files that have been generated in the trace directory of the system.
Identifies long-running savepoint operations.
Determines how many columns in columnstore tables have been unloaded from memory. This can indicate performance issues.
Python trace activity
Determines whether or not the python trace is active and for how long. The python trace affects system performance.
Determines if the instance secure store in the file system (SSFS) of your SAP HANA system is accessible to the database.
Determines whether or not the plan cache is too small.
Determines the percentage of transactions that are blocked.
Identifies a bad trigger asynchronous read ratio. This means that asynchronous reads are blocking and behave almost like synchronous reads. This might have negative impact on SAP HANA I/O performance in certain scenarios.
Identifies a bad trigger asynchronous write ratio. This means that asynchronous writes are blocking and behave almost like synchronous writes. This might have negative impact on SAP HANA I/O performance in certain scenarios.
Identifies database users whose password is due to expire in line with the configured password policy. If the password expires, the user will be locked. If the user in question is a technical user, this may impact application availability. It is recommended that you disable the password lifetime check of technical users so that their password never expires (ALTER USER DISABLE PASSWORD LIFETIME).
Determines if the internal support role (SAP_INTERNAL_HANA_SUPPORT) is currently granted to any database users.
Determines what percentage of the effective memory allocation limit is being consumed by the database table used for table-based audit logging. If this table grows too large, the availability of the database could be impacted.
Determines whether or not the most recent log backup terminates in the given time.
Determines whether or not the period, during which the database is prepared for a storage snapshot, exceeds a given threshold.
Determines the growth rate of rowstore tables
Determines the current memory size of a row store used by a service
Determines whether automatic log backup is enabled.
Verifies the consistency of schemas and tables in internal system components (for example, the repository) after a system upgrade.
Determines the overflow ratio of the rowstore version space.
Determines the overflow ratio of the metadata version space.
Determines whether the rowstore version chain is too long.
Identifies discrepancies between the server times of hosts in a scale-out system.
Determines the total used disk space of the database. All data, logs, traces and backups are considered.
Identifies closed connections between the primary system and a secondary system. If connections are closed, the primary system is no longer being replicated.
Identifies configuration parameters that do not have the same value on the primary system and a secondary system. Most configuration parameters should have the same value on both systems because the secondary system has to take over in the event of a disaster.
Monitors error messages related to table replication.
Determines how much memory is occupied by cached view
Compares SAP HANA internal timezone conversion with Operating System timezone conversion.
Identifies the number of errors and affected tables detected by _SYS_STATISTICS.Collector_Global_Table_Consistency.
Determines whether the master key of the instance secure store in the file system (SSFS) of your SAP HANA system has been changed. If the SSFS master key is not changed after installation, it cannot be guaranteed that the initial key is unique.
Determines whether the master key of the secure store in the file system (SSFS) of your system's internal public key infrastructure (system PKI) has been changed. If the SSFS master key is not changed after installation, it cannot be guaranteed that the initial key is unique.
Determines whether the ports used by SAP HANA for internal communication are securely configured. If the "listeninterface" property in the "communication" section of the global.ini file does not have the value ".local" for single-host systems and ".all" or ".global" for multiple-host systems, internal communication channels are externally exploitable.
Determines if support privileges for the SAP HANA Deployment Infrastructure (DI) are currently granted to any database users or roles.
Determines if the delta merge of a table was executed successfully or not.
Determines if there is any volume file missing.
Determines if the system was not installed/updated with the SAP HANA Database Lifecycle Manager (HDBLCM).
Determines whether or not the plan cache hit ratio is too low.
Not all services that persist data could be reached the last time the root key change of the data volume encryption service was changed. As a result, at least one service is running with an old root key.
Determines how many days until your streaming license expires. Once your license expires, you can no longer start streaming projects.
System Replication secondary site has a higher log replay backlog than expected.
Determine the Data Quality reference data expiration dates.
Identifies all long-running tasks.
Determines if the container import feature of the SAP HANA Deployment Infrastructure (DI) is enabled and if import privileges for SAP HANA DI containers are currently granted to any database users or roles.
Determines whether or not the lob garbage collection is activated.
Checks the installed HANA version.
Determines if the operating system of the SAP HANA Database hosts is supported.
Determines if SQL access has been enabled for any SAP HANA DI technical users. SAP HANA DI technical users are either users whose names start with '_SYS_DI' or SAP HANA DI container technical users (, #DI, #OO).
Determines whether or not a system database backup exists. Without a system database backup, your system cannot be recovered.
Determines if any deprecated features were used in the last interval.
System Replication secondary site has a higher log shipping backlog than expected.
The check monitors the number of open transactions per service
Checks if local in-memory buffer in ASYNC replication mode runs full
Determines if an inconsistent fallback snapshot exist.
Determines if a snapshot exists for an extended period of time.
If the backup history is broken, the log_mode is internally set to overwrite; it is not ensured that the service is fully recoverable via backup.
Identifies the number of errors and affected objects detected by _SYS_STATISTICS.Collector_Global_Catalog_Consistency.
Check whether the status of replication log is disabled.
Determines the number of records in non-partitioned column-store tables (only include tables are checked). Current table size may not be critical. Partitioning need only be considered if tables are expected to grow rapidly (a non-partitioned table cannot contain more than 2,147,483,648 (2 billion) rows).
Determines the number of records in the partitions of column-store tables (only include tables are checked). A table partition cannot contain more than 2,147,483,648 (2 billion) rows.
Checks if any user is enabled for LDAP Authentication and SSL is off.
Checks for the dbspace size usage.
Determines whether or not all dbspaces are available.
Determines whether or not all dbspace files are available.
Identifies inactive Streaming applications.
Identifies inactive Streaming project managed adapters.
Determines what percentage of total physical memory available on the host is used for the streaming project.
Determines the percentage CPU usage for a streaming project on the host and therefore whether or not CPU resources are running out.
Identify the large publishers of streaming project. Make sure that they will not break the streaming project.
Identify the large subscribers of streaming project. Make sure that they will not break the streaming project.
Identify which subscriber of streaming project has low throughput measured in rows per second.
Identify which subscriber of streaming project has transaction throughput measured in transactions per second.
Identify which publisher of streaming project has low throughput measured in rows per second.
Identify which publisher of streaming project has transaction throughput measured in transactions per second.
Identify which project managed adapter has much rows with error.
Identify which project managed adapter has high latency.
Identify which stream of streaming project has large queue.
Identify which stream of streaming project has large store.
Determines how many minutes the agent has been inactive.
Determines what percentage of total memory available to agent is used.
Checks for recent exceptions in remote subscriptions and remote sources.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center