SAP ASE, originally known as Sybase SQL Server, is a relational model database server developed by Sybase Corporation, which is predominantly used on the Unix platform but is also available for Microsoft Windows. The administrators can monitor the Sybase database and track the availability and performance issues.
- Database and port(5002) are reachable from the gateway.
- A gateway management profile mapped to a resource.
- Create credentials with type Database before assigning a template to a resource. The Port, Connection Time Out, and Is Secure values are not used to create credentials.
Sybase ASE 160 or higher.
Database Discovery and Monitoring
The administrator can deploy a gateway to support Sybase agentless monitoring.
Discovery using the gateway
The gateway establishes a connection to the database using the management profile and collects metrics from the templates and starts monitoring. To monitor Sybase, install gateway version 5.0.0 or later.
Use one of the following mechanisms to discover Sybase servers to add them to your inventory:
Optionally, add a database server manually to the infrastructure inventory.
To add a resource manually to the inventory:
- Select Infrastructure.
- Click the Settings > Resource > Add.
- From the Add Device window, provide the required details such as Device Type and Management Profile.
- Click Save.
Prepare the resource to start monitoring
To monitor Sybase:
- Associate appropriate database credentials to the discovered database.
- Assign one or more database-specific global templates on the device.
Global templates and metrics
|Collector Type||Template Name|
|Gateway||Sybase - Cache|
|Sybase - Engine|
|Sybase - HeapMemory|
|Sybase - Network|
|Sybase - Statistics|
|Sybase - ThreadPool|
|OpsRamp Metric||Metric Display Name||Unit||Description|
|sybase.cache.object.cachedkb||Sybase Object Cache||kilobytes(KB)||The number of kilobytes occupied by the cache.|
|sybase.cache.procedure.loads||Sybase Cache Procedure Loads||count||The number of stored procedures loaded into the cache.|
|sybase.cachepool.allocated||Sybase Cachepool Allocated||kilobytes(KB)||The number of bytes allocated for the pool.|
|sybase.cachepool.pages.read||Sybase Cachepool Pages Read||count||The number of pages read into the pool.|
|sybase.cachepool.pages.touched||Sybase Cachepool Pages Touched||count||The number of pages currently used within the pool.|
|sybase.cachepool.writes||Sybase Cachepool Writes||count||The number of write operations performed in this pool (one write operation can include multiple pages).|
|sybase.datacache.bufferpools||Sybase Datacache Bufferpools||count||The number of buffer pools within the cache.|
|sybase.datacache.cachesize||Sybase Datacache Cache Size||kilobytes(KB)||Total size of cache in kilobytes.|
|sybase.datacache.status||Sybase Datacache Status||-||The Status of cache.|
|sybase.engine.connections||Sybase Engine Connections||count||The number of connections handled by the engine.|
|sybase.engine.cpu.time||Sybase Engine CPU Time||seconds(s)||The total time, in seconds, the engine has been running.|
|sybase.locks.active||Sybase Active Locks||count||The number of active locks.|
|sybase.locks.free||Sybase Inactive Locks||count||The number of inactive locks.|
|sybase.networkio.packets.received||Sybase NetworkIO Packets Received||count||The number of packets received.|
|sybase.networkio.packets.sent||Sybase NetworkIO Packets Sent||count||The number of packets sent.|
|sybase.netwrokio.bytes.received||Sybase NetworkIO Bytes Received||megabytes(MB)||The number of bytes received by the server.|
|sybase.netwrokio.bytes.sent||Sybase NetworkIO Bytes Sent||megabytes(MB)||The number of bytes sent by the server.|
|sybase.process.activity.heap.memory.allocated||Sybase Process Activity Allocated Heap Memory||kilobytes(KB)||The amount of allocated heap memory.|
|sybase.process.activity.heap.memory.inuse||Sybase Process Activity In Use Heap Memory||kilobytes(KB)||The amount of heap memory currently in use.|
|sybase.process.activity.heap.memory.reserved||Sybase Process Activity Reserved Heap Memory||kilobytes(KB)||The amount of reserved heap memory.|
Assign templates from setup
Assign Sybase templates to one or more resources for a selected client and modify the configuration parameters while assigning templates. For more information, see Assign Templates from Setup.
Assign templates at the device level
Applying Sybase templates at the device level helps assign one or more templates to a specific resource. You can change the configuration parameter default values while assigning the templates. For more information, see Assign Templates at the Device Level.
Resource template configuration parameters:
|Connection Time Out||The maximum time to connect to the database. The driver waits for the specified time before timing out due to connection failure. The default time is 15000 milliseconds(ms).|
|Service Transport Type||To configure the database at a secure end-point. The default type is In-secure. The connection is Secure when the data sent between the client and server is encrypted.|
|Service Port||The port number where the database is running. The connection is made to the specified port if you specify the port and the database name. The default port is 5002.|
|DB Instance Name||The name of the database to connect to. The default names are SYBASE and SYBASEASE.|
|Application Type||The application type value to identify the adapter. For example, SYBASE.|
Warning: Do not change the default application type value.
Assign template from device management policies
Device management policies help manage resources. You can assign monitoring templates, knowledge base articles, and custom attributes using device management policies. The device management policy can be applied to one or a set of resources. For more information, see Creating Policies.
View resource metrics
The gateway monitors the application using the assigned templates and displays the results in graphical format. To view resource metrics, click the desired database resource name > resource Details > Metrics.
Verify the following if the graphs are not plotted correctly:
- The resource is accessible and Telnet is established for the IP address and port.
- Valid credentials are used for the resource.