products:promonitor:6.8:monitorsguide:sybase:sybasetransactionlog

Sybase transaction log

Purpose

<p> The transaction log file contains information that allows Sybase to recover from a system failure. The transaction log is also required for auditing. </p> <p> Sybase IQ records in the transaction log the information necessary to recover from a system failure. Although the information logged is small for each committed transaction, the transaction log continues to grow in size. In systems with a high number of transactions that change data, over a period of time the log can grow to be very large. </p> <p> It becomes then crucial being able to monitor some transaction log key factors such as the number of log pages already used, the number of log pages reserved for rollbacks or the number of log pages that has not been used yet. </p> <p>Monitor features include :</p> <p> &#x25CF; Monitoring transaction log free pages, used pages and CLR pages </p> <p> &#x25CF; Choice of the unit of measure you want to set to monitor all the items : KB, MB, GB, number of pages, or expressed in percentage values. </p> <p> &#x25CF; Setting a muIti threshold alarm policy for every monitored item and to alert in case a threshold is reached </p>

Report Configuration

Configuration hints

Unit of measure of the monitor: Select the unit of measure you want the monitor to fetch monitored features data, it includes : KB, MB, GB, PAGES

Surveillance table: This is a table of rules that you can use to configure and customize the configuration. Each line of the table will define a rule of monitoring. You can combine multiple rules to cover different cases. Within a rule, you can configure the feature you want to monitor (Free pages, Used pages, CLR pages), a multi-threshold value for the selected feature and the the unit of measure of the threshold

Monitored feature : Select the specific Sybase transaction log feature you want to monitor (Free pages, Used pages, CLR Pages)

Feature threshold : Use the multi-threshold syntax to set multiple threshold/severity associations: G2W:50 W2M:80 M2C:90 (Green To Warning, Warning To Major, etc…), expressed as the monitor Unit of measure or as percentage values An alarm of the corresponding severity will be sent if the monitored feature is over or under threshold (depending on what is being monitored). Set 0 in the field if unused

When setting the multi-thread threshold, notice that for used pages the lower better policy will apply, for free pages and CLR pages a higher better policy.

Unit : Select “As monitor” if you want to monitor data expressed in the same unit of measure as the monitor or select “Percentage” if you prefer values to be monitored this way.

Atomic fields

Unit of measureSelect the unit of measure you want the monitor to fetch the requested information (KB, MB, GB, Pages)

Surveillance table

ParameterDescription
ActiveUse this field to activate or deactivate a line of configuration.
Monitored featureselect one of the supported features : Free pages, Used pages, CLR pages
Feature thresholdThe threshold setting for the selected feature You can use the multi threshold syntax (i.e. : G2W:40 W2C:5) .
UnitSelect “As monitor” if threshold values are expressed in the monitor generic Unit of measure - see “Unit of measure” in the Atomic fields section - , or select “Percentage” if threshold setting are expressed as percentage values
Auto clearIf checked, the alarm will be cleared as soon as the alarm condition is not met anymore.
Alarm tagThis field allows to add custom text within the alarm message. %MSG% variable will contain the actual generated message and can be used such as: “my_prefix %MSG% my_suffix”. By default, tag will be used as prefix.
AlarmIf checked, this line of surveillance will be used for alarm generation.
MetricIf checked, this line of surveillance will be used for metric generation.
ReportIf checked, this line of surveillance will used for showing threshold and severity in the daily report

Examples

ActiveMonitored featureFeature thresholdUnitAuto clearAlarm tagAlarmMetricReport
trueUsed pagesG2W:70 W2C:85Percentagetrue truetruetrue

Effect : For this rule, used pages within the trasaction log file will be monitored

A WARNING alarm is sent if used pages are monitored at 70% or more, a CRITICAL alarm if 85% or more.

Generated metrics

metricIdmetricUnitmetricTargetmetricDescription
SAP_DATABASE_TRANS_LOG_CLR_PAGES_KBKBCLR_PAGESfetched CLR pages value, expressed in KB
SAP_DATABASE_TRANS_LOG_CLR_PAGES_MBMBCLR_PAGESfetched CLR pages value, expressed in MB
SAP_DATABASE_TRANS_LOG_CLR_PAGES_GBGBCLR_PAGESfetched CLR pages value, expressed in GB
SAP_DATABASE_TRANS_LOG_CLR_PAGES_NUMBERNumber of pagesCLR_PAGESfetched CLR pages value, expressed in number of pages
SAP_DATABASE_TRANS_LOG_CLR_PAGES_PERCENTPercentageCLR_PAGESfetched CLR pages value, expressed in percentage
SAP_DATABASE_TRANS_LOG_FREE_PAGES_KBKBFREE_PAGESfetched free pages value, expressed in KB
SAP_DATABASE_TRANS_LOG_FREE_PAGES_MBMBFREE_PAGESfetched free pages value, expressed in MB
SAP_DATABASE_TRANS_LOG_FREE_PAGES_GBGBFREE_PAGESfetched free pages value, expressed in GB
SAP_DATABASE_TRANS_LOG_FREE_PAGES_NUMBERNumber of pagesFREE_PAGESfetched free pages value, expressed in number of pages
SAP_DATABASE_TRANS_LOG_FREE_PAGES_PERCENTPercentageFREE_PAGESfetched free pages value, expressed in percentage
SAP_DATABASE_TRANS_LOG_USED_PAGES_KBKBUSED_PAGESfetched used pages value, expressed in KB
AP_DATABASE_TRANS_LOG_USED_PAGES_MBMBUSED_PAGESfetched used pages value, expressed in MB
SAP_DATABASE_TRANS_LOG_USED_PAGES_GBGBUSED_PAGESfetched used pages value, expressed in GB
SAP_DATABASE_TRANS_LOG_USED_PAGES_NUMBERNumber of pagesUSED_PAGESfetched used pages value, expressed in number of pages
SAP_DATABASE_TRANS_LOG_USED_PAGES_PERCENTPercentageUSED_PAGESfetched used pages value, expressed in percentage value
/home/clients/8c48b436badcd3a0bdaaba8c59a54bf1/wiki-web/data/pages/products/promonitor/6.8/monitorsguide/sybase/sybasetransactionlog.txt · Last modified: 2020/05/29 16:16 (external edit)