KBI 311478 Argent for Sybase Rules
Version
Argent Advanced Technology 5.1A-1610-A and later
Date
Wednesday, 23 November 2016
Summary
This article explains Argent for Sybase Rules
Technical Background
Sybase ASE (Adaptive Server Enterprise) originally known as Sybase SQL Server and also commonly known as Sybase DB or ASE is a high performing Relational SQL database management system developed by Sybase Corporation which became part of SAP
Sybase ASE is designed to offer extreme performance and it continuously manage extremely large amount of data and thousands of concurrent users
Sybase ASE ensures high running efficiency and yield on a large number of platforms
ASE is supported on UNIX, Linux and Windows platforms
Argent for Sybase provides the complete monitoring of Sybase ASE database servers
Argent for Sybase monitors all the important performance indicators of Sybase ASE database server and notifies through Alerts, if the performance metrics are beyond a given threshold
This helps the DBA to easily pinpoint the issues which affect the overall Sybase ASE database
The following section describes how Argent for Sybase achieves the complete monitoring of Sybase ASE database
- Custom Query Rule
This Rule provides the ability to monitor any SQL Query on a Sybase Database
With this, database administrators can monitor additional performance metrics and monitor custom database tables
- Sybase Capacity Rule
This Rule monitors the active user connections, available user connections, connection utilization percentage, number of connections per second, number of available locks, locks utilization percentage etc
- Sybase Availability Rule
This Rule category contains Rules that monitors Sybase ASE instance availability, engine status (online/offline) and blocked sessions
- Sybase Disk I/O Rule
This Rule monitors disk read/write operations
The category contains Rules to monitor number of logical disk reads, number of logical disk writes, disk reads per second, disk writes per second and disk I/O per second
- Sybase Kernel Rule
This Rule monitors Sybase ASE Engines
Each ASE server running on the machine will have at least one OS process, the data server binary and may have many such running processes
A single server instance consists of at least one data server process
Under Sybase terminology, such data server processes that are cooperating and communicating with each other in shared memory are known as Engines
Sybase Kernel Rule category contains Rules to monitor number of online Engines, Engine utilization etc
- Sybase Data Cache Rule
This Rule monitors important data cache metrics such as cache searches, cache hit rate, cache hits per second and cache space usage
The data cache contains pages from recently accessed objects such as:
- sysobjects, sysindexes and other system tables for each database
- Active log pages for each database
- The higher levels and parts of the lower levels of frequently used indexes
- Recently accessed data pages
- Sybase Procedure Cache Rule
This Rule monitors the procedure cache metrics such as hit rate, size, hits per second and space usage
SAP ASE uses the procedure cache while running stored procedures
If the server finds a copy of a procedure already in the cache, it does not need to read it from the disk
- Sybase Metadata Rule
This Rule monitors the indexes, objects, databases, or partitions in Adaptive Server
- Sybase Database Rule
This Rule monitors the database count, database space usage and transaction log space usage
- Sybase Network Rule
This Rules monitors the data traffic in the Adaptive Server
There are Rules to monitor packets sent per second, packets received per second, data sent per second, data received per second etc
- Sybase Error Logs Rule
This Rule monitors Sybase ASE error logs
Error log contains the details of most recent errors that occurred in Adaptive Server
There is an option to configure the Rule for the occurrence of particular error
- Sybase Active Transaction Rule
This Rule monitors the open transaction in Adaptive Server
There are Rules to monitor the active transaction count and long running transactions
- Sybase Wait Event Rule
This Rule monitors the wait Events occurred in the Adaptive Server
Adaptive Server task management includes four states for a process: running, runnable, sleeping, and blocked
When a process is not running, it is:
- Waiting on the CPU (the “runnable” state)
- Sleeping because of disk or network I/O
- Blocked on a resource (a lock or semaphore)
A wait Event occurs when a server process suspends itself, sleeps, and waits for another Event to wake it
- General Statistics Rule
This category contains the Rules to monitor SQL query response time, slow running queries, deadlocks, query CPU usage, instance uptime and license expiry of ASE instance
Resolution
Upgrade to Argent Advanced Technology 5.1A-1610-A or later