sybase AC Configuration

You can configure the sybase probe by defining various profiles and connections to the Sybase server. The connections that you set up are used for running monitoring profiles on the Sybase server. These profiles monitor real-time events occurring in the server using various checkpoints. You can select the required checkpoints and activate the profile that notifies you when any unwanted event occurs in the server. For example, you can create a profile that uses locked_users checkpoint to monitor the number of locked users in the system at a given time.
uimpga-ga
sybase_AC
You can configure the sybase probe by defining various profiles and connections to the Sybase server. The connections that you set up are used for running monitoring profiles on the Sybase server. These profiles monitor real-time events occurring in the server using various checkpoints. You can select the required checkpoints and activate the profile that notifies you when any unwanted event occurs in the server. For example, you can create a profile that uses locked_users checkpoint to monitor the number of locked users in the system at a given time.
The probe provides predefined checkpoints, which you can customize. You can also create checkpoints. These profiles can also be configured to generate alarm and QoS messages.
The following diagram outlines the process to configure the sybase probe.
sybase_AC_configuration
sybase_AC_configuration
 
Contents
 
 
 
 
Verify Prerequisites
  • Verify that required hardware, software, and related information is available before you configure the probe.
  • The probe is configured on the same system as the Sybase server.
Set up General Properties
You can set up the logging and alarm severity conditions of sybase probe. The probe uses the default settings if you do not configure the general properties.
 
Follow these steps:
 
  1. Select the 
    sybase
     node and specify the following values as needed:
    •  
      Alarm severity filter:
       sets a filter on severity levels that can become potential alarms. The sybase probe can check the Sybase databases. Some events that are generated are vital and key to the performance and availability of the database. For example, as a database administrator, you want to convey important events on to the operations center or help-desk, so that the event can trigger emails. The 
      Alarm severity filter
       considers the events matching or exceeding the selected severity level alarms. If you select major, then only the messages with severity level as major and above are considered as alarms.
    •  
      Log Size in KB
      : specifies the maximum size of the probe log file.
      Default: 100
    •  
      Log Level: 
      specifies the level of details that are written to the log file. Log as little as possible during normal operation to minimize disk consumption, and increase the amount of detail when debugging.
      Default: 0 - Normal
  2. Click 
    Save
    .
Create a Connection
A connection can be used by more than one monitoring profile. The probe provides you the advanced option to define connections that helps you monitor server or tables, as needed.
 
Follow these steps:
 
  1. Click the 
    Options (icon)
     next to the 
    sybase
     node in the navigation pane.
  2. Click the 
    Create new profile
     option.
  3. Specify a name of the connection in the 
    Connection Name
     field.
  4. Specify the 
    User ID
    Password
    , and name of the 
    Server
     that you want to connect. 
  5. Set or modify the following values, as needed:
    •  
      Advanced monitoring
      : enables you to perform advanced monitoring from the probe. The 
      Monitor Option
       field is enabled when you select the 
      Advanced monitoring
       check box.
      •  
        Monitor Option
        : specifies one of the following objects to be monitored:
        • Monitoring Server
        • Monitoring Tables
         
        • In advanced mode, the probe allows you to monitor Sybase server and tables. In basic mode, the probe monitors only the server. 
        • The Monitoring Server is not a part of the Adaptive Server Enterprise version 15.7 and later. Hence, advanced monitoring using Monitoring Server is not supported.
    •  
      Description
      : indicates additional information about the connection.
    •  
      Monitoring Server
      : specifies the monitoring server name. This field appears when you select the Monitoring option as 
      Monitoring server
      .
    •  
      Retry attempts
      : specifies the number of attempts that the probe tries to connect in case of connection failure.Default: 0 
    •  
      Retry Delay
      :
       
      specifies the time period for which the probe waits between two connection attempts.
      Default: 1 
    •  
      Retry Delay (Units)
      : specifies the unit for measuring the value of retry delay.
      Default: sec
    •  
      Timeout
      : specifies the time before considering a connection failure.
      Default: 5
    •  
      Timeout (Units)
      : specifies the unit for measuring the timeout.
      Default: sec
  6. Click 
    Submit
    .
Test the Connection
Click 
Actions
 > 
Test Connection
 in the 
Connection Name
 node. If the connection is successful, it returns the instance name and version number. If the connection is unsuccessful, the probe displays a sybase error message. 
Create a Profile
You can create multiple profiles that monitor various parameters of the Sybase server. These profiles can be configured to to use a Sybase server connection that you have defined.
 
Follow these steps:
 
  1. Navigate to the 
    connection name
     
     
    node and click the 
    Options (icon)
    .
  2. Click the 
    Create new profile
     option.
  3. Specify a unique name of the profile in the 
    Name
     field.
  4. Select the connection to be used in the profile from the 
    Connection
     field.
  5. Click 
    Submit
    .
    The profile is saved.
    : The probe adds default checkpoints to the profile, however, they are inactive by default. For more information about activating the required checkpoint, see the Add Profile Checkpoints section.
Add Profile Checkpoints
The 
Add Profile Checkpoint
 option lets you add a checkpoint to the monitoring profile of the probe.
 
Follow these steps:
 
  1. Navigate to the required 
    profile name
     node and click the 
    Options
     icon.
  2. Click 
    Add profile checkpoints
    .
  3. Select the checkpoints to be added from the 
    Available
     list and click 
    Submit
    .
    The profile checkpoint is added to the profile.
Configure Checkpoints
You can configure the properties of a checkpoint to monitor the server performance or unwanted events. 
 
Follow these steps:
 
  1. Navigate to the 
    checkpoint name
     node under the required profile.
    : You can also configure a checkpoint from sybase > Checkpoints > 
    checkpoint name
    . All changes that are made to a checkpoint are applied to all instances of the checkpoint in the configured profiles.
  2. Select  
    Active
     to activate the checkpoint. If you do not select the check box, the checkpoint is not available for monitoring.
  3. Specify the following values as required:
    •  
      Profile/Checkpoint
      : specifies the checkpoint name that you want to configure.
    •  
      Description
      : specifies the additional information about the checkpoint.
    •  
      Check Interval
      : specifies the time interval at which the Sybase tables and server is scanned.
       A shorter interval can also increase the system load. Reduce this interval to generate alarms frequently. 
    •  
      Check interval (Units)
      : specifies the check interval unit. You can select any of the following units:
      • sec
      • min
      • hrs
    •  
      Samples:
       specifies the number of samples to calculate an average value, which is compared with the specified alarm threshold. The probe generates an alarm when the average value of any sample breaches the threshold. The probe behavior for the following 
      Samples
       value is described as follows: 
      • 0: Sampling is done based on the number of samples defined in the template. If no number is specified in the template, no sampling is done. 
      • 1: No sampling is done. 
      • 3: The probe performs the following: 
        • uses the first sample value in the first interval 
        • uses the average of samples 1 and 2 in the second interval 
        • uses the average of samples 1, 2, and 3 in the third interval 
      Default: 1
    •  
      Clear message
      : specifies the message name used for clear alarm.
    •  
      Clear severity
      : specifies the severity used for message issued when the threshold is not breached. You can select from the following options:
      • clear
      • information
      • warning
      • minor
      • major
      • critical
       Default: clear
  4. Click 
    Save 
    to save the checkpoint configuration details.
Create Custom Checkpoints
You can define a custom checkpoint for monitoring the Sybase server.
 
Follow these steps:
 
  1. Navigate to the 
    Checkpoints 
    node in the navigation pane.
  2. Click the 
    Options (icon)
     next to the 
    Checkpoints 
    node.
  3. Click 
    Add New Checkpoint
    .
  4. Specify the name of the checkpoint that you want to create in the
     Name
     field.
  5. Specify the connection in the 
    Connection Name
     field.
  6. Specify the file name where the query is stored in the 
    Query File
     field.
  7. Specify the query to retrieve the data for the checkpoint in the
     Query
     field.
  8. Enable the 
    Interval Modus
     check box to subtract the variable value from the value generated at the end of the interval. 
  9. Click 
    Submit
    .
Add Exclude Patterns
You can define exclude patterns to define objects that you do not want to monitor for the checkpoint.
 
Follow these steps:
 
  1. Click the 
    checkpoints name
     
     
    node in the navigation pane.
  2. Select 
    Use Exclude 
    check box in the 
    Use Exclude Configuration
     section.
  3. Click
     New 
    in the.
    Exclude List
     section.
  4. Specify the regular expression in the 
    Exclude Pattern
     field.
  5. Click
     Test
     in the 
    Action 
    drop-down list.
    Response
     dialog opens displaying the list of objects that are excluded. The excluded objects have their Exclude value set to 1.
     This test is possible only for running active profiles and checkpoints that you do not want to monitor on the checkpoint.
  6. Click 
    Save
    .
    The exclude pattern is added.