Monitoring - Check configuration - Cockpit ITSM · Network I. Network - Bandwidth Objective: To...

Monitoring - Check configuration

FAQ document

Table of contentsPrerequisites..................................................................................................................................................... 8

I. Item configuration..................................................................................................................................... 8

II. Specific settings...................................................................................................................................... 8

Equipment........................................................................................................................................................ 9

I. Equipment - Ping...................................................................................................................................... 9

II. Equipment - Port................................................................................................................................... 11

Network.......................................................................................................................................................... 12

I. Network - Bandwidth.............................................................................................................................. 12

II. Network - Processor.............................................................................................................................. 13

III. Network - Memory................................................................................................................................ 14

SNMP............................................................................................................................................................. 16

I. Prerequisites........................................................................................................................................... 16

II. SNMP - SNMP Request......................................................................................................................... 16

Web................................................................................................................................................................. 21

I. Web - HTTP request............................................................................................................................... 21

II. Web - SSL Certificate............................................................................................................................24

III. Web - FTP connection.......................................................................................................................... 25

IV. Web - SMTP connection.......................................................................................................................26

Unix / Linux..................................................................................................................................................... 28

I. Prerequisites........................................................................................................................................... 28

II. Unix - Connection test...........................................................................................................................28

III. Unix - Time offset.................................................................................................................................. 28

IV. Unix - Up-time...................................................................................................................................... 29

V. Unix - Process status............................................................................................................................. 30

VI. Unix - Process - Memory......................................................................................................................31

VII. Unix - Process - Processor usage.......................................................................................................32

VIII. Unix - Disk free space.........................................................................................................................33

IX. Unix - Disk mounted............................................................................................................................. 35

X. Unix - I/O disk........................................................................................................................................ 36

XI. Unix - Inode usage............................................................................................................................... 37

XII. Unix - Swap usage.............................................................................................................................. 38

XIII. Unix - Memory usage......................................................................................................................... 39

XIV. Unix - Processor usage...................................................................................................................... 40

XV. Unix - Network usage..........................................................................................................................41

XVI. Unix - Directory - Size........................................................................................................................42

XVII. Unix - File - Count............................................................................................................................. 43

XVIII. Unix - File - Size............................................................................................................................... 44

XIX. Unix - File - Modification date............................................................................................................45

Monitoring - Check configuration2

238

XX. Unix - Custom command - Exit code..................................................................................................46

XXI. Unix - Custom command - Output.....................................................................................................47

XXII. Unix - Log file.................................................................................................................................... 48

XXIII. Unix - System load........................................................................................................................... 51

Windows......................................................................................................................................................... 53

I. Pre-requisites.......................................................................................................................................... 53

II. Windows - Connection test...................................................................................................................53

III. Windows - Time offset.......................................................................................................................... 53

IV. Windows - Up-time............................................................................................................................... 54

V. Windows - Disk free space.................................................................................................................... 55

VI. Windows - Service status.....................................................................................................................56

VII. Windows - Process status...................................................................................................................57

VIII. Windows - Process - Threads............................................................................................................58

IX. Windows - Processes - Memory..........................................................................................................59

X. Windows - Swap usage......................................................................................................................... 60

XI. Windows - Memory usage.................................................................................................................... 61

XII. Windows - Processor usage................................................................................................................62

XIII. Windows - Network usage..................................................................................................................63

XIV. Windows - Scheduled tasks...............................................................................................................64

XV. Windows - Security center................................................................................................................... 66

XVI. Windows - File - Count.......................................................................................................................67

XVII. Windows - File - Size.........................................................................................................................68

XVIII. Windows - File - Creation date.........................................................................................................69

XIX. Windows - File - Modification date.....................................................................................................70

XX. Windows - Custom command - Output..............................................................................................71

XXI. Windows - Log file.............................................................................................................................. 72

XXII. Windows - IIS - Application pool status............................................................................................74

AS400............................................................................................................................................................. 76

I. Pre-requisites.......................................................................................................................................... 76

II. AS400 - Connection test........................................................................................................................ 76

III. AS400 - Time offset.............................................................................................................................. 76

IV. AS400 - Active jobs.............................................................................................................................. 77

V. AS400 - ASP Usage............................................................................................................................... 78

VI. AS400 - Temp. addresses usage..........................................................................................................79

VII. AS400 - Central unit usage..................................................................................................................80

VIII. AS400 - Printer state..........................................................................................................................81

IX. AS400 - Subsystem state..................................................................................................................... 82

X. AS400 - Problems monitoring...............................................................................................................83

XI. AS400 - Number of jobs in a queue.....................................................................................................84

XII. AS400 - Jobs execution state.............................................................................................................85


238

XIII. AS400 - Jobs status........................................................................................................................... 86

XIV. AS400 - Job existence........................................................................................................................89

XV. AS400 - *SYSOPR messages needing reply.......................................................................................90

XVI. AS400 - SQL query returning "OK"....................................................................................................91

vSphere - vCenter (VMWare server virtualization platform)............................................................................93

I. Pre-requisites.......................................................................................................................................... 93

II. vSphere - vCenter - Connection test.....................................................................................................93

III. vSphere - vCenter - Alert monitoring....................................................................................................93

ESX (VMWare server virtualization platform)...................................................................................................95

I. Pre-requisites.......................................................................................................................................... 95

II. ESX - Connection test...........................................................................................................................95

III. ESX - Time offset.................................................................................................................................. 95

IV. ESX - DataStore - Config. status..........................................................................................................96

V. ESX - DataStore - Overall status............................................................................................................97

VI. ESX - Disk I/O....................................................................................................................................... 98

VII. ESX - Configuration status..................................................................................................................99

VIII. ESX - Overall status............................................................................................................................ 99

IX. ESX - Memory usage.......................................................................................................................... 100

X. ESX - Network usage.......................................................................................................................... 101

XI. ESX - NIC state check........................................................................................................................ 102

XII. ESX - Processor usage...................................................................................................................... 103

XIII. ESX - Uptime.................................................................................................................................... 104

XIV. ESX - VM connection state...............................................................................................................105

XV. ESX - VM power state........................................................................................................................ 106

Database...................................................................................................................................................... 108

I. Pre-requisites........................................................................................................................................ 108

II. DB - Connection test........................................................................................................................... 108

III. DB - Connection count....................................................................................................................... 110

IV. DB - SQL - Row count........................................................................................................................ 110

V. DB - SQL - Query - Return integer.......................................................................................................111

VI. DB - SQL - Query - Return string.......................................................................................................113

VII. DB - MSSQL - DB Size...................................................................................................................... 113

VIII. DB - MSSQL - DB free space...........................................................................................................114

IX. DB - MSSQL - Free space in files.......................................................................................................116

X. DB - MSSQL - DB Backup..................................................................................................................117

XI. DB - MSSQL - Log file Backup...........................................................................................................118

XII. DB - MSSQL - Jobs in progress........................................................................................................119

XIII. DB - MSSQL - Jobs in error..............................................................................................................120

XIV. DB - MSSQL - Lock detection..........................................................................................................121

XV. DB - Hana - Alert monitoring.............................................................................................................122


238

XVI. DB - Hana - Free space on volume (LOG)........................................................................................123

XVII. DB - Hana - Free space on volume (DATA)......................................................................................124

XVIII. DB - Hana - Memory usage............................................................................................................126

XIX. DB - Hana - Free disk space............................................................................................................127

XX. DB - Hana - Backup status...............................................................................................................128

XXI. DB - Hana - Archive status...............................................................................................................129

XXII. DB - Hana - Savepoint monitoring..................................................................................................130

XXIII. DB - Hana - Service status.............................................................................................................131

XXIV. DB - Hana - Replication status.......................................................................................................132

XXV. DB - Hana - DB Threads..................................................................................................................132

XXVI. DB - Hana - Transactions blocked.................................................................................................134

XXVII. DB - Oracle - Free space in DB.....................................................................................................134

XXVIII. DB - Oracle - ArchiveLog Mode...................................................................................................135

XXIX. DB - Oracle - RedoLog count........................................................................................................136

XXX. DB - Oracle - Tablespace status.....................................................................................................137

XXXI. DB - Oracle - Free space in tablespace.........................................................................................138

XXXII. DB - Oracle - Max. Extent.............................................................................................................140

XXXIII. DB - Oracle - Next Extent.............................................................................................................141

XXXIV. DB - Sybase - Monitoring engine status......................................................................................142

XXXV. DB - Sybase - LOG Free Space....................................................................................................142

XXXVI. DB - Sybase - DB Free space......................................................................................................143

XXXVII. DB - Sybase - LOG backup........................................................................................................145

XXXVIII. DB - Sybase - DB backup..........................................................................................................146

XXXIX. DB - DB2 - Lock wait................................................................................................................... 147

XL. DB - DB2 - Transaction log usage.....................................................................................................148

SAP............................................................................................................................................................... 150

I. Prerequisites......................................................................................................................................... 150

II. Generic configuration alerts.................................................................................................................150

III. SAP - Connection test........................................................................................................................ 150

IV. SAP - System up-time........................................................................................................................ 151

V. SAP - Users expired (SU01).................................................................................................................152

VI. SAP - Users profil (SU01)................................................................................................................... 153

VII. SAP - License expiration................................................................................................................... 154

VIII. SAP - DB - Object consistency (DB02).............................................................................................155

IX. SAP - DB - Sybase - DB Free space (DB02)......................................................................................156

X. SAP - DB - Oracle - DB Free space (DB02).........................................................................................157

XI. SAP - DB - Oracle - Tablespace Free space (DB02)...........................................................................158

XII. SAP - DB - Oracle - Backup (DB12)..................................................................................................160

XIII. SAP - DB - Oracle - Archiving (DB12)...............................................................................................161

XIV. SAP - DB - Oracle - DBA Planning Calendar (DB13)........................................................................162


238

XV. SAP - DB - MSSQL - DB Free space (DB02).....................................................................................163

XVI. SAP - DB - MSSQL - Free space in files (DB02)..............................................................................164

XVII. SAP - DB - MSSQL - Backup (DB12)..............................................................................................165

XVIII. SAP - DB - MSSQL - Archiving (DB12)...........................................................................................166

XIX. SAP - DB - MSSQL - Database Check (DB13).................................................................................167

XX. SAP - DB - MSSQL - Deadlocks (DB02)...........................................................................................168

XXI. SAP - DB - DB2 - Free space DB (DB02).........................................................................................169

XXII. SAP - DB - DB2 - Backup (DB12)...................................................................................................170

XXIII. SAP - DB - DB2 - Archiving (DB12)................................................................................................171

XXIV. SAP - DB - Hana - Backup (DB12).................................................................................................172

XXV. SAP - DB - MaxDB - Backup (DB12)...............................................................................................172

XXVI. SAP - Performance (ST03).............................................................................................................173

XXVII. SAP - Waiting work processes (SM50)..........................................................................................175

XXVIII. SAP - Work processes in error (SM50).........................................................................................176

XXIX. SAP - Lock entries (SM12).............................................................................................................177

XXX. SAP - Update status (SM13)...........................................................................................................179

XXXI. SAP - Updates in error (SM13).......................................................................................................180

XXXII. SAP - Dump count (ST22).............................................................................................................182

XXXIII. SAP – Batch Input in error (SM35)................................................................................................184

XXXIV. SAP - Jobs ready (SM37).............................................................................................................185

XXXV. SAP - Intercepted jobs (SM37)......................................................................................................186

XXXVI. SAP - Jobs in process (SM37).....................................................................................................188

XXXVII. SAP - Jobs in error (SM37)..........................................................................................................189

XXXVIII. SAP - Job finished (SM37).........................................................................................................191

XXXIX. SAP - Process chain in progress (RSPCM)..................................................................................193

XL. SAP - Process chain in error (RSPCM)..............................................................................................194

XLI. SAP - Process chain finished (RSPCM)............................................................................................195

XLII. SAP - RFC destination status (SM59)..............................................................................................196

XLIII. SAP - APO Live Cache status (LC10).............................................................................................197

XLIV. SAP - Bridge status (SMGW)..........................................................................................................198

XLV. SAP - Global setting status (SE06)...................................................................................................199

XLVI. SAP - Client status (SCC4).............................................................................................................200

XLVII. SAP - Trace status (ST05)..............................................................................................................201

XLVIII. SAP - Syslog (SM21)..................................................................................................................... 202

XLIX. SAP - Prints in process (SP01).......................................................................................................204

L. SAP - Prints in error (SP01)..................................................................................................................204

LI. SAP - qRFC - Output - Queue status (SMQ1)....................................................................................205

LII. SAP - qRFC - Output - Flow error (SMQ1)........................................................................................207

LIII. SAP - qRFC - Output - Flow on hold (SMQ1)...................................................................................208

LIV. SAP - qRFC - Input - Queue status (SMQ2).....................................................................................209


238

LV. SAP - qRFC - Input - Flow error (SMQ2)............................................................................................210

LVI. SAP - qRFC - Input - Flow on hold (SMQ2)......................................................................................211

LVII. SAP - tRFC in error (SM58)..............................................................................................................213

LVIII. SAP – tRFC on hold (SM58)............................................................................................................214

LIX. SAP - Transmission requests (SOST)...............................................................................................215

LX. SAP - Idocs (WE05)........................................................................................................................... 216

LXI. SAP - Transports statuses (STMS)...................................................................................................219

LXII. SAP - XML Messages monitoring (SXMB_MONI)............................................................................219

LXIII. SAP - NetWeaver Gateway - Error log............................................................................................221

LXIV. SAP - CCMS Monitor (RZ20)..........................................................................................................221

JAVA application - JMX................................................................................................................................ 223

I. Prerequisites......................................................................................................................................... 223

II. JMX - MBean request.......................................................................................................................... 223

III. JMX - CPU Usage............................................................................................................................... 226

IV. JMX - Heap memory usage................................................................................................................227

V. JMX - Thread count............................................................................................................................. 228

Email............................................................................................................................................................. 229

Custom command (from monitoring server).................................................................................................231

Group check................................................................................................................................................. 233

Annexes........................................................................................................................................................ 235

I. Regular expressions............................................................................................................................. 235

II. Date and time format........................................................................................................................... 236

III. OID Examples..................................................................................................................................... 236

IV. Windows - WMI Performance Counters.............................................................................................236

A. Test the query.................................................................................................................................................... 236

B. Rebuild Performance Counters.........................................................................................................................237

V. SAP - DB - Return codes..................................................................................................................... 237

VI. SAP - Process chain - Return code....................................................................................................237

VII. Running checks manually..................................................................................................................238


238

Prerequisites

I. Item configuration

To create a check, the following items must be configured:

• Organization

• Environment

• Application

• Equipment

• Run schedule

• Team

• Notification (option)

II. Specific settings

The generic settings are common to all control types:

• “Parameters” tab

• “Instructions” tab

• “Applications” tab

• “Availability reports” tab


238

Equipment

I. Equipment - Ping

Objective:

To monitor the availability of a device.

Generic settings:

• Equipment availability: Yes

• Reverse status: Yes

• Graphics: Yes

• Dual threshold: No

• Available in the reports: Yes (Monitoring)

Specific settings:

Setting Information Value Mandatory

Alert threshold Alerts if the equipment does not respond when pinged.

Alerts if the response time exceeds X ms. Integerbetween 1 and 30,000

Yes

Configuration alerts:

• If an internal error occurs with the monitoring engine (i.e., if cannot run the command).

Additional information:

• When the control is in error, a second attempt is launched after 10 seconds, if the control is still in

error, an alert is generated.

• There are three different ping types, by default the System ping is used, Java ping and JNI native

ping are deactivated. The parameters ping are specified in the monitoring engine settings (in expert

mode), and their default configuration is:

Setting Default value Description

network.ping.java.enabled false Java ping active [true|false]

network.ping.jni.enabled false Native ping active [true|false]

network.ping.jni.generate.errors false Native ping cannot generate true alerts [true|false]

Principles:

• Java ping: this is the first ping to be sent if the "network.ping.java.enabled" option is set to "true."


238

The check is an ECHO over port 7 of the target device, and it does not increase the response time:

◦ If the request completes, the check reports a successful outcome.

◦ If port 7 is blocked, if the DNS name of the device is unknown or unreachable, the check

reports an issue with the configuration.

◦ In other cases, the check uses a different type of ping.

• JNI native ping: this is the second ping to be sent if the "network.ping.java.enabled" option is set

to "true" and if the check engine is installed on a Windows machine.

The check is an internal development that has similar functionality to "ping.exe." It is only available

on Windows installation and only IP v4 addresses are supported. It increases the response time by

a few milliseconds.

The ping settings contain a second setting: "network.ping.jni.generate.errors":

◦ network.ping.jni.generate.errors = true:

▪ If the ping generates a time-out, an error report is sent.

▪ Other errors generate a report of a configuration issue.

◦ network.ping.jni.generate.errors = false:

▪ If the address is not an IP v4 address, or if the ping command generates an error, the check

switches to a different type of ping.

• System ping: by default this is the only used ping. This is the third and final ping to be sent when

the 2 others pings are activated.

The check uses the output of the "ping" system command. It increases the response time by a few

milliseconds. This is the command that serves as the standard, because it generates exactly the

same output as a manual ping command. Under Windows, each ping is the output of a sub-

processes, and this can generate issues when 60 to 100 sub-processes are run in parallel with one

another.

Example:


238

II. Equipment - Port

Objective:

Monitoring whether a port is open.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Port number to monitor IntegerBetween 1 and 65535

Yes

Configuration alerts: None

Additional information: None

Example:


238

Network

I. Network - Bandwidth

Objective:

To monitor the bandwidth load on a network device.

Generic settings:

• Equipment availability: No

• Reverse status: No

• Graphics: No

• Dual threshold: Yes

• Available in the reports: No

Specific settings:


Interface ID of the network interface to be monitored. Can be entered manually or selected via the "List" button.

Integer be-tween 0 and 999 999 999

Yes

Traffic Traffic direction. InboundOutboundBoth

Yes

Alert threshold Load range (minimum or maximum values). Whole num-ber between 0 and 100

Yes


• The SNMP connection could not be established.


• The check can only be run on "Network" type hardware.


238

Example:

II. Network - Processor

Objective:

To monitor the load on the processor of a network device.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Load range (minimum or maximum values). Whole num-ber between 0 and 100

Yes




• The check can only be run on "Network" type hardware.


238

Example:

III. Network - Memory

Objective:

To monitor memory usage of a network device.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Load range (minimum or maximum values). Integer be-tween 0 and 100

Yes




• The alert can only be run on "Network" type hardware.


238

Example:


238

SNMP

I. Prerequisites

• The device must be present in the infrastructure (Infrastructure - Equipment management)

• SNMP access must be correctly configured.

II. SNMP - SNMP Request

Objective:

To send an SNMP request (OID) to a device.

Generic settings:



• Graphics: Yes


• Available in the reports: Yes (Monitoring / Backups)

Specific settings:


Object Identifier(OID)

OID (Object Identifier) sent to the device Yes

Manufacturer Manufacturer name No

MIB file MIB file No

Alert threshold Validity range (minimum, maximum or different from). Integer be-tween 0 and 999 999 999

Yes

Value returned (different or contains). Alphanumeric Yes

Number of times to run in excess of the threshold before generating an alert.

Integer be-tween 0 and 99

Yes



• Error code 1002 - Result was not a Number: This alert is generated when the value that is returned

does not match the expected type (For example, a tab may be returned instead of an integer) or

when the SNMP agent cannot respond to the OID.


• The check executes the SNMP request via the SNMPGET command.


238

• The check carries out a polling operation by sending a request to obtain a value, but does not

receive any traps.

Note: to receive SNMP taps, configure the monitoring engine in the "Functional settings" tab under

"Monitoring and infrastructure / Monitoring - Network." The output of the alerts is shown in the

"Monitoring" module under "External alerts."

• The "Object Identifier (OID)" field can be completed manually with an OID.

It is recommended that you run a request to monitor the value returned.

In the example below, the OID generates a "STRING" type value, and obviously you must not select

a "numeric value" type alert threshold; instead, this needs to be an "Alphanumeric value."

• The "Object Identifier (OID)" field can be completed using the MIBs provided in Cockpit IT Service

Manager. To do this, the "Manufacturer" and "MIB file" must be configured (see the menu under

Monitoring > Configuration > MIB Management) before the check is created.

In the check, click on the "List" button, and in the window that appears, select:

◦ The manufacturer

◦ The MIB file

The browse the MIB hierarchy to select an OID. There are three types of data:

"NODE": "NODE"s are hierarchical nodes in the MIB hierarchy; when launching an SNMPWALK

with their OID, this lists the child OIDs. The results that are generated cannot be used, so do not

use these OIDs.

The image below shows a "NoSuchInstance" value generated by a "NODE" type OID:


238

"SCALAR ": "SCALAR" type OIDs generate a numeric or alphanumeric value and can be selected

for monitoring.

Example with an alphanumeric return:

Example with a numeric return:


238

"TABLE": "TABLE" OIDs have "TABLE_ROW" and "TABLE_COLUMN" OIDs as children. When you

click on a table OID, the table is shown in the "Details" section.

The table values are refreshed when you click on the "List" button.

To monitor a table element, click on the cell containing the value that you wish to monitor. The

"Value" and "Object Identifier (OID)" are automatically updated. Then, save the results.


238

When a table does not generate a value, this means that the OIDs do not exist on the device:

• Note 1: When the check generates the "Result was not a number" message, this can be related to

the "No such object available on this agent at this OID" which means that the SNMP agent cannot

respond to the requested OID,

Example:


238

Web

I. Web - HTTP request

Objective:

To monitor the availability of a URL.

Generic settings:



• Graphics: Yes



Specific settings:


Request type GET: method of retrieving information contained in a web-page specified in the "ADDRESS (URL)" field.Post: method of transmitting data: when this box is checked, ten fields will appear to post 10 items.

GETPOST

Yes

Address (URL) URL to be monitored, which must be in one of the following formats:

• http://*• https://*

Alphanumeric Yes

Item to post The purpose of the "POST" method is to send data via a form.When the "POST" method is selected, ten fields appear, andeach field represents an item to be posted.The format of the "POST" fields is: key = value

No

SSL certificate fingerprint

SSL Certificate fingerprint in SHA-1 formatCase sensitive.The characters “:” and “ “ are accepted.

Alphanumeric No

HTTP Authenti-cation

HTTP authentication involves authenticating the client with an HTTP server (a popup before showing the website).Authentication can be:

• Standard◦ User◦ Password◦ Zone (authentication realm): optional

• NTLM◦ User◦ Password◦ NTLM workstation◦ NTLM domain

No

Alert threshold Triggers an alert if the return code of the HTTP request is anything other than 'XXX'

HTTP code No


238

Triggers an alert if the response time exceeds X ms. Integer be-tween X and X

Triggers an alert based on the presence of terms on the webpage.Case sensitive.

ContainsDoes not contain

No


• The authentication as configured does not work correctly (1011 - illegal argument).

• Certificate issues The certificate is self-signed, does not originate with a trusted authority, has

expired and/or the SSL fingerprint is not provided (Example: SSL error -

SunCertPathBuilderException : unable to find valid certification path to requested target).


• The certificate fingerprint must be provided when the certificate is self-signed, does not originate with

a trusted authority, or has expired.

• The error message "SSL peer shut down incorrectly" indicates that the SSL connection has been

closed, this can happen when the supervised Url uses deprecated algorithms incompatible with those

of the supervision engine.

• The following alert « SSL error - SunCertPathBuilderException : unable to find valid certification

path to requested target » shows that the control need a fingerprint to be successful.

• The alert below shows that both fingerprints (expected by the Web server and filled in the control)

are not matching.

SSL error - The certificate sent by the server does not match the expected fingerprint:

fingerprint=E24A79739DCBD480F871FFEFDD3127C3B100A031 /

expected=398E1936639BA5206DF5179BFBB7010933969400

fingerprint : fingerprint returned by the Web server.

expected : fingerprint filled in the control.

In this case the fingerprint returned by the Web server must be chose.

After this modification, if the same error message is back with another fingerprint, it means that

several fingerprints are needed. Add the different fingerprints separated with a comma, ex:

BD8E3CFB8FDE5789A40919C6D319417CAD78140A,398E1936639BA5206DF5179BFBB70109339

69400, etc.

• The control can accept all the fingerprints returned by the Web server when the character « * » is

filled. But this option is not secure.


238

Example:

• Authentication is required to access the URL being monitored.:

To find out which settings to send:

◦ With a browser (e.g., Firefox) use the "Inspect element" function and retrieve the network

exchanges and therefore the POST method sent:

◦ in the "Headers" tab the "Request URL" field indicates the URL that must be used to run the

test (in the "Check address (URL)" field).

◦ In the "Settings" tab the "Form data" section indicates the elements that are posted. The

username, password and action of the button on the first copy of the screen are shown here.

◦ Complete the items to be posted with the relevant information.:

◦ In this example, the alert threshold (return code, search terms, and response time) applies to

the URL that appears after logging in and therefore allows the availability of the application to

be monitored over and above simply connecting to it.


238

• Example with additional HTTP authentication: ("User" and "Password" fields):

II. Web - SSL Certificate

Objective:

To monitor the validity of the SSL certificate.

Generic settings:



• Graphics: No



Specific settings:


Check type Select the check type:Check the certificate of the URL filled in.Check the certificate chain of the URL filled in.

CertificateCertificate chain

yes

Address (URL) Address (URL) to be monitoredEnter a secure URL (https).

Alphanumeric Yes

SSL Certificate fingerprint

SSL Certificate fingerprint in SHA-1 formatCase sensitive.The characters “:” and “ “ are accepted.

Alphanumeric No

Alert threshold Remaining validity period (prior to expiration (in days). Integer be- Yes


238

tween 1 and 90


• "SSL error - The certificate sent by the server does not match the expected fingerprint:" Check the

fingerprint specified in the "SSL Certificate fingerprint" field.

• "SSL error - SunCertPathBuilderException: unable to find valid certification path to requested

target:" The certificate cannot be validated without a valid certification path.

• URL issues (missing or unavailable URL or a protocol other than "https").

• Connection error (timeout, bad port, or blocked port).

Example: « SSL error - SocketException: Connection reset »

• SSL (handshake) error.

• Unknown DNS name.

Example: « SSL error - SSLPeerUnverifiedException: Certificate for <wrong.host.badssl.com>

doesn't match any of the subject alternative names: [*.badssl.com, badssl.com] »

• Unexpected error that was not handled correctly.


• The certificate fingerprint must be provided when the certificate is self-signed, does not originate with

a trusted authority, or has expired.

Example:

To monitor the site "https://www.google.com" - which has up to date certificates from a trusted authority,

configure the alert as follows:

If the certificate is self-signed or does not originate with a trusted authority, the fingerprint of the SSL

certificate must be provided:


238

III. Web - FTP connection

Objective:

To monitor the availability of the FTP connection.

Generic settings:



• Graphics: No



Specific settings:


Port Port to use to connect via FTP. Integer between 10 and 65536

Yes

Login details Username Alphanumeric No

Password Password Alphanumeric No



Example:

IV. Web - SMTP connection

Objective:

To monitor the availability of the SMTP connection.

Generic settings:



• Graphics No


238



Specific settings:


Server SMTP Server Alphanu-meric

Yes

Port Port to connect over. IntegerBetween 1 and 65535

Yes

Protocol Use the SSL secure protocol YesNo

No

Authentication method

Authentication method:• Plain text (RFC4616)• CRAM-MD5 (RFC2195)• Login (Microsoft)• No authentication

Yes

Username User. Alphanu-meric

Yes

Password Password. Alphanu-meric

Yes


• The SMTP connection is closed.

• The specified port is not valid.

• Username/password issue.


Example:


238

Unix / Linux

I. Prerequisites


• System access must be correctly configured.

II. Unix - Connection test

Objective:

Monitor the connectivity of a Unix-type OS.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Unable to connect


• User/password issues

• Incorrectly listed or closed SSH port

• SSH not started on the device

• Issue with the SSH key


• The device must be running a Unix-type operating system such as HP UX, Linux, AIX, or Solaris.

Example:

III. Unix - Time offset

Objective:


238

Compare the system time with a time server.

Generic settings:



• Graphics: No



Specific settings:


Time server (NTP)

Time server name Alphanumeric Yes

Port Port numberPort by default: 123


Yes

Alert threshold Delay in seconds beyond which an alert is triggered Integer be-tween 1 et 99 999

Yes


• Hardware connection issues.

Additional information: None.

Example :

IV. Unix - Up-time

Objective:

Monitors the amount of time since the system last started up.

Generic settings:



• Graphics: No



238


Specific settings:


Alert threshold Time since the system last started (minimum or maximum value).


Yes

Time unit. DaysHours Min-utes

Yes




Example:

V. Unix - Process status

Objective:

Monitors whether processes are running.

Generic settings:



• Graphics: No



Specific settings:


Process Name of the process to be monitored. May be entered manually or selected via the "List" button.

Alphanumeric between 1 and255 charac-ters

Yes

Use of a regular expression. No

Case sensitive. No

Selection by process owner No

Selection according to the group that owns th process No


238

Alert threshold Number of processes found (below or above) Integer be-tween 0 and 999 999 999

Yes




• This search is based on the Unix command, "ps": for example, if you search on the terms "init" the

process "/sbin/init" will be included.

Example:

VI. Unix - Process - Memory

Objective:

To monitor the memory used by a process.

Generic settings:



• Graphics: Yes



Specific settings:




Yes


Case sensitive. No

Selection by process owner No


238

Selection according to the group that owns th process No

Add the memory of all found processes. No

Alert threshold Memory used by the process (minimum or maximum val-ues).


Yes

Unit of measurement. BytesKBMBGBTB

Yes




• This search is based on the Unix command, "ps": for example, if you search on the terms "init" the

process "/sbin/init" will be included.

• When the metrics are activated for the check, the graph value is the sum of all found processes,

even if the option “Add the memory of all found processes” is not selected.

Example:

VII. Unix - Process - Processor usage

Objective:


Generic settings:



238


• Graphics: No



Specific settings:




Yes


Alert threshold Processor used by the process (minimum or maximum val-ues) in percentage.


Yes




• This search is based on the Unix command, "top", this program must be available.

• The check collects 10 values for a process and calculates the average.

• If more than 1 process is found, each process is checked separately to the threshold. The check is

stopped when a process exceeds the threshold.

• When the metrics are activated for the check, the graph value is the sum of all found processes,

even if the option “Add the memory of all found processes” is not selected.

Example:

VIII. Unix - Disk free space

Objective:


238

To monitor the space used by system files.

Generic settings:



• Graphics: No



Specific settings:


Disks Disks to monitor.Can be entered manually or selected via the "List" button.

AllAll except Only those

Yes

Peripheral: file system. No

Alert threshold Utilization range (minimum or maximum values). Integer be-tween 1 and 999 999 999

Yes

Unit of measurement. BytesKB MBGBTB%

Yes



• System file could not be found.


Example:


238

IX. Unix - Disk mounted

Objective:

To monitor the mounted disks.

Generic settings:



• Graphics: No



Specific settings:



Alphanu-meric

Yes

Mount point: mount point of the file system. Yes

Alert threshold Utilization range (minimum or maximum values). Integer be-tween 1 and 999 999 999

Yes

Unit of measurement. BytesKB MBGBTB%

Yes



• System file could not be found.


Example:


238

X. Unix - I/O disk

Objective:

To monitor the volume of data written to and read from the disk.

Generic settings:



• Graphics: No



Specific settings:


Peripheral Physical peripheral (e.g. sda, sdb) or virtual (e.g. sda1, sdb2) to be monitored. Must be completed manually.

Yes

Traffic Data transfer type. ReadWrite

Yes

Alert threshold Range of values for usage (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes

Unit of measurement. Bytes/s KBytes/s MBytes/s GBytes/s TBytes/s

Yes

Number of times to run the check generating a value outside the range before generating a notification.


Yes


• System connectivity issues.

• The "iostat"" command is not available and must be installed.


Example:


238

XI. Unix - Inode usage

Objective:

Monitor the inode usage of a File System.

Generic settings:



• Graphics: No



Specific settings:


Disk File system to be monitored.This can be completed manually or selected via the "List" button.

AllAll exceptionOnly those

Yes

Peripheral: file system. No

Alert threshold Utilization range (minimum or maximum values). Integer be-tween 0 and 100

Yes



• The File System could not be located.


• When the inode usage of a File System is 100 %, it is impossible to create files or directories in the

File System.

Example:


238

XII. Unix - Swap usage

Objective:

To monitor the use of virtual memory.

Generic settings:



• Graphics: No



Specific settings:



Yes



Yes




Example:


238

XIII. Unix - Memory usage

Objective:

To monitor the utilization of physical memory.

Generic settings:



• Graphics: No



Specific settings:



Yes



Yes

Treat the cache and buffer as free.This option is deactivated for OSX, AIX, HPUX and BSD sys-tems.

No




Example:


238

XIV. Unix - Processor usage

Objective:

To monitor the load on the processor.

Generic settings:



• Graphics: No



Specific settings:



Yes



Yes


• Hardwares connection issues.


• This check monitors the CPU load as follows: "100 - idle."

• The alert threshold is always between 1 and 100%, no matter how many processors there are:

Example:


238

XV. Unix - Network usage

Objective:

Monitors the amount of inbound/outbound data passing through a network interface.

Generic settings:



• Graphics: No



Specific settings:


Interface Physical network interface (e.g., eth0) or virtual (e.g., bridge0) to be monitored.

Yes

Traffic Traffic type. InboundOutbound

Yes


Yes


Yes



Yes


• System connectivity issues.

• Interface could not be found.


238


• Network interfaces can be viewed via the "ipconfig" command, such as eth0, eth2, lo, etc.

Example:

XVI. Unix - Directory - Size

Objective:

Check the size of a directory, i.e. the disk space occupied by everything it contains.

Generic settings:



• Graphics: No



Specific settings:


Directory Complete path directory. Alphanumeric Yes

Alert threshold File size range (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes

Unit of measurement. ByteskBMBGBTB

Yes



238


• The directory could not be found.

• The check is based on the "du" command, the user set up for connection to the equipment must

have sufficient rights on the directory and the directories it contains.


• The value returned by the check corresponds to the disk space occupied by the content of the

directory specified in the check:

◦ All the files in it

◦ All directories and files contained in these directories

Example:

XVII. Unix - File - Count

Objective:

To monitor the number of files in a directory.

Generic settings:



• Graphics: No



Specific settings:


Directory Complete path to search for the files. Alphanumeric Yes

Files Filename.Can be truncated with the * character.

Alphanumeric Yes


Alert threshold Range for the number of files (minimum or maximum val-ues)


Yes





238


Example:

XVIII. Unix - File - Size

Objective:

To monitor the size of files stored in a directory.

Generic settings:



• Graphics: No



Specific settings:



Files Filename.Can be truncated with the * character.

Alphanumeric Yes


File size File size range (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes

Unit of measurement. ByteskBMBGBTB

Yes

Alert threshold Range for the number of files (minimum or maximum values) Integer be-tween 0 and 999 999 999

Yes





238


Example:

XIX. Unix - File - Modification date

Objective:

To monitor the modification date of files in a directory.

Generic settings:



• Graphics: No



Specific settings:



Files Filename.Regular expressions can be directly used.

Alphanumeric Yes

Modification date

Age of the file in minutes. Integer be-tween 0 and 999 999 999

Yes



Yes

Alert if no file matches the name criteria. No





Example:


238

XX. Unix - Custom command - Exit code

Objective:

To run a command or a script on the device and recover the exit code.

Generic settings:



• Graphics: No



Specific settings:


Command line Command to be run with the specified options (without line breaks).

Multiple commands can be linked using standard connectors (|, & or ;).Note : do not ending custom command with the character “;” a new sequence would be expected.

Script to be run with the complete path, e.g., "/home/exploit/script.sh".

Alphanu-meric with up to 65,535characters

Yes

Alert threshold Exit code (equals, greater than, less than, or different than) Integer be-tween 0 and 999 999 999

Yes



• The command or script could not be located or the user does not have sufficient rights to run them.


• The "Command Line" field cannot contain lines of code to be run directly.

• The command or the script are executed via the user specified in the device datasheet.


238

Example:

XXI. Unix - Custom command - Output

Objective:

Run a command on the device and retrieve the string of characters that it outputs.

Generic settings:



• Graphics: Yes



Specific settings:


Command line Command to be run with the specified options (without line breaks).

Multiple commands can be linked using standard connectors(|, & or ;).Note : do not ending custom command with the character “;” a new sequence would be expected.

Script to be run with the complete path, e.g., "/home/exploit/script.sh".

Alphanumericwith up to 65,535 char-acters

Yes

Alert threshold Search expression in the output. Alphanumeric Yes


Invert the output of the expression No



• The command or script could not be located or the user does not have sufficient rights to run them.


• The "command line" field cannot directly contain lines of code to run.

• The command or script are run via the user specified in the device datasheet.


238

Example:

XXII. Unix - Log file

Objective:

To search for a string of characters in a log file.

Generic settings:



• Graphics: No



Specific settings:


File Filename:If no other option is selected, this option must refer to a sin-gle file.Specify the directory where the file is located, e.g.: "/home/exploit/test.log". If no other option is selected, this option must refer to a sin-gle file.

Alphanumeric Yes

Filename after rotation. Alphanumeric No

The option "The filename contains date elements"allows you to include parts of the current date in the filename.

Alert threshold Terms searched using a regular expression; if found, an alertis triggered.

Alphanumeric No

Terms searched using a regular expression, with an alert be-ing triggered if they are not found.

Alphanumeric No


• The file could not be found (e.g., an issue with the directory or in the filename).

• The file could not be read (e.g., due to file corruption)


238

• The user does not have sufficient rights to access the file on this device.

Principles:

• First automatic run: when it is run for the very first time, the check checks the integrity of the file

and counts the number of lines. However, it does not check for the presence of the search terms.

When run for the first time, the check always generates a successful report, regardless of the file

content.

At the end of the verification stage, the position in the file is memorized.

• Subsequent automatic runs: when the check is run on subsequent occasions (even if the check is

deactivated or activated in the meantime) the alert checks the content that has been added since

the last time that the check ran. Once verification is complete, the position in the file is memorized.

• Run manually: If the check is not run automatically before it is run manually, the status of the check

will always be reported as successful. When it is run manually, content that has been added since

the last time the check was run manually is verified. Once verification is complete, the position in

the file is not updated. Instead, the next automatic check will verify the content that was previously

verified when the check was run manually.


• A check that is run against an empty file with a search on "Containing text" will generate a

successful report.

• The check must only be implemented on log files that are fed by data. A file that is purged after

every update (e.g., backup logs that are stored in a new file every day) or that only contain a single

value (e.g.: "OK" or "NOK","0" or "1") may not be monitored correctly. For this type of file, turn

instead to the check "Unix - Specific Command - Standard Output" and add a "more" to the file for

example.

• The field "Content not matching the pattern" will only generate an error if, when the check is run,

new lines have appeared and the search terms are not found in this new data. If, between the times

when two checks are run, there is no new data, the terms may not be present, but no error will be

generated.

• There is no need to enter search terms in brackets or quotes.

• There is no separator character, and the check uses the expression provided in its entirety. To

search for multiple terms, regular expressions must be used such as WARN.*\|ERROR.*

Examples:


238

• In the example above:

◦ The check is configured to check for the presence of the term "ERROR" in the file

"/home/exploit/test.log".

◦ When the check is run for the first time, no notification is generated.

◦ The term "ERROR" appears in the file.

◦ When the check is run for the second time, and the term "ERROR" is found, a notification is

sent.

◦ The term "ERROR" does not appear in the file on any further occasion.

◦ When the check is run for the third time, the term "ERROR" is not found and therefore no

notification is generated.

◦ In this example, the log file "file" is archived as "file_01.log," "file_02.log," and so on.

• The filename can be truncated using the * character, for example:

"/home/exploit/test*.log" will find files named "test.log" and "test1.log."

In this case, check the option "Examine the most recent file if multiple files exist with this name."

• When the file being monitored is archived:

◦ With rotation, for example:

◦ Without rotation, for example:

When the check is run following archiving, the search takes place as soon as the previous check is added

to the archive file (e.g., "test_*log" or "test_old.log"), up until the current file (e.g., "test.log").

• It is possible to specify a file with a date in its filename:


238

◦ For a filename "file_2011-11-11 17:11", specify "file_${yyyy-MM-dd HH:mm}"

◦ Fo a filename "file_Tues", specify "file_${E}"

Example:

The characters in quotes are replaced by the date and time of the check.

The date format follows the rules for the "SimpleDateFormat" Java class: see Annexes > Date and time

format.

XXIII. Unix - System load

Objective:

Monitor the system load of a device.

Generic settings:



• Graphics: No



Specific settings :


Period Select the system load for a period of minutes (standard peri-ods).

1515

Yes

Alert threshold Range for system load (minimum or maximum values).The thresholds below are generally acceptable:

• 0.70 => The system is not under load. • 1.00 => If the value is constant, the system may en-

counter problems. • 5.00 => The system may encounter serious prob-

lems. The threshold must be adapted to reflect the number of pro-cessors that the hardware has: Example: on a dual-core system, the threshold for a system not under load would be 1.40 (0.70 × 2).


Yes

Number of instances that the check may be run, returning a result outside the permitted range, before triggering the alert.


Yes



238



Example:


238

Windows

I. Pre-requisites



II. Windows - Connection test

Objective:

To monitor whether the connection to a Windows device is working.

Generic settings:



• Graphics: No



Specific settings:




• User/password issues.

• WinRM/WMI configuration issues such as port opening.


• The device must be running a Windows operating system version Windows Server 2003 or above.

Example:

III. Windows - Time offset

Objective:



238

Generic settings:



• Graphics: No



Specific settings:


Time server (NTP)




Yes


Yes




Example :

IV. Windows - Up-time

Generic settings:



• Graphics: No



Specific settings:



238

Alert threshold Time passed since the system last restarted (minimum or maximum values).

Integer be-tween 1 and 9 999

Yes

Unit of measurement. DaysHours Min-utes

Yes




Example:

V. Windows - Disk free space

Objective:

To monitor the amount of disk space taken up.

Generic settings:



• Graphics: No



Specific settings:



AllAll except Only those

Yes

Peripheral: Volume name. No


Yes

Unit of measurement. BytesKBMBGBTB%

Yes


238



• The disk could not be located.


• When disks are excluded from the selection, their presence is not monitored and therefore no alert

is generated if they are not present.

• Error "110-Internal error: Exception": see the WMI performance counters problems in Annexes part.

Example:

VI. Windows - Service status

Objective:

To monitor the status of Windows services.

Generic settings:



• Graphics: No



Specific settings:


Services Monitors all services that are set to start "Automatically." Yes

Monitor selected services.These can be entered manually or selected by the "List" button.

ID of the Windows service. Alphanumeric Yes


238

Name of the Windows service (optional). Alphanumeric No

Alert threshold The status of a service shows that it has not started.



• The service does not exist or could not be located.



• The "ID" field corresponds to the "Service name" in Windows service Properties.

• The "Name" field corresponds to the "Display name" in Windows Service Properties.

Example:

VII. Windows - Process status

Objective:

To monitor which services are active.


238

Generic settings:



• Graphics: No



Specific settings:


Process Name of the process to be monitored.The process name is not case sensitive, but it must be en-tered in full.This can be entered manually or selected by the "List" but-ton. Processes can be displayed singly or sorted by name.

Alphanumeric Yes

Alert threshold Number of processes found (minimum or maximum values) Integer be-tween 0 and 999 999 999

Yes





Example:

VIII. Windows - Process - Threads

Objective:

Monitor the number of threads for a process.

Generic settings:



• Graphics: Yes




238

Specific settings:


Process Name of the process to be monitored.The process name is not case sensitive, but it must be en-tered in full.This can be entered manually or selected by the "List" but-ton. Processes can be displayed singly or sorted by name.

Alphanumeric Yes

Alert threshold Number of threads for the process (minimum or maximum value).


Yes





• The check searches for the specified process and returns the first matching result. If multiple

processes have the same name, the check cannot be run automatically on all of them and therefore

becomes less useful.

Example:

IX. Windows - Processes - Memory

Objective:


Generic settings:



• Graphics: Yes



Specific settings:


Process Name of the process to be monitored.The process name is not case sensitive, but it must be en-tered in full.This can be entered manually or selected by the "List" but-

Alphanumeric Yes


238

ton. Processes can be displayed singly or sorted by name.

Alert threshold Memory used by the process (minimum or maximum val-ues).


Yes

Unit of measurement. BytesKBMBGBTB

Yes





• The check searches for the specified process and returns the first matching result. If multiple

processes have the same name, the check cannot be run automatically on all of them and therefore

becomes less useful.

Example:

X. Windows - Swap usage

Objective:

To monitor the usage of the swap file.

Generic settings:



• Graphics: No




238

Specific settings:



Yes

Number of consecutive instances of the check to be run be-fore triggering a report.


Yes





Example:

XI. Windows - Memory usage

Objective:

To monitor the memory usage rates.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Load range (minimum or maximum values). Integer be- Yes


238

tween 0 and 100

Number of consecutive instances of the alert to be run beforetriggering a report.


Yes





Example:

XII. Windows - Processor usage

Objective:

Monitor the processor load.

Generic settings:



• Graphics: No



Specific settings:



Yes

Number of consecutive instances of the alert to be run beforetriggering a report.

Integer be-tween 1 and

Yes


238

99





• The alert threshold is always between 1 and 100, no matter how many processors there are.

Example:

XIII. Windows - Network usage

Objective:

To monitor the usage of bandwidth by a network interface.

Generic settings:



• Graphics: No



Specific settings:


Interface ID of the network interface to be monitored. Can be entered manually or selected via the "List" button.

Alphanumeric Yes

Traffic Traffic direction. InboundOutbound

Yes

Alert threshold Range of values for usage (minimum and maximum levels) Integer be-tween 0 and 999 999 999

Yes


238


Yes

Number of consecutive checks run in excess of the threshold before generating an alert.


Yes



• The network interface could not be found.



• This check only works with a WinRM connection.

• The "Interface" field corresponds to the "Device Name" field visible in Windows:

Example:

XIV. Windows - Scheduled tasks

Objective:

To monitor the execution of scheduled tasks.

Generic settings:



238


• Graphics: No


• Available in the reports: Yes (Jobs)

Specific settings:


Task name Name of the task to be monitored.The task can be selected from the "List" button, which will display all tasks that are scheduled on the device in a new window.

Alphanu-meric

Yes

Alert threshold Search period for the scheduled task in minutes.Alert if the task is not processed during the selected period.


Yes

Alert if the task is not running when the check is processed.




• This check only works with a WinRM connection.

• The task name contains the complete path, e.g.:

"\Microsoft\Windows\CertificateServicesClient\SystemTask"

• To display the window containing the list of scheduled tasks from the "List" button, the RPC must

be active and running. In the window you can find:

◦ Exit code: There is thousands of possible return code, below three examples:

▪ 0: The task is successful

▪ 1: Error, function incorrect

▪ 2: Error, file not found

◦ Missed execution: Time between the time task was planned but did not executed and now.

Example:


238

XV. Windows - Security center

Objective:

Monitor the statuses of the Windows Security Center.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Alert if the domain network firewall is disabled Checkbox Yes

Select at least one threshold

Alert if the public network firewall is disabled Checkbox

Alert if the private network firewall is disabled Checkbox

Alert if the antivirus is inactiveAlert if the antivirus is out-of-date

Checkbox

Alert if the last antivirus scan is more than “xx” days old CheckboxInteger between 1and 365

Alert if the last antivirus update is more than “xx” days old

CheckboxInteger between 1and 365

Alert if the last Windows update is more than “xx” days old

Checkbox integer between 1 and 365




238

• The WMI AntiVirusProduct object is not available. This may occur when the Windows version is too

old (prior to Windows Server 2003).

• The Security Center is not installed or deactivated.


• The check may request on the AntiVirusProduct object. It therefore detects all antivirus products

that Windows recognizes as such.

Example:

XVI. Windows - File - Count

Objective:

Monitor the number of files in a folder.

Generic settings:



• Graphics: No



Specific settings:


Folder Disk and folder where files are to be monitored. Examples:• "C:\exploit\scripts" • "D:\"

Alphanumeric Yes

Files Filenames to search for. A single name may be specified, but it may also be truncated using the * character.To select all files in a folder, enter *.*

Alphanumeric Yes



Yes


238

999 999 999



• The disk or folder could not be located.


Example:

XVII. Windows - File - Size

Objective:

To monitor the size of files in a folder.

Generic settings:



• Graphics: No



Specific settings:



Alphanumeric Yes

Files Filenames to search for. A single name may be specified, but it may also be truncated using the * character.To select all files in a folder, enter *.*

Alphanumeric Yes

File size File size range (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes

Unit of measurement. BytesKBGBTB



Yes


238

999 999 999





Example:

XVIII. Windows - File - Creation date

Objective:

To monitor the dates when files in a folder were created.

Generic settings:



• Graphics: No



Specific settings:



Alphanumeric Yes

Files Filenames to search for. A single name may be specified, butit may also be truncated using the * character.To select all files in a folder, enter *.*

Alphanumeric Yes

Date created Date of creation of files (minimum or maximum value) in min-utes.


Yes


Yes

Alert if no files match the name criteria. No


238





Example:

XIX. Windows - File - Modification date

Objective:

To monitor the last modified date of files in a folder.

Generic settings:



• Graphics: No



Specific settings:



Alphanumeric Yes

Files Filenames to search for. A single name may be specified, butit may also be truncated using the * character.To select all files in a folder, enter *.*

Alphanumeric Yes

Last modified date

Range for permitted values of the last modified date (mini-mum or maximum values) in minutes.


Yes


Yes

Alert if no files match the name criteria. No


238





Example:

XX. Windows - Custom command - Output

Objective:

Run a command on the device and retrieve the string of characters that is output.

Generic settings:



• Graphics: Yes



Specific settings:


Command line Command to be run with the following options (with no line break). The command can be part of a scripting language such as PowerShell, Cscript, cmd DOS, etc. Multiple commands can be linked using standard connec-tors (&, &&). Scripts must be run with the complete path, e.g.: "C:\script\purge.bat". The field cannot directly contain the source code of a scriptto be run

Alphanumeric up to 65,535 characters

Yes

Arguments Arguments associated with the command are provided af-terwards (with no line break).

Alphanumeric up to 65,535 characters

Yes

Alert threshold Search expression in the output. Alphanumeric Yes


Invert the output of the expression No


238



• The script or command to be run could not be located.

• The user specified in the "Device" section does not have the necessary permissions to run the

command line or script.


• The check works with a WinRM connection to the device, but not with a WMI connection.

Example:

XXI. Windows - Log file

Objective:

To search for a string of characters in a log file.

Generic settings:



• Graphics: No



Specific settings:


File Filename:If no other selection is selected (such as a file containing a date), this name may only identify a single file.Specify the file to be monitored with its complete path, e.g., "C:\script\test.log"

Alphanumeric Yes


238

The option "The filename contains date elements" allows you to include parts of the current date in the filename.

Containing text Terms to be searched within the file that, if found, will triggeran alert.The "findstr" command is used.The search is not strict, for example: to select the words "Successfully" and "Success,"» use the expression "Suc-cess".Each term separated by a space is searched individually, forexample: entering “error” and “break” will return all lines containing “error” or “break” or both.

Alphanumeric Yes

Search for the exact character stringSelect this option to search exactly several terms

Checkbox

*Not* containingthe expressions

Regular expression on the text uploaded by the “Containing text” field.The purpose is to exclude from the results the expressions searched in this field

Alphanumeric



• The disk, folder, or file could not be located.

• Permissions issues, where the user does not have sufficient permissions over the file or the folder

where the file is located.

• Data readability issues (such as file corruption).

Principles:

• First automatic run: When the check is run for the very first time, the entire content of the file is

checked. However, it does not check for the presence of the search terms. When run for the first

time, the check always generates a successful report, regardless of the file content.

At the end of the verification stage, the position in the file is memorized.

• Subsequent automatic runs: when the check is run on subsequent occasions (even if the check is

deactivated or activated in the meantime) the check checks the content that has been added since

the last time that the check ran. Once verification is complete, the position in the file is memorized.

• Run manually: If the check is not run automatically before it is run manually, the status of the check

will always be reported as successful. When it is run manually, content that has been added since

the last time the check was run manually is verified. Once verification is complete, the position in

the file is not updated. Instead, the next automatic check will verify the content that was previously

verified when the check was run manually.


• The monitored file must use the same character encoding standard as the equipment’s operating

system or use the ASCII coding standard.

Otherwise malfunctions may occur when using the check (display problem, special character

search problems, etc.).


238

• A check that is run against an empty file with a search on "Containing text" will generate a

successful report.

• The check must only be implemented for log files that are fed by data. A file that is purged after

every update (e.g., backup logs that are stored in a new file every day) or that only contain a single

value (e.g.: "OK" or "NOK","0" or "1") may not be monitored correctly. For this type of file, turn

instead to the check "Unix - Specific Command - Standard Output" and add a "more" to the file for

example.

• The field "Content *not* matching the pattern" searches the terms returned by the search in the

“Containing text” field, in order to exclude lines containing the searched expressions from the

result.

• There is no need to enter search terms in brackets or quotes.

• Example:

In the screen capture above:

◦ The check is configured to check for the presence of the term "ERROR" in the file "C:\test.log."

◦ When the check is run for the first time, no notification is generated.

◦ The term "ERROR" appears in the file.

◦ When the check is run for the second time, and the term "ERROR" is found, a notification is

sent.

◦ The term "ERROR" does not appear in the file on any further occasion.

◦ When the check is run for the third time, the term "ERROR" is not found and therefore no

notification is generated.

• It is possible to specify a file with a date in its name:

◦ For a filename "file_2011-11-11 17:11", specify "file_${yyyy-MM-dd HH:mm}"

◦ Fo a filename "file_Tues", specify "file_${E}"

Example:

The date format follows the rules for the "SimpleDateFormat" Java class: see Annexes > Date and time

format.

XXII. Windows - IIS - Application pool status

Objective:


238

To monitor the application pool status of a IIS web server.

Generic settings:



• Graphics: No



Specific settings:


Application pools

Allows the user to select the application pools. AllExceptOnly

Yes

Alert threshold Alert if at least one application pool is inactive.


• WinRM connection issues.

• The application pool does not exist.

• « Uncaught exception fetching IIS pools » : The extension IIS monitoring needs to be installed.

Check: On the monitored server, go to « Server Manager > Roles > Web Server (IIS) », do a right-clic

on « Web Server (IIS) » and choose « Add Role Service ». In the tree the option « Managed Tools

(installed) > IIS Management Scripts and Tools (installed) » must be checked.


• The control works with a WinRM connection only.

• The pool selection is based on the name of the application pool:


238

AS400

I. Pre-requisites



II. AS400 - Connection test

Objective:

To monitor whether the connection to an AS400 machine is working correctly.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Triggers an alert if it is not possible to connect.



Example:

III. AS400 - Time offset

Objective:


Generic settings:




238

• Graphics: No



Specific settings:


Time server (NTP)




Yes


Yes




Example :

IV. AS400 - Active jobs

Objective:

To monitor the number of active jobs.

Generic settings:



• Graphics: No



Specific settings:



238

Alert threshold Permitted range for the number of active jobs (minimum or maximum values).


Yes


• Unable to connect to the AS400 machine.


• The result of the check is the same as that generated by the WRKSYSSTS command.

Example:

V. AS400 - ASP Usage

Objective:

To monitor ASP usage.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Permitted usage range (minimum or maximum values). Integer be-tween 0 and 100

Yes





Example:


238

VI. AS400 - Temp. addresses usage

Objective:

To monitor the usage of temporary addresses.

Generic settings:



• Graphics: No



Specific settings:



Yes





• When an object is created, it uses a unique, temporary address. The system has a finite number of

temporary addresses available.

Example:


238

VII. AS400 - Central unit usage

Objective:

To monitor CPU usage and to compare it to the threshold.

Generic settings:



• Graphics: No



Specific settings:



Yes

Number of instances that the check may be run, returning a result in excess of the threshold, before triggering the alert.


Yes






238

Example:

VIII. AS400 - Printer state

Objective:

To monitor the status of printers.

Generic settings:



• Graphics: No



Specific settings:


Printers Printer selection AllAll exceptOnly

Yes

Printer name(s).May be entered manually or selected via the "List" but-ton.

Alphanumeric No

Alert threshold Triggers an alert if at least one selected print queue re-ports an unexpected status.

See the list of statuses be-low.

Yes




• The result of check is the same as that generated by the WRKWTR command (if the printer is

switched on).

• Printer status:


238

Name Description

UNAVAILABLE Unavailable

POWERED_OFF_OR_NOT_YET_AVAILABLE Switched off, or currently unavailable

STOPPED Stopped

MESSAGE_WAITING In a pending status, awaiting a message

HELD Suspended

STOP_PENDING In the process of stopping

HOLD_PENDING In the process of going into suspend mode

WAITING_FOR_PRINTER Awaiting a response from hardware

WAITING_TO_START Waiting to start up

PRINTING Currently printing

WAITING_FOR_OUTQ, Awaiting the output queue

CONNECT_PENDING Awaiting a connection

POWERED_OFF Powered off

UNUSABLE Cannot be used

BEING_SERVED Undergoing maintenance

UNKNOWN Unknown

Example:

IX. AS400 - Subsystem state

Objective:

To monitor the status of sub-systems.

Generic settings:



• Graphics: No



238


Specific settings:


Sub-systems Sub-system selection AllAll exceptOnly

Yes

Sub-system name(s)May be entered manually or selected via the "List" button.

Alphanumeric No

Alert threshold Triggers an alert if at least one of the selected sub-sys-tems reports an unexpected status.

See the list of statuses be-low

Yes




• The result generated by the check is the same as that reported by the WRKSBS command.

• Sub-system statuses:

Name Description

ACTIVE Active

ENDING In the process of ending

INACTIVE Not active

RESTRICTED Restricted

STARTING In the process of starting up

UNKNOWN Unknown

Example:

X. AS400 - Problems monitoring

Objective:


238

To monitor the presence of problems in status “Not closed”.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Triggers an alert if at least one not closed problem exists. Yes



• The Cockpit user does not have the rights to access the file where the problems are stored.


• The result of the check should be the same as the DSPPRB command.

Example:

XI. AS400 - Number of jobs in a queue

Objective:

To monitor the status of a job queue and the number of jobs in this job queue.

Generic settings:



• Graphics: No



Specific settings:


Job queue Name of the job queue Alphanumeric Yes

Library Name of the library of the job queue. Alphanumeric


238

Alert threshold Alert if the job queue is in “held” status. Yes

Alert if the number of jobs in the job queue exceeds the threshold (less, greater, equal or different)




• The job queue or library was not found or the Cockpit user's rights do not allow access to it.


• The result generated by the check is the same as that reported by the WRKJOBQ command.

• Sub-system statuses:

Name Description

ACTIVE Active

ENDING In the process of ending

INACTIVE Not active

RESTRICTED Restricted

STARTING In the process of starting up

UNKNOWN Unknown

Example:

XII. AS400 - Jobs execution state

Objective:

To monitor the status of jobs.

Generic settings:



• Graphics: No




238

Specific settings:


Sub-systems Job selection AllAll exceptOnly

Yes

Job name(s).May be entered manually or selected via the "List" button.

Alphanumeric No

Alert threshold Triggers an alert if at least one selected job reports an un-expected status.


Yes




• The result generated by the check is the same as that reported by the WRKACTJOB command,

when you manage a job (hit 5) and display job status attributes (hit 1).

• Job statuses:

Name Description

ACTIVE Active

OUTQ In the outbound queue

JOBQ In the queue of jobs to be run

Example:

XIII. AS400 - Jobs status

Objective:

To monitor the status of jobs.

Generic settings:


238



• Graphics: No



Specific settings:


Jobs Job selection AllAll exceptOnly

Yes

Job name(s).May be entered manually or selected via the "List" button.

Alphanumeric No

Alert threshold Triggers an alert if at least one selected job reports an un-expected status.Select at least one status.Up to 3 statuses can be selected.


Yes




• The result generated by the check is the same as that reported by the WRKACTJOB command,

column “Status”

• Job statuses:

Name Description

BSCA The job is waiting in a pool activity level for the completion of an I/O operation to a binary synchronous device.

BSCW The job is waiting for the completion of an I/O operation to a binary synchronous device.

CMNA The job is waiting in a pool activity level for the completion of an I/O operation to a com-munications device.

CMNW The job is waiting for the completion of an I/O operation to a communications device.

CMTW The job is waiting for the completion of save-while-active checkpoint processing in an-other job.

CNDW The initial thread of the job is waiting for the handle-based condition.

CPCW The job is waiting for the completion of a CPI communications call.

DEQA The job is waiting in the pool activity level for completion of a dequeue operation.

DEQW The job is waiting for completion of a dequeue operation. For example, QSYSARB and subsystem monitors generally wait for work by waiting for a dequeue operation.

DKTA The job is waiting in a pool activity level for the completion of an I/O operation to a diskette unit.

DKTW The job is waiting for the completion of an I/O operation to a diskette unit.


238

DLYW The job is delayed. The Delay Job (DLYJOB) command delays the job for a time interval toend, or for a specific delay end time. The function field shows either the number of sec-onds the job is to delay (999999), or the specific time when the job is to start running again.

DSC The job is disconnected from a workstation display.

DSPA The job is waiting in a pool activity level for input from a workstation display.

DSPW Waiting for input from a workstation display.

END The job has been ended with the *IMMED option, or its delay time has ended with the *CNTRLD option.

EOFA Waiting in the activity level to try a read operation again on a database file after the end-of-file has been reached.

EOFW Waiting to try a read operation again on a database file after the end-of-file has been reached.

EOJ Ending for a reason other than running the End Job (ENDJOB) or End Subsystem (ENDSBS) command, such as SIGNOFF, End Group Job (ENDGRPJOB), or an exception that is not handled.

EVTW Waiting for an event. For example, QLUS and SCPF generally wait for work by waiting for an event.

GRP The job is suspended by a Transfer Group Job (TFRGRPJOB) command.

HLD The job is held.

HLDT The initial thread of the job is held.

ICFA The job is waiting in a pool activity level for the completion of an I/O operation to an inter-system communications function file.

ICFW The job is waiting for the completion of an I/O operation to an intersystem communica-tions function file.

INEL The job is ineligible and not currently in the pool activity level.

JVAA The initial thread of the job is waiting for completion of a Java program operation in the pool activity level.

JVAW The initial thread of the job is waiting for completion of a Java program operation.

LCKW The job is waiting for a lock.

LSPA The initial thread of the job is waiting for a lock space to be attached in the pool activity level.

LSPW The initial thread of the job is waiting for a lock space to be attached.

MLTA The job is waiting in a pool activity level for the completion of an I/O operation to multiple files.

MLTW The job is waiting for the completion of an I/O operation to multiple files.

MSGW The job is waiting for a message from a message queue.

MTXW The initial thread of the job is in a mutex wait. A mutex is asynchronization function that is used to allow multiple jobs orprocesses to serialize their access to shared data.

MXDW The job is waiting for the completion of an I/O operation to a mixed device file.

OPTA The initial thread of the job is waiting, in an activity level, for the completion of an I/O oper-ation to an optical device.

OPTW The initial thread of the job is waiting for the completion of an I/O operation to an optical device.

OSIW The job is waiting for the completion of an OSI Communications Subsystem/400 OSLISN,


238

OSRACS, OSRACA, OSRCV, or OSRCVA operation.

PRTA The job is waiting in a pool activity level for output to a printer to complete.

PRTW The job is waiting for output to a printer to be completed.

PSRW A prestart job waiting for a program start request.

RUN The job is currently running in the pool activity level.

SELW The initial thread of the job is in a select wait.

SEMW The initial thread of the job is waiting for a semaphore. A semaphore is a synchronization function that is used to allow multiple jobs or threads to serialize their access to shared data.

SIGS The initial thread of the job is stopped by a signal.

SIGW The initial thread of the job is waiting for a signal.

SRQ The job is the suspended half of a system request job pair.

SVFA The job is waiting in a pool activity level for completion of a save file operation.

SVFW The job is waiting for completion of a save file operation.

TAPA The job is waiting in a pool activity level for completion of an I/O operation to a tape unit.

TAPW The job is waiting for completion of an I/O operation to a tape unit.

THDW The initial thread is waiting for another thread to complete anoperation.

TIMA The job is waiting in a pool activity level for a time interval to end.

TIMW The job is waiting for a time interval to end.

Example:

XIV. AS400 - Job existence


238

Objective:

To check the existence of a job.

Generic settings:



• Graphics: No



Specific settings:


Job name Enter the name of the job to check. Alphanumeric Yes

Alert threshold Alert if the job exists when the check is executed.




Example:

XV. AS400 - *SYSOPR messages needing reply

Objective:

To monitor the presence of *SYSOPR messages awaiting a response.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Triggers an alert as soon as a *SYSOPR message is await- All Yes


238

ing a response. All exceptOnly




• The result generated by the check is the same as that reported by the DSPMSG *SYSOPR

command.

• Communication between the system, users, and programs takes place by way of messages.

*SYSOPR messages are system messages (System Operator).

Example:

XVI. AS400 - SQL query returning "OK"

Objective:

To run a SQL query to send the result (string of characters).

Generic settings:



• Graphics: No



Specific settings:


SQL Query SQL query to be run. Alphanumeric Yes




• The result is consistent with the results obtained via STRSQL.

• The table names, if qualified, must follow standard SQL syntax and not the syntax used in STRSQL,

namely: "LIB.TABLE" and not "LIB/TABLE."


238

• The tables have a specific encoding and different types. In order to avoid encoding problems, it

may be useful to use the "CAST" function to transcode the data and the "TRIM" function to remove

blank characters at the beginning and end of character strings that may disturb the result of the

query:

Example:

SELECT TRIM(CAST(objet AS CHAR(25) CCSID 819)) FROM LIB.TABLE

In this example the “CCSID 819” corresponds to the “Latin-1” countries or regions.

Search the list of CCSID values on the manufacturer's website if necessary:

https://www.ibm.com/support/knowledgecenter/

Example:


238

https://www.ibm.com/support/knowledgecenter/

vSphere - vCenter (VMWare server virtualization platform)

I. Pre-requisites



II. vSphere - vCenter - Connection test

Objective:

To monitor whether the vCenter connection is working correctly.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Triggers an alert if the connection times out.


• Username/password issues.

• Certificate issues (self-signed or expired certificates, etc.) In this case, view the equipment

datasheet under the "Monitoring" tab and check the "Trust SSL" box.


Example:

III. vSphere - vCenter - Alert monitoring

Objective:

To monitor the vCenter alerts.


238

Generic settings:



• Graphics: No



Specific settings:


Severity Severities to take into account. Green, Yel-low, Red

Yes

Type Objects types whose alerts are to be taken into account. Yes

Search terms (separated by;)

Alert selection.Select the “Other” type to go back to all the alert types thatare not in the list.

AllAll exceptOnly

Yes

Terms are searched on field “Name” of alerts.Multiple terms may be entered, provided that they are sepa-rated by the ; character.

No


Statut Exclude alerts already acknowledge in vSphere. Checkbox No







Example:


238

ESX (VMWare server virtualization platform)

I. Pre-requisites



II. ESX - Connection test

Objective:

To monitor whether the ESX connection is working correctly.

Generic settings:



• Graphics: No



Specific settings:








Example:

III. ESX - Time offset

Objective:



238

Generic settings:



• Graphics: No



Specific settings:


Time server (NTP)




Yes


Yes




Example :

IV. ESX - DataStore - Config. status

Objective:

To monitor the configuration status of DataStores.

Generic settings:



• Graphics: No




238

Specific settings:


DataStore name DataStore selection. Options Yes

Alert threshold Triggers an alert if the configuration of the DataStore is not "green."


• Unable to connect to the ESX.

• The DataStore could not be located.


• The check requires that the RPC connection to the engine must be active and properly configured.

• DataStores can have three configuration statuses:

◦ "Green" => Normal

◦ "Orange" => Warning

◦ "Red" => Error

Example:

V. ESX - DataStore - Overall status

Objective:

To monitor the overall status of Datastores.

Generic settings:



• Graphics: No



Specific settings:


DataStore name DataStore selection. Options Yes

Alert threshold Triggers an alert if the overall status of the DataStore is not "green."


238



• The DataStore could not be located.


• The check requires that the RPC connection to the engine must be active and properly configured.

• DataStores can have three overall statuses:

◦ "Green" => Normal

◦ "Orange" => Warning

◦ "Red" => Error

Example:

VI. ESX - Disk I/O

Objective:

To monitor disk I/O values.

Generic settings:



• Graphics: No



Specific settings:


Element Selection of the element to be monitored• Number of aborted commands• Number of bus resets• Mean total latency (read): in milliseconds• Mean total latency (write): in milliseconds• Mean kernel latency: in milliseconds• Mean device latency: in milliseconds• Mean queue latency: in milliseconds

Options Yes

Alert threshold Range of permitted values (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes

Number of instances that the check may be run, returning a result in excess of the threshold, before triggering the alert.


Yes


238

99




Example:

VII. ESX - Configuration status

Objective:

To monitor the configuration status of ESX.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Triggers an alert if the configuration status is not "green."



Additional informations: None

Example:

VIII. ESX - Overall status


238

Objective:

To monitor the overall status of the ESX.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Triggers an alert if the overall status is not "green."




Example:

IX. ESX - Memory usage

Objective:

To monitor the usage of memory by the ESX.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Permitted usage range (minimum or maximum values. Integer be-tween 0 and 100

Yes


238



Yes




Example:

X. ESX - Network usage

Objective:

To monitor the bandwidth usage by the ESX and to compare it to the threshold.

Generic settings:



• Graphics: No



Specific settings:


Traffic Traffic direction. InboundOutbound

Yes

Alert threshold Utilization range (minimum or maximum values). Integer be-tween0 and 999 999 999

Yes

Unit of measurement. bpskbpsMbps

Yes


238

GbpsTbps



Yes




• Information that is reported applies to the host.

Example:

XI. ESX - NIC state check

Objective:

To monitor the status of the NICs.

Generic settings:



• Graphics: No



Specific settings:


NICs Selection of NICs to monitor AllAll exceptOnly

Yes


238

NIC namesMay be entered manually or selected via the "List" but-ton.

Alphanumeric No

Alert threshold Triggers an alert if one or more NICs reports an unex-pected status.

CONNECTEDDISCONNECTED

Yes




Example:

XII. ESX - Processor usage

Objective:

To monitor the usage levels of the ESX processor.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Permitted usage range (minimum or maximum values. Integer be-tween 0 and 100

Yes


238



Yes





Example:

XIII. ESX - Uptime

Objective:

To monitor the time that has passed since the ESX started up.

Generic settings:



• Graphics: No



Specific settings:


Alert threshold Uptime (minimum or maximum values) Integer be-tween 0 and 999 999 999

Yes

Unit of measurement. DaysHoursminutes

Yes


238





Example:

XIV. ESX - VM connection state

Objective:

To monitor the connection status of VMs.

Generic settings:



• Graphics: No



Specific settings:


Virtual machines VM selection. AllAll exceptOnly

Yes

VM Name(s).May be entered manually or selected via the "List" button.

Alphanumeric No

Alert threshold Triggers an alert if at least one selected VM reports an unexpected status.

CONNECTEDDISCONNECTEDORPHANEDINACCESSIBLEINVALID

Yes



• The VM could not be found.

Additional information None

Example:


238

XV. ESX - VM power state

Objective:

To monitor the status of VMs, namely whether or not they are running.

Generic settings:



• Graphics: No



Specific settings:


Virtual machines VM selection. AllAll exceptOnly

Yes

VM Name(s).May be entered manually or selected via the "List" button.

Alphanumeric No

Alert threshold Triggers an alert if at least one selected VM reports an unexpected status.

POWERED_OFFPOWERED_ONSUSPENDED

Yes



• The VM could not be found.



238

Example:


238

Database

I. Pre-requisites

• The database must be present in the infrastructure (Infrastructure - Database management)

• Database access must be correctly configured, see FAQ document:

https://faq.cockpit-itsm.com/COCKPIT_FAQ_MONITORING_access_database_en.pdf

• The JDBC drivers corresponding to the database must be installed on the supervision engine, see

FAQ document:

https://faq.cockpit-itsm.com/

COCKPIT_FAQ_TECHNICAL_standalone_engine_management_windows_en.pdf

https://faq.cockpit-itsm.com/

COCKPIT_FAQ_TECHNICAL_standalone_engine_management_linux_en.pdf

II. DB - Connection test

Objective:

to monitor whether the connection to a database is up and running. See the document below:

Generic settings:



• Graphics: No



Specific settings:




• User/password issues

Additional information: Monitoring is available for databases in the following formats:

• DB2

• HANA

• SP Max DB

• MS SQL

• MySQL


238

https://faq.cockpit-itsm.com/COCKPIT_FAQ_TECHNICAL_standalone_engine_management_linux_en.pdf

https://faq.cockpit-itsm.com/COCKPIT_FAQ_TECHNICAL_standalone_engine_management_linux_en.pdf

https://faq.cockpit-itsm.com/COCKPIT_FAQ_TECHNICAL_standalone_engine_management_windows_en.pdf

https://faq.cockpit-itsm.com/COCKPIT_FAQ_TECHNICAL_standalone_engine_management_windows_en.pdf

https://faq.cockpit-itsm.com/COCKPIT_FAQ_MONITORING_access_database_en.pdf

• Oracle

• Pervasive SQL

• PostgreSQL

• SQLExpress

• Sybase


238

Example:

III. DB - Connection count

Objective:

To monitor the number of active connections to a database.

Generic settings:



• Graphics: No



Specific settings:


Database Database to be monitored. Yes

User The user details for the test. No

Alert threshold Permitted range for the number of active connections (mini-mum or maximum values).


Yes


• Database connection issues.


Example:

IV. DB - SQL - Row count

Objective:


238

To monitor the number of records in a table.

Generic settings:



• Graphics: No



Specific settings:



Table Table or view to be monitored. Specify the database where the table is located, e.g., table "SAPDB2.T100" where database SAPDB2 forms part of the instance specified in the "Database" field.

Alphanumeric Yes

Column Column to filter the search. Alphanumeric No

WHERE clause Filter in SQL languageExample: MSGNR = '036'

Alphanumeric No

Alert threshold Permitted range for the number of records (minimum ormaximum values)

Integer be-tween 0 and 9 999 999 999

Yes

Keep check chart results (metrics) Checkbox No



• The table or view could not be located.

• The 'WHERE' clause is incorrectly formatted or invalid.


Example:

V. DB - SQL - Query - Return integer


238

Objective:

To perform a SQL query on the database and to return the result, which must be an integer.

Generic settings:



• Graphics: Yes



Specific settings:



SQL query SQL query, which must return an integerThere is no need to terminate the query with the ";" character.

Alphanumeric Yes

Alert threshold Permitted range of values (minimum or maximum val-ues)

Integer be-tween 0 and 9 999 999 999

Yes

Keep check chart results (metrics) Checkbox No




Example:


238

VI. DB - SQL - Query - Return string

Objective:

To perform a SQL query on the database and to return a text format result.

Generic settings:



• Graphics: No



Specific settings:



SQL query SQL query that generates a text result.There is no need to terminate the query with the ";" character.

Alphanumeric Yes

Alert threshold Search terms that will generate an alert if not found.The terms provided are taken from a single block.Regular expressions may be used:The error trigger ".*error." will result in the string "Gen-eral error - please contact your system administrator." However, the error trigger "error" will not result in the string "General error - please contact your system ad-ministrator."

Alphanumeric Yes




Example:

VII. DB - MSSQL - DB Size

Objective:


238

Monitor the size of the database.

Generic settings:



• Graphics: No



Specific settings:


Instance Database instance. Yes


Alert threshold Permitted values for size (minimum or maximum values) Integer be-tween 0 and 999 999 999

Yes


Yes




Example:

VIII. DB - MSSQL - DB free space

Objective:


238

To monitor the amount of free space remaining for the database.

Generic settings:



• Graphics: No



Specific settings:




Data type Type of data to be monitored DATALOG

Yes

Alert threshold Permitted values for size (minimum or maximum values) Integer be-tween 0 and 999 999 999

Yes


Yes




Example:


238

IX. DB - MSSQL - Free space in files

Objective:

To monitor the amount of free file space available for the database.

Generic settings:



• Graphics: No



Specific settings:




Files Allows the user to select the database files to be moni-tored.

AllAll exceptOnly

Yes

Database file names. Alphanumeric No

Alert threshold Permitted utilization range (minimum or maximum values) Integer be-tween 0 and 999 999 999

Yes


Yes




Example:


238

X. DB - MSSQL - DB Backup

Objective:

Monitoring the latest backups.

Generic settings:



• Graphics: No



Specific settings:


MSSQL Server Database to be monitored. Yes

Database Selection of the databases to be monitored. All All exceptOnly

Yes

Database names.Can be entered manually or selected via the "List" but-ton.

Alphanumeric No

Save type Save type to be monitored.D: Full Database backupI: Differential databaseF: File or file groupG: Differential fileP: PartialQ: Differential partial

Checkbox Yes

Alert threshold Triggers an alert if the last backup is older than 'XX' hours

Integer be-tween 1 and 9,999

Yes




238


Example:

XI. DB - MSSQL - Log file Backup

Objective:

To monitor the latest backup records.

Generic settings:



• Graphics: No



Specific settings:


MSSQL Server Database. Yes

Database Selection of the databases to be monitored All All exceptOnly

Yes

Database names.Can be entered manually or selected via the "List" but-ton.

Alphanumeric No

Alert threshold Triggers an alert if the last backup is older than 'XX' min-utes.


Yes


238

9,999




Example:

XII. DB - MSSQL - Jobs in progress

Objective:

To manage job duration.

Generic settings:



• Graphics: No



Specific settings:



Search terms (sep-arated by;)

Job selection. AllAll exceptOnly

Yes

Job names.Multiple jobs may be entered, provided that they are sep-arated by the; character.

Alphanu-meric

No


238


Alert threshold Triggers an alert if a job remains active for more than 'XX' minutes.


Yes




Example:

XIII. DB - MSSQL - Jobs in error

Objective:

To monitor jobs that are in an error status.

Generic settings:



• Graphics: No



Specific settings:



Search terms (sep-arated by ; )

Job selection. AllAll exceptOnly

Yes

Job names.Multiple jobs may be entered, provided that they are sep-

Alphanumeric No


238

arated by the; character.


Alert threshold Triggers an alert if more than 'XX' jobs have generated er-rors since the last monitoring operation.


Yes




Example:

XIV. DB - MSSQL - Lock detection

Objective:

Monitor the presence of database locks.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Maximum number of locks. Integer be-tween 1 and 9,999

Yes


238




Example:

XV. DB - Hana - Alert monitoring

Objective:

To report alerts detected by the statistic service.

Generic settings:



• Graphics: No



Specific settings:



Checks Selection type AllAll exceptOnly

Yes

Alert IDMay be entered manually or selected via the "List" but-tonDB - MSSQL - DB backup

Integer Yes

Description of the alert.May be entered manually or selected via the "List" but-ton

Alphanumeric No

Level Alerts level to be monitored.INFOLOWMEDIUMHIGHERROR

Checkbox Yes

Triggers an alert if more than 'XX' alerts have been gen-erated since the last monitoring operation.

Alphanumericbetween 0 and 99

Yes


238




• The statistic service regularly runs monitoring operations and stores the alerts generated in the

"_SYS_STATISTICS" view. Each time the operation runs, it checks whether any new alerts have

been generated since the last monitoring operation.

• The "Run" command does not appear in the actions menu for the operation if the operation has

never run automatically.

Example:

XVI. DB - Hana - Free space on volume (LOG)

Objective:

To monitor the utilization of LOG type volumes.

Generic settings:



• Graphics: No



Specific settings:



Volumes Selection type. AllAll exceptOnly

Yes


238

Volume ID.May be entered manually or selected via the "List" but-ton

Integer yes

Volume description.May be entered manually or selected via the "List" but-ton

Alphanumeric Yes

Alert threshold Utilization threshold (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes


Yes

Number of consecutive instances of the alert to be run before triggering a report.

integer be-tween 1 and 99

No



• The volume could not be found.


• This information can be found in the “Volumes” tab of Hana Studio.

Example:

XVII. DB - Hana - Free space on volume (DATA)

Objective:

To monitor the utilization rates of DATA type volumes.

Generic settings:


238



• Graphics: No



Specific settings:



Volumes Selection type. AllAll exceptOnly

Yes

Volume ID.May be entered manually or selected via the "List" but-ton

Integer yes

Volume description.May be entered manually or selected via the "List" but-ton

Alphanumeric Yes


Yes


Yes

Number of consecutive instances of the check to be run before triggering a report.

integer be-tween 1 and 99

No



• The volume could not be found.


• This information can be found in the “Volumes” tab of Hana Studio.

Example:


238

XVIII. DB - Hana - Memory usage

Objective:

To monitor memory usage.

Generic settings:



• Graphics: No



Specific settings:



Nodes Selection type. AllAll exceptOnly

Yes

Node to be monitored, i.e., the host that is visible within SAP HANA Studio.May be entered manually or selected via the "List" button

Alphanu-meric

Yes


Yes


Yes



238


• The node could not be found.


• In the event that there are multiple nodes, the check is run on multiple nodes, such that the result is

not an average across all nodes.

Example:

XIX. DB - Hana - Free disk space

Objective:

To monitor the availability of disk space.

Generic settings:



• Graphics: No



Specific settings:



Disks Selection type. AllAll exceptOnly

yes

Path: disks to be monitored.May be entered manually or selected via the "List" button

Alphanumeric Yes

Usage type: one of three different usage types in Hana:• Data• Log

Alphanumeric No


238

• Trace


Yes


Yes



• The disk could not be found.


Example:

XX. DB - Hana - Backup status

Objective:

To monitor the status of the latest backup.

Generic settings:



• Graphics: No



Specific settings:


238



Monitoring period Backup search period in minutes. Integer be-tween 5 and 1,400

Yes




• An alert is generated when no backup is found for the specified monitoring period.

• An alert is generated when a backup found within the monitoring period shows a status other than

"Complete data backup."

Example:

XXI. DB - Hana - Archive status

Objective:

To monitor archive status.

Generic settings:



• Graphics: No



Specific settings:



Monitoring period Archive search periods in minutes. Integer be-tween 6 and 100,000

Yes

Alert threshold Number of successful archiving operations since the last monitoring operation.

Integer be-tween 0 and 999,999,999

Yes

Number of failed archiving operations since the last moni-


238

toring operation.




• The monitoring period extends back to the last monitoring operation, and this duration depends on

the run schedule.



• Successful archiving operations show a status of "successful."

Example:

XXII. DB - Hana - Savepoint monitoring

Objective:

To monitor the age of the savepoints.

Generic settings:



• Graphics: No



Specifics settings:



Alert threshold Triggers an alert if a savepoint is older than 'XX' minutes. Integer be-tween 0 et 999 999 999

Yes



238



Example:

XXIII. DB - Hana - Service status

Objective:

To monitor the status of services.

Generic settings:



• Graphics: No



Specific settings:






• This check monitors the status of all services across all nodes.

• The services relate to the different SAP HANA processes that can be viewed in the SAP HANA

Studio:

◦ daemon

◦ name server

◦ preprocessor

◦ index server

◦ statistics server

◦ xsengine

◦ compile server


238

Example:

XXIV. DB - Hana - Replication status

Objective:

To monitor replication status.

Generic settings:



• Graphics: No



Specific settings:






• This alert verifies the replication status across all nodes in the SAP HANA system.

Example:

XXV. DB - Hana - DB Threads

Objective:

To monitor the age and status of threads.

Generic settings:



238


• Graphics: No



Specific settings:



Search terms Types selection. AllAll exceptOnly

Yes

Search terms.It is possible to search for multiple search terms separately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.

Alphanu-meric

Yes


Alert threshold Generates an alert if the lock is older than 'XX' minutes. Integer be-tween 5 and 1440

Yes




• This alert verifies that threads do not retain any of the statuses listed below for longer than:

◦ SHAREDLOCK

◦ SLEEPING

◦ EXCLUSIVELOCK

• The “Exclude phantom threads” option excludes threads showed as active when they should not

be, they are known bugs listed in the OSS 1969700 note.

Example: “BackupMonitor_TransferThreads” thread in “Sleeping” status, etc.

Example:


238

XXVI. DB - Hana - Transactions blocked

Objective:

To monitor the age of locked transactions.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Generates an alert if the lock is older than 'XX' minutes. Integer be-tween 5 and 1440

Yes




• The monitoring operation reports on transactions in "M_BLOCKED_TRANSACTION" that have been

locked for more than 'xx' minutes.

Example:

XXVII. DB - Oracle - Free space in DB

Objective:

To monitor the free space available for the database.

Generic settings:



• Graphics: No



238


Specific settings:



Calculation mode Manual extension: the free space is calculated without tak-ing into account any auto-extend for the tablespaces.Automatic extension: the free space is calculated, taking into account the maximum size of any auto-extended ta-blespaces as well a the size of any tablespaces that are not in auto-extend mode.

Yes


Yes


Yes




Example:

XXVIII. DB - Oracle - ArchiveLog Mode

Objective:

To monitor whether the database is in ArchiveLog mode.

Generic settings:


238



• Graphics: No



Specific settings:






• When the Oracle database is in ArhiveLog mode, the log is retained in full and, each time a redo log

file is full, it is backed up to the archive directory. It is therefore possible to restore the file from any

time up to the moment of the incident.

• When the Oracle database is not in ArchiveLog mode, redo log files are not backed up, and are

deleted at the end of each cycle, which means that they can only be restored from the last backup

point.

Example:

XXIX. DB - Oracle - RedoLog count

Objective:

To monitor the number of redo log files that are not backed up.

Generic settings:



• Graphics: No



Specific settings:


238



Alert threshold Triggers an alert if the number of redo log files that are not backed up is above or below a threshold (minimum or maxi-mum values).


Yes




• Redo log files contain the change history for the Oracle database, saving successive changes to the

database in order to provide a restoration facility in the event of a system failure.

• If there are too many redo log files (i.e., if they are not deleted in non-ArchiveLog mode, or are not

backed up (in ArchiveLog mode) this can cause problems.

Example:

XXX. DB - Oracle - Tablespace status

Objective:

To monitor if the status of tablespaces is offline.

Generic settings:



• Graphics: No



Specific settings:



238


Tablespaces Tablespace selection AllAll exceptOnly

Yes

Name of the tablespace to be monitored.May be entered manually or selected via the "List" but-ton

Alphanumeric No



• The tablespace could not be located.


Example:

XXXI. DB - Oracle - Free space in tablespace

Objective:

To monitor the free space for tablespaces.

Generic settings:



• Graphics: No



Specific settings:



238


Calculation mode Selection of calculation mode:Manual extensionAutomatic extension

Yes


Yes

Name of the tablespace to be monitored.May be entered manually or selected via the "List" but-ton

Alphanumeric No

Alert threshold Permitted utilization threshold (minimum or maximum value)


Yes




• The tablespace could not be located.


• The following calculation modes are available:

◦ Manual extension: the check verifies the free space available to the tablespace.

◦ Automatic extension: the check verifies the free space available to the tablespace, taking into

account its maximum extension limit. If the selected tablespace is not in autoextend mode, the

check will verify the value in manual extension mode.

Example:


238

XXXII. DB - Oracle - Max. Extent

Objective:

To monitor whether a segment is attaining its MaxExtent.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Generates an alert if the number of allocatable extensions before reaching the MaxExtent of a segment is below 'XX'

Integer between 0and 999 999 999

Yes




• The alert threshold is applied for all segments (tables and indexes).

• Segments (tables and indexes) are made up from Extents (data spaces). When Extents are full of

data, the segment allocates new Extents to itself. The segments have a "Max Extent<" limit, beyond

which they cannot allocate themselves any more Extents.

• Segments are not required to have a MaxExtent, in which case they can allocate Extents to

themselves without any internal limitations.

Example:


238

XXXIII. DB - Oracle - Next Extent

Objective:

To monitor whether a segment can allocate Extents to itself.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Triggers an alert if the minimum number of extensions thatcan be allocated to a segment is below 'XX'.

Integer be-tween 0 and999 999 999

Yes




• The alert threshold is applied for all segments (tables and indexes).

• Segments (tables and indexes) are made up from Extents (data spaces). When Extents are full of

data, the segment allocates new Extents to itself.

• Extents vary in size, depending on the segment. In order to be allocated, the tablespace in which

the segment is located contiguous free space at least equal to the size of the Extent, failing which

the Extent cannot be allocated.

Example:


238

XXXIV. DB - Sybase - Monitoring engine status

Objective:

To monitor the number of engines in "online" status.

Generic settings:



• Graphics: No



Specific settings:


Sybase Server Sybase Server to be monitored. Yes

Alert threshold Triggers an alert if the number of engines in "Online" status is below 'XX':

Integer between 1 and 100000

Yes




Example:

XXXV. DB - Sybase - LOG Free Space

Objective:

To monitor the free space available to the transaction log.

Generic settings:



• Graphics: No




238

Specific settings:



Database Database selection. AllAll exceptOnly

Yes

Database names.May be entered manually or selected via the "List" button.

Alphanu-meric

No

Alert threshold Permitted threshold for LOG utilization (minimum or maxi-mum values)


Yes


Yes



• Database could not be located.


Example:

XXXVI. DB - Sybase - DB Free space

Objective:

To monitor the free space available to databases.

Generic settings:


238



• Graphics: No



Specific settings:



Databases Database selection. AllAll exceptOnly

Yes

Database names.May be entered manually or selected via the "List" but-ton.

Alphanumeric No

Alert threshold Permitted threshold for database utilization (minimum or maximum values)


Yes


Yes





Example:


238

XXXVII. DB - Sybase - LOG backup

Objective:

To monitor the age of the last successful LOG backup.

Generic settings:



• Graphics: No



Specific settings:




Yes


Alphanumeric No

Alert threshold Alert if the last successful backup is older than 'XX' hours.


Yes





• the results of database backups are stored in the "MASTER" database.

Example:


238

XXXVIII. DB - Sybase - DB backup

Objective:

To monitor the age and status of the last DB backup.

Generic settings:



• Graphics: No



Specific settings:




Yes


Alphanumeric No

Alert threshold Alert if the latest backup:• is in progress• is in an error status• Is older than 'XX' hours.


Yes





238


• The check retrieves the most recent backup for all selected databases.

• The results are stored in the "MASTER" database.

Example:

XXXIX. DB - DB2 - Lock wait

Objective:

To monitor the number and lock wait time.

Generic settings:



• Graphics: No



Specific settings:


Instance DB2 database to monitor Yes

Alert threshold Alert if :• More than “xx” locks• Accumulate more than “xx” milliseconds of

waiting time


Yes



238



• The check controls the number of locks that have occured as well as the cumulative time since the

previous check was performed.

• Both thresholds must be reached for triggering an alert.

Example:

XL. DB - DB2 - Transaction log usage

Objective:

To monitor the transaction log usage.

Generic settings:



• Graphics: No



Specific settings:


Instance DB2 database to monitor Yes

Alert threshold Permitted threshold for database utilization (minimum ormaximum values)


Yes

Unit of measurement BytesKBMBGBTB




Example:


238


238

SAP

I. Prerequisites

• The SAP instance must be present in the infrastructure (Infrastructure - SAP instance management)

• SAP instance access must be correctly configured.

II. Generic configuration alerts

Objective:

Present configuration alerts that we can encounter for all SAP type controls.

• Setting up problems of the SAP system (password, user, client, etc.).

• “JCO_ERROR_TIMEOUT”: The JCO connection does not succeed and falls in timeout, the system

did not respond.

• “Connection pool xxx is exhausted. The current pool size limit is x connections”: The threshold of

simultaneous SAP connections for the monitoring engine is reached.

Check the number of SAP type checks, schedules and hierarchy, see good practices in the

following document:

https://faq.cockpit-itsm.com/COCKPIT_FAQ_MONITORING_configuration_guide_en.pdf

If necessary, increase the threshold in the configuration of the supervision engine in expert mode.

• “Illegal argument - check.sapInstance must not be null”: Check if the equipments of the SAP

system (Central Services and Instances) are on the same monitoring engine.

• “No such function”: The module function used by the check does not exist on the SAP system or

the check is deployed on a system type that cannot execute the check.

III. SAP - Connection test

Objective:

To monitor whether the connection to a SAP instance is working correctly, returns an error, or if no

connection is possible.

Generic settings:



• Graphics: No



Specific settings:


238

https://faq.cockpit-itsm.com/COCKPIT_FAQ_MONITORING_configuration_guide_en.pdf


SAP Instance SAP Instance to be monitored. Yes


• See the generic configuration alerts section.


• To monitor all instances of a SAP ECC system, deploy a "SAP - connection test" check on each

Application Server.

Example:

IV. SAP - System up-time

Objective:

To monitor the start date of the SAP instance.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Alert if the start date for the instance is greater than or less than 'XX'.


Yes

Unit of measurement. Minuteshoursdays

Yes





238

Example:

V. SAP - Users expired (SU01)

Objective:

To monitor SAP users whose validity date has expired when the check is performed.

Generic settings:



• Graphics: No


• Available in the reports: Yes (Monitoring > Custom checks)

Specific settings:



Search terms Users selection. AllAll exceptOnly

Yes

Search terms.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.

Alphanumeric Yes


Alert threshold Triggers an alert if the number of expired users is ex-ceeded (minimum or maximum values)





• SAP users belong to an SAP system; there is no benefit in monitoring each AS individually.

Example:


238

VI. SAP - Users profil (SU01)

Objective:

To monitor SAP users according to their profiles.

Generic settings:



• Graphics: No



Specific settings:



Search terms Users selection. OnlyAll except

Yes


Alphanumeric Yes


Alert threshold Triggers an alert if the number of users with the searched profiles is exceeded (minimum or maximum values)





• SAP users belong to an SAP system; there is no benefit in monitoring each AS individually.


238

Example:

VII. SAP - License expiration

Objective:

To monitor the time remaining before the expiration of the license of an SAP system.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Triggers an alert if the licence expires in less than ‘XX’ days.


Yes




• The date “31.12.9999” is considered as an unlimited license.

Example:


238

VIII. SAP - DB - Object consistency (DB02)

Objective:

To report on objects that are missing from the DB or unknown in the ABAP dictionary.

Generic settings:



• Graphics: No


• Available in the reports: Yes (SAP Systems)

Specific settings:



Database Objects selection. AllExcluded

Yes

Search terms within the name of the objects.It is possible to exclude multiple terms of the search.Terms must be separated by the ; character.

Alphanu-meric

No

ABAP dictionary Objects selection. AllExcluded

Yes

Search terms within the name of the objects.It is possible to exclude multiple terms of the search.Terms must be separated by the ; character.

Alphanu-meric

No

Alert threshold Triggers and alert if objects are:• missing from the database• unknown in the ABAP dictionary

Yes




• Objects that trigger an alert when missing or unknown are indexes, tables, or views.

• The exclusions are done on exact terms of the objects.

• Inconsistencies that generate an error report are:

◦ Missing in the DB: the object is defined in the ABAP Dictionary but is not in the DB.

◦ Unknown in the ABAP dictionary: the object is in the DB but not in the ABAP Dictionary.


238

Example:

IX. SAP - DB - Sybase - DB Free space (DB02)

Objective:

To monitor the free space available to the database.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Permitted utilization threshold (minimum or maximum value)


Yes


Yes




• The check monitors the SAP database, not other system databases (such as the master database).

Example:


238

X. SAP - DB - Oracle - DB Free space (DB02)

Objective:

To monitor the free space available to the database.

Generic settings:



• Graphics: No



Specific settings:



Refresh data Refresh data during collection. No

Calculation mode Select the calculation mode:Manual extensionAutomatic extension

Yes


Yes


Yes




238


The following calculation modes are available:

• Manual extension: the free space is calculated, taking into account the free space available to

tablespaces (but without taking into account any tablespace auto-extension that may occur).

• Automatic extension: the free space is calculated, assuming that all tablespaces that feature auto-

extend are extended fully as well as the free space available to tablespaces that are not in auto-

extend mode.

• Refresh data:

◦ Checked: The control is based on same values which are on transaction DB02, the data update

time can be old (ex: 24h).

◦ Disabled: The control collects updated values, the execution time of the control can be longer.

Example:

XI. SAP - DB - Oracle - Tablespace Free space (DB02)

Objective:

To monitor the free space available to tablespaces.

Generic settings:



• Graphics: No



Specific settings:



238


Refresh data Refresh data during collection. No

Calculation mode Select the calculation mode:Manual extensionAutomatic extension

Yes


Yes

Tablespace names.Can be entered manually or selected via the "List" but-ton.

Alphanumeric No


Yes


Yes



• The tablespace does not exist.



◦ Manual extension: the monitoring operation verifies the free space available to the tablespace.

◦ Automatic extension: the monitoring operation verifies the free space available to the

tablespace, taking into account the maximum extension limit. If a selected tablespace is not in

auto-extend mode, the monitoring operation verifies the value in manual extension mode.

• The selected calculation method applies to all tablespaces covered by the monitoring.

• Refresh data:

◦ Checked: The control is based on same values which are on transaction DB02, the data update

time can be old (ex: 24h).

◦ Disabled: The control collects updated values, the execution time of the control can be longer.

Example:


238

XII. SAP - DB - Oracle - Backup (DB12)

Objective:


Generic settings:



• Graphics: No


• Available in the reports: Yes (Monitoring / SAP Systems / Backups)

Specific settings:



Monitoring period Backup search period in minutes Integer be-tween 6 and 100,000

Yes

Alert threshold Triggers an alert if the status of the latest backup is greater than 'XXXX'.

01359999

Yes





238

• This check verifies the occurrence of a backup in a length of time specified in the "Monitoring

period" field, ending at the time when the check is run.

• The time period indicated in the "Monitoring period" field must cover the entire backup period, e.g.,

if the backup takes place at some time between 9 p.m. and 10 p.m., the monitoring period must be

long enough to go back before 9 p.m.

• See the section "Annexes - SAP - DB - Oracle - Return Codes" to view details of return codes.

• When no backup is found during the monitoring period, an alert is triggered, reporting that there is

no backup.

Example:

XIII. SAP - DB - Oracle - Archiving (DB12)

Objective:

To report on the number and status of archives.

Generic settings:



• Graphics: No



Specific settings:




Yes

Alert threshold Number of archives Number be-tween 0 and 9,999

Yes

Return code range (minimum or maximum values). 01359999

Yes


238




• See the section "Annexes - SAP - DB - Oracle - Return Codes" to view details of return codes.

• When no archive is found in the monitoring period, an alert is triggered, reporting that no archive

was found.

Example:

XIV. SAP - DB - Oracle - DBA Planning Calendar (DB13)

Objective:

To report on the status and age of the latest DBA action.

Generic settings:



• Graphics: No


• Available in the reports: Yes (Monitoring / SAP Systems)

Specific settings:



DBA Action Select the DBA action to check. List Yes

Alert threshold DB Check status. 00000001000300059999

Yes

Maximum age of the DB check in days. Integer be-tween 0 and 9999

Yes




238


• The check will search for the most recent DBA action in SAP's DBA Calendar (DB13).

• The status must be specified as it appears in SAP's DBA Calendar:

SAP return codes Meaning

0000 Success

0001 Warning

0003 Error

0005 Error

9999 In progress

• When the searched DBA action is not found during the monitoring period, an alert is also triggered.

Example:

XV. SAP - DB - MSSQL - DB Free space (DB02)

Objective:

To monitor the free space in the database as it appears in SAP's DB02.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Minimum or maximum utilization value for the database. Integer be-tween 0 and 999 999 999

Yes

Unit of measurement. Bytes Yes


238

KBMBGBTB%




• The check returns the same information as that generated by transaction DB02; it therefore returns

the free space in the "SID" database, and the MASTER, MSDB, and other databases are not taken

into account.

Example:

XVI. SAP - DB - MSSQL - Free space in files (DB02)

Objective:

To monitor the available database file space.

Generic settings:



• Graphics: No



Specific settings:



Files File selection All Yes


238

All exceptOnly

Filenames.Can be entered manually or selected via the "List" but-ton.

Alphanumeric Yes

Alert threshold File utilization threshold (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes


Yes



• The file does not exist.


Example:

XVII. SAP - DB - MSSQL - Backup (DB12)

Objective:

To monitor whether backups are available.

Generic settings:



• Graphics: No




238

Specific settings:



Backup type Select the backup type:Full DB backupDifferential DB backupBoth

Yes

Monitoring period Monitoring period in minutes. Integer be-tween 6 and 100 000

Yes




• The check verifies whether backups are present without considering their status.

• The following backup types are identified:

◦ D => Full Database Backup

◦ I => Differential Database Backup

• Backups that are identified by the check are those of the <SID> SAP instance, and technical

databases, e.g. MASTER, are not identified.

Example:

XVIII. SAP - DB - MSSQL - Archiving (DB12)

Objective:

To monitor the number of archives.

Generic settings:



• Graphics: No



Specific settings:


238



Monitoring period Monitoring period in minutes. Integer be-tween 6 and100 000

Yes

Alert threshold Triggers an alert if there are fewer than 'XX' archiving in-stances during the period.

Integer be-tween 1 and9 999

Yes




• The check monitors whether archives are present, without considering their status.

• The following backup types are identified:

◦ L => Log Backup

• Backups that are identified by the check are those of the <SID> SAP instance, and technical

databases, e.g. MASTER, are not identified.

Example:

XIX. SAP - DB - MSSQL - Database Check (DB13)

Objective:

To monitor the age and status of the latest Database Check and to compare them to the threshold.

Generic settings:



• Graphics: No



Specific settings:




238

Alert threshold DB Check Status 0 = Failed1 = Successful

Yes

Maximum age (in days) of the latest DB Check. Integer between 0 and 999 9

Yes




• The check searches for the latest DB Check in SAP's DBA Calendar (DB13).

• When no DB Check is found in the monitoring period, an alert reports that the DB Check is missing.

Example:

XX. SAP - DB - MSSQL - Deadlocks (DB02)

Objective:

To check for the presence of deadlocks.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Alert if at least one deadlock has been generated since thelast check.





238

• The check checks whether any deadlocks have appeared since the last time the check was run.

• When the check is activated, existing deadlocks do not result in an error report.



Example:

XXI. SAP - DB - DB2 - Free space DB (DB02)

Objective:

To monitor the free space available to the DB2 database.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Triggers an alert if the free space is outside the range (minimum or maximum values).


Yes


Yes




• The check reports the free space available to the database as it appears in transaction DB02.

Example:


238

XXII. SAP - DB - DB2 - Backup (DB12)

Objective:

To check for the presence of the last backup during the specified period and its applicable return code.

Generic settings:



• Graphics: No



Specific settings:



Monitoring period Backup search period in minutes. Integer be-tween 6 and 100 000

Yes

Alert threshold Triggers an alert if the status of the latest backup is greater than 'XXXX.'


Yes




• The time period indicated in the "Monitoring period" field must cover the entire backup period, e.g.,

if the backup takes place at some time between 9 p.m. and 10 p.m., the monitoring period must be

long enough to go back before 9 p.m.

• When no backup is found during the monitoring period, an alert is triggered to report the absence of

a backup.


238

Example:

XXIII. SAP - DB - DB2 - Archiving (DB12)

Objective:

To report on the number of archives and their status.

Generic settings:



• Graphics: No



Specific settings:




Yes

Alert threshold Number of archives. Integer be-tween 1 and 9 999

Yes

Permitted return code (minimum or maximum value) Integer be-tween 1 and 9 999

Yes




• Backup statuses for the "Alert threshold" field:"

Return code Meaning

0 Successful

• When no archive is found during the monitoring period, an alert is triggered to report that no archive

has been found.


238

XXIV. SAP - DB - Hana - Backup (DB12)

Objective:


Generic settings:



• Graphics: No



Specific settings:


Database SAP instance to be monitored. Yes

Monitoring period Backup search period in minutes. Integer be-tween 6 and 1,000,000

Yes




• An alert is generated when no backup is found for the specified monitoring period.

• An alert is generated when a backup found within the monitoring period shows a status other than

"Finished successfully"

Example:

XXV. SAP - DB - MaxDB - Backup (DB12)

Objective:

To check for the presence of the last backup during the specified period and its applicable return code.


238

Generic settings:



• Graphics: No



Specific settings:



Backup type Select the backup type:Full DB backupDifferential DB backupBoth

Yes

Monitoring period Backup search period in minutes. Integer between 6and 100 000

Yes

Alert threshold Triggers an alert if the latest backup:• still running• the return code is greater than “XX”

0, 1, 2, 3 Yes



Informations complémentaires :

• Return codes details:


0 Success

1 Warning

2 Error

3 to 9998 Error with details

9999 Running

Example :

XXVI. SAP - Performance (ST03)


238

Objective:

To retrieve the response time for processes by type.

Generic settings:



• Graphics: No



Specific settings:



Job type Job type to be monitored. DIALOGUPDATESPOOLBACKGROUNDHTTPHTTPSRFC

Yes

Calculation mode Selection of the calculation mode of the average re-sponse time.

Yes

Alert threshold Triggers an alert if the average response time over the last hour is greater than 'XXX' milliseconds.


Yes

Triggers an alert if the number of steps in the last hour is greater than 'XXX'.


Number of consecutive instances of running the check greater than the threshold before sending a notification.


Yes




• The average response time is calculated as the total response time divided by the number of steps.

• The alert thresholds "Average response time" and "Number of steps" can be selected individually.

• When both alert thresholds ("Average response time" and "Number of steps") are selected, both

thresholds must be met or exceeded before an alert is triggered.

Note: it can be worthwhile to combine both alert thresholds. The "Average response time" is the

ratio between the total response time and the number of stages and therefore an instance that is

not called upon frequently (and that therefore has fewer steps) - can report a higher average

response time compared to a period of activity that generates a large number of steps.

•


238

• The check repSelecting the calculation mode:

◦ Average response time since 00h00: This is the cumulative response time since the beginning

of the day (00h00). This corresponds to the value displayed when the user arrives in transaction

ST03.

• Average response time over the previous hour: This is the response time only for the previous

hour.orts the response times recorded in ST03, and updates to the data therefore depend on the

whether or not the SAP job to collect statistics has completed.

Example:

XXVII. SAP - Waiting work processes (SM50)

Objective:

To monitor the availability rates of work processes.

Generic settings:



• Graphics: No



Specific settings:



Process type Type of process to be monitored. All typesDIAUPDBGDSPOUP2

Yes

Instances SAP Instances selection. AllAll expectedOnly

Yes


238

Calculation mode Per application server: The availability rate of work pro-cesses is calculated separately on each application server.

For the whole SAP system: The availability rate of work processes is calculated with all the applications server of the SAP system.

Yes

Alert threshold Triggers an alert if the percentage of processes in 'Wait-ing'' status is below 'XX' %.


Yes




• A work process is considered to be available in when its status is "Waiting".

• Regardless the calculation mode, the check controls work processes on all Application Server

selected in “Instances” field, and there is therefore no benefit in monitoring each AS individually.

Example:

XXVIII. SAP - Work processes in error (SM50)

Objective:

To monitor work processes in an error state.

Generic settings:



• Graphics: No


238



Specific settings:



Process type Type of process to be monitored. All typesDIAUPDBGDSPOUP2

Yes

Error type Select the statuses in error to be taken into ac-count.

StoppedOn hold with PRIV reasonreserv.

Yes

Alert threshold Triggers an alert if the number of work processes in 'Error'' status is above 'XX'.

Integer between 0 and 99

Yes




• Work processes in error of all Application Server are summed and evaluated at the alert threshold.

• A work process with an “On Hold” status and a “PRIV” reason is conisdered as a work process in

error.

Example:

XXIX. SAP - Lock entries (SM12)

Objective:

To monitor the age of locked statuses.

Generic settings:


238



• Graphics: No



Specific settings:



Client Check “All clients” or precise the client 'XXX' to be moni-tored.

Integer be-tween '000' and '999'

Yes

Search terms Users selection. AllAll exceptOnly

Yes


Alphanumeric No


Search terms Tables selection. AllAll exceptOnly

Yes

Search terms.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms is found. Terms must be separated by the ";" character.

Alphanumeric No

Use of regular expression No

Alert threshold Triggers an alert if entries have been present for more than 'XX' hours.





• The check reports on blocked entries on all Application Servers within an SAP system; there is no

benefit in monitoring each AS individually.

Example:


238

XXX. SAP - Update status (SM13)

Objective:

To monitor the status of update processes.

Generic settings:



• Graphics: No



Specific settings:





• “Error fetching data from CCMS”: The update status is not present in the CCMS (RZ20), see the

additional information below.


238


• The function module used in the check returns the status of the update: active / inactive.

• If the function module mentioned above does not exist, the check monitors update activity by

retrieving the value from the CCMS (RZ20) and notifies an error if the update is inactive.

In order for the check to operate, the update status must be present in the CCMS (RZ20). it can be

viewed in "Change" mode within the CCMS.

Example:

If the update status is not found, it must be added by running the "RS_UPDATE_STARTUP" program

(SM37).

Example:

XXXI. SAP - Updates in error (SM13)

Objective:

To check for the presence of update errors.

Generic settings:



• Graphics: No



Specific settings:



238


Monitoring period Selection of the monitoring period:Since the last checkOver the course of 'XX' minutes

Integer be-tween 999 999 999 et 999 999 999

Yes

Search terms Update selection. AllAll exceptOnly

Yes

Search terms on the Update Server Name.

It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.

Alphanumeric Yes



Yes

Search terms on the TCODE field (transaction code).


Alphanumeric Yes



Yes

Search terms on the Module Function Name.


Alphanumeric Yes


Alert threshold Triggers an alert if more than 'XX' updates have gener-ated an error since the last check.


Yes




• The check checks for updates that have generated an error in the update table.

• It checks updates that have occurred since the last check and prior to the current check.

• When it is run for the first time, the check does not address any prior updates that have generated

an error.




238

• The check monitors all updates, regardless of the SAP instance where they are run. There is

therefore no benefit in implementing individual checks for each instance and a single check is

sufficient for an entire SAP system.

• The control monitors the updates in error from all clients.

Example:

XXXII. SAP - Dump count (ST22)

Objective:

To monitor memory dumps.

Generic settings:



• Graphics: No




238

Specific settings:




Integer be-tween -2147483648 et 2147483647

Search terms Message selection. AllAll exceptOnly

Yes


Alphanumeric Yes


Alert threshold Alerts if more than 'XX' memory dumps have occurred during the monitoring period.


Yes




• The check monitors all memory dumps, regardless of the SAP instance where they are performed.

Accordingly, there is no benefit in monitoring each instance individually, and a single check is


• The control monitors dump memory from all clients.

• The following search modes are available:

◦ Since the last check: The check monitors the log files, monitoring memory dumps that occur

between the last check and the current check.

When the check is first activated, any memory dumps that occurred previously are not taken

into consideration.

If the check is switched on or off, memory dumps that occur during the process of switching

the check on or off are reported.

The "Run" command does not appear in the actions menu for the operation if the operation has


◦ Over the course of 'XX' minutes: The check reports on memory dumps that have occurred

during the specified time.

This configuration is most suitable for monitoring the frequency of memory dumps.

Example:


238

XXXIII. SAP – Batch Input in error (SM35)

Objective:

To monitor Batch Input in error.

Generic settings:



• Graphics: No



Specific settings:



Search terms Name selection. AllAll exceptOnly

Yes


Alphanumeric Yes



238

Alert threshold Alerts if more than 'XX' Batch Input are in error since the last check.


Yes




• The check monitors all Batch Input, regardless of the SAP instance where they are performed.

Accordingly, there is no benefit in monitoring each instance individually, and a single check is


• The check monitors as the log files, monitoring Batch Input that occur between the last check and

the current check.

When the check is first activated, any Batch Input that occurred previously are not taken into

consideration.

If the check is switched on or off, Batch Input that occur during the process of switching the check

on or off are reported.



• Batch Input considered in error have the “E” status.

Example:

XXXIV. SAP - Jobs ready (SM37)

Objective:

To check for jobs that are in "ready" status.

Generic settings:



238


• Graphics: No



Specific settings:



Alert threshold Triggers an alert if one or more jobs are in "ready" sta-tus for more than 'XX' minutes.





• The check searches for all SAP jobs in "ready" status, regardless of their date. This is equivalent to

a search in SM37 with:

◦ * for the job name and user name.

◦ no date or time

◦ status "Ready" checked.

• The check processes all jobs, regardless of the SAP instance where they are scheduled.

Accordingly, there is therefore no benefit in setting up one check per instance and a single check is


• The control monitors the jobs from all clients that the user – filled in the SAP System – is accessing.

Example:

XXXV. SAP - Intercepted jobs (SM37)

Objective:

To check for jobs that are in "intercepted" status.

Generic settings:



• Graphics: No


238



Specific settings:




Integer be-tween 999 999 999 et 999 999 999

Yes

Search terms Job name selection. AllAll exceptOnly

Yes


Alphanumeric No


Search terms Job user selection. AllAll exceptOnly

Yes


Alphanumeric No


Alert threshold Triggers an alert if more than 'XX' jobs are running. Integer be-tween 1 and 9 999

Yes




• The check searches for all SAP jobs in "Intercepted" status on the check period.





Example:


238

XXXVI. SAP - Jobs in process (SM37)

Objective:

To monitor the time taken by active jobs.

Generic settings:



• Graphics: No



Specific settings:




Yes


Alphanumeric No



Yes

Search terms. Alphanumeric No


238



Alert threshold Triggers an alert if more than 'XX' jobs are running. Integer be-tween 1 and 9 999

Yes

Triggers an alert if jobs are running for more than 'XX'minutes.









Example:

XXXVII. SAP - Jobs in error (SM37)

Objective:

To manage jobs that have been aborted.


238

Generic settings:



• Graphics: No



Specific settings:




Integer be-tween 999 999999 et 999 999 999

Yes


Yes


Alphanumeric Yes



Yes


Alphanumeric Yes


Alert threshold Triggers an alert if more than 'XX' jobs have generated errors since the last check.


Yes




• The check searches for all SAP jobs that are shown as having been "aborted" since the last check.







238


Example:

XXXVIII. SAP - Job finished (SM37)

Objective:

To monitor finished jobs.

Generic settings:



• Graphics: No


• Available in the reports: Yes (SAP Systems / Jobs)

Specific settings:




Yes


Alphanumeric Yes



238


Yes


Alphanumeric Yes


Alert threshold Triggers an alert if fewer than 'XX' jobs have run cor-rectly during the monitoring period.


Yes

Period in minutes. Integer be-tween 1 and 1440

Yes




• The check searches for all SAP jobs specified in the "Job name" field showing a "Completed"

status during the specified period.

• The check processes all jobs, regardless of the SAP instance where they are scheduled. There is

therefore no benefit in implementing individual check for each instance and a single check is



• The "Monitoring period" field must encompass the start time of the job for it to be included in the

search.

• When the check results in an error, the log contains the end times and status of jobs that are found.

In the example below, the check found four jobs instead of 'XX' jobs that were being searched:

• The statuses are:

◦ F = Finished

◦ A = Cancelled / Aborted

◦ R = Running

◦ S = Released

◦ Y = Ready

◦ Z = Active


238

In the example below, the job does not have an end date and the status is "Released":

Exemple:

XXXIX. SAP - Process chain in progress (RSPCM)

Objective:

To monitor the running process chains.

Generic settings:



• Graphics: No



Specific settings:

Parameter Information Value Mandatory

SAP instance SAP instance to be monitored. Yes

Search terms Process chain selection. AllAll exceptOnly

Yes

Search terms.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms

Alphanumeric No


238

is found. Terms must be separated by the ";" character.


Alert threshold Triggers an alert if more than 'XX' process chains are running (minimum or maximum value)


Yes





• The control checks all running process chains without considering start time.

Example :

XL. SAP - Process chain in error (RSPCM)

Objective:

To monitor process chains that are in an error state.

Generic settings:



• Graphics: No



Specific settings:



Search terms Process chain selection. All Yes


238

All exceptOnly

Search terms.It is possible to search for multiple search terms separately, but the search will terminate if one of theterms is found. Terms must be separated by the ";" character.

Alphanumeric Yes


Alert threshold Triggers an alert if more than 'XX' process chains have generated errors since the last check.

Integer between 0 and 999 999 999

Yes




• The check searches all process chains that have generated errors since the last check.



Example:

XLI. SAP - Process chain finished (RSPCM)

Objective:

To monitor finished process chains.

Generic settings:



• Graphics: No

• Dual threshold : No

• Available in the reports: Yes (SAP Systems / Jobs)


238

Specific settings:

Settings Information Value Mandatory

SAP instance SAP to be monitored. Yes

Check period Selection of the monitoring period:Since the last checkOver the course of 'XX' minutes

Yes

Search terms Process chain selection. AllAll exceptOnly

Yes

Search terms.It is possible to search for multiple terms separately, but the search will terminate if one of the terms is found. Terms must be separated by the ";" character.

Alphanumeric No

Use of a regular expression No

Alert threshold Triggers an alert if less than 'XX' process chains fin-ished during the check period.

Integer between0 and 999 999 999

Yes

Period in minutes. Integer between1 and 1440




• The check searches all process chain in error since the last check.

• When the check period is "Since the last check", the "Run" command does not appear in the

actions menu.

Example:

XLII. SAP - RFC destination status (SM59)

Objective:

To monitor the availability of RFC destinations.


238

Generic settings:



• Graphics: No



Specific settings:



RFC Destination Name of the RFC DestinationMay be entered manually or selected via the "List" but-ton.Case sensitive.

Alphanumeric Yes

TREX Destination No




• To monitor a TCPI/IP TREX destination, check the option “TREX Destination”.

Example:

XLIII. SAP - APO Live Cache status (LC10)

Objective:

To monitor the activity of the APO Live Cache.

Generic settings:



• Graphics: No




238

Specific settings:






Example:

XLIV. SAP - Bridge status (SMGW)

Objective:

To monitor the status of gateways.

Generic settings:



• Graphics: No



Specific settings:



Connections to gateways

Gateway selection. May be entered manually or selected via the "List" but-ton.

AllAll exceptOnly

Yes

Gateway ID(s). Alphanumeric Yes

Alert threshold Triggers an alert if at least one connection shows a sta-tus other than 'FREE' or 'CONNECTED.





238

Example:

XLV. SAP - Global setting status (SE06)

Objective:

To monitor the “Global Setting” parameter of the SAP transaction “SE06 – System Change Options”.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Alert if the global setting parameter is “Modifiable”




Example:


238

XLVI. SAP - Client status (SCC4)

Objective:

To manage the level of client protections.

Generic settings:



• Graphics: No



Specific settings:



Client Client 'XXX' to be monitored. Integer be-tween '000' and '999'

Yes

User User selection. AllAll exceptOnly

Yes

Search terms on the names of users who last changedclients.

It is possible to search for multiple search terms separately,but the search will terminate if one of the terms is found.Terms must be separated by the ; character.

Alphanu-meric

No


Alert threshold Triggers an alert if Changes and Transports for Client-Spe-cific Objects has a value below:

• “0”: Changes without automatic recording• “1”: Automatic recording of changes• “2”: No changes allowed• “3”: Changes w/o automatic recording, no trans-

ports allowed

Yes

Triggers an alert if the protection level of copies of the client is below 'X':

• “2”: No overwriting, no external availability• “1”: No overwriting

Integer '1' or '2'

Triggers an alert if Cross-Client Object Changes has a value below:

• “0”: Changes to Repository and cross-client Cus-tomizing objs

• “1”: No changes to cross-client Customizing ob-jects

• “2”: No changes to Repository objects• “3”: No changes to Repository and cross-client

Customizing objs


238

Triggers an alert if the CATT and eCATT Restrictions has a different value of:

• eCATT and CATT Not Allowed• eCATT and CATT Allowed• eCATT and CATT Only Allowed for ‘Trusted RFC’• eCATT Allowed, but FUN/ABAP and CATT not Al-

lowed• eCATT allowed, but FUN/ABAP and CATT only for

‘Trusted RFC’




• Elements that are monitored correspond to the fields contained within the SCC4 transaction within

SAP. In the text below, " Cockpit IT Service Manager field => field within SAP SCC4:"

◦ the client's dependent objects are modifiable => Modifications and transfers of dependent

objects

◦ inter-client objects are modifiable => Modification of inter-client objects

◦ the protection level of copies of the client is below 2 => Protection: client copy protection and

comparison tool

◦ CATT and e-CATT launches are permitted => Restrictions when CATT and e-CATT are launched

Example:

XLVII. SAP - Trace status (ST05)

Objective:

To monitor the status of system traces and to generate a notification if they are active.

Generic settings:


238



• Graphics: No



Specific settings:



Alert threshold Triggers an alert if system traces are active. Yes




• The check provides an error notification when at least one system trace shows an "On" status. All

types of trace are included in the search (including SQL Trace, Enqueue Trace, etc.)

Example:

XLVIII. SAP - Syslog (SM21)

Objective:

To search for messages in the Syslog (SM21).

Generic settings:



• Graphics: No



Specific settings:



Monitoring period Select the search mode:Since the last monitoring activity

Yes


238

Over the last 'XX' minutes

Search terms Message selection:Inclusive: all messages containing at least one of the terms.Exclusive: any message not containing any of the terms.

ContainingNot contain-ing

Yes


Alphanumeric Yes


Alert threshold Triggers an alert if more than 'XX' messages generated during the monitoring period match the criteria.


Yes




• The check searches for terms on redo logs of all SAP instance. Accordingly, there is therefore no

benefit in setting up one check per SAP instance, a single check is sufficient for an entire SAP

system.

• The check will report on Syslog messages from all clients.

• Threshold: A message (or a line in the redo log) containing several searched terms distinctly is just

counted one time.


◦ Since the last monitoring activity: The check scans all messages that have appeared since the

last check, even in the event that the check has been switched off and switched back on again.

When the check is first activated, it will not report on prior messages.



◦ Over the last 'XX' minutes: the check scans all messages that have appeared over the specified

period (in minutes) immediately preceding the check being run.

Example:


238

XLIX. SAP - Prints in process (SP01)

Objective:

To monitor the presence and the duration of spool jobs in process.

Generic settings:



• Graphics: No



Specific settings:



Status type Selection of the type of status to be taken into account. BothProcessingWaiting

Yes

Alert threshold Triggers an alert if more than 'XX' prints are running. Integer be-tween 1 and 9 999

Yes

Triggers an alert if prints are running for more than 'XX'minutes.

Integer be-tween 1 and 3 000.




• The check will report on spools from all clients.

Example:

L. SAP - Prints in error (SP01)

Objective:

To monitor the presence of spool jobs that have generated errors.


238

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Triggers an alert if more than 'XX' print jobs have gener-ated an error since the last check.


Yes




• "Problematic" print jobs are not identified by the check.

• The check will report on spools from all clients.



Example:

LI. SAP - qRFC - Output - Queue status (SMQ1)

Objective:

To monitor the presence of outbound queues in an error state.

Generic settings:



• Graphics: No




238

Specific settings:



Queue Queue selection. AllIncludedExcluded

Yes

Search terms within the queue name(s).It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.

Alphanumeric No


Status Status selection. AllIncludedExcluded

Yes


Alphanumeric No


Alert threshold Triggers an alert if at least 'XX' queues within the selec-tion are in an error state.


Yes




• A notification is triggered when at least one of the queues being searched is in an error state,

regardless of the date.

• A search on a missing queue will not generate a notification of success, because it is not in an error

state

• The check monitors queues from all clients.

Example:


238

LII. SAP - qRFC - Output - Flow error (SMQ1)

Objective:

To monitor the presence of flow errors in outbound queues.

Generic settings:



• Graphics: No



Specific settings:




Yes


Alphanu-meric

No


Alert threshold Triggers an alert if at least 'XX' flows in the selection have been in an error state since the last time the check was run.

Integer be-tween 1 and1,000

Yes




• The flows considered in error have the following statuses:

◦ SYSFAIL

◦ CPICERR

◦ RETRY

◦ ARETRY

◦ ANORETRY

• All flows in an error state will trigger a notification, regardless of date.

• A search on a queue that does not appear but which is not in an error state will result in a

successful report.

• The check will report on flows from all clients.




238

Example:

LIII. SAP - qRFC - Output - Flow on hold (SMQ1)

Objective:

To monitor the age of outbound queues.

Generic settings:



• Graphics: No



Specific settings:



Destination This field is used when executing the function module, the destination can truncated by the right:“ * ”: Search on all destinations“ DEST* “: Search all destinations starting with “DEST”“ *DEST* “: This search will not succeed

Yes


Yes


Alphanumeric No


Alert threshold Triggers an alert if at least 'XX' flows have been present for more than 'XX' minutes/hours.


Yes




238


• More than 20,000 flows are found during the search.


• A search on a destination that does not exist will be a success.

• A search on a missing queue will generate a report of a successful outcome.

• The flows on hold can be very numerous (several million) and uploading all the information can

cause timeouts and load the engine. This is why a setting paramerter alert goes up when more than

20,000 flows are found. It is better to create several checks (one for each destination to be

monitored) than a single check that will cover all destinations.


Example:

LIV. SAP - qRFC - Input - Queue status (SMQ2)

Objective:

To monitor the presence of inbound queues that are in an error state.

Generic settings:



• Graphics: No



Specific settings:




Yes

Search terms within the queue name(s).It is possible to search for multiple search terms sepa-

Alphanumeric No


238

rately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.



Yes


Alphanumeric No


Alert threshold Triggers an alert if at least 'XX' queues within the selec-tion are in an error state.


Yes




• The flows considered in error have the following statuses:

◦ SYSFAIL

◦ CPICERR

◦ RETRY

◦ ARETRY

◦ ANORETRY

• A notification will be generated when at least one of the selected queues is in an error state ,

regardless of the date.

• Searching on a queue that does not appear, but which is also not in an error state, will generate a

report of a successful outcome.


Example:

LV. SAP - qRFC - Input - Flow error (SMQ2)


238

Objective:

To monitor the presence of flows in an error state in inbound queues.

Generic settings:



• Graphics: No



Specific settings:




Yes


Alphanumeric No


Alert threshold Triggers an alert if at least 'XX' flows in the selection have been in an error state since the last time the check was run.


Yes




• An alert is triggered when at least one flows is in an error state among the selected queues.

• Searching on a queue that does not appear, but which is also not in an error state, will generate a

report of a successful outcome.


Example:

LVI. SAP - qRFC - Input - Flow on hold (SMQ2)


238

Objective:

To monitor the age of flows in inbound queues.

Generic settings:



• Graphics: No



Specific settings:




Yes


Alphanumeric No


Alert threshold Triggers an alert if at least 'XX' flows have been present for more than 'XX' minutes/hours.


Yes





• A search on a missing queue will generate a report of a successful outcome.


Example:


238

LVII. SAP - tRFC in error (SM58)

Objective:

To monitor the status of tRFC (SM58) transactions.

Generic settings:



• Graphics: No



Specific settings:



User User selection. AllIncludedExcluded

Yes

Search terms within the usernames.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.

Alphanumeric No

Recipient Recipient selection. AllIncludedExcluded

Yes

Search terms within recipients.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms is found. Terms must be separated by the ; character.

Alphanumeric No

Alert threshold Triggers an alert if more than 'XX' tRFC transactions have been in an error state since the last check.


Yes




• The check verifies the status of the RFC call status, and only reports on tRFC transactions that have

entered into an error state since the last check.



• The statuses of tRFC transactions that are treated as errors are as follows:

◦ SYSFAIL

◦ CPICERR


238

• The check monitors the tRFC transactions from all clients.

Example:

LVIII. SAP – tRFC on hold (SM58)

Objective:

To monitor the status of tRFC (SM58) transactions.

Generic settings:



• Graphics: No



Specific settings:



User User selection. AllIncludedExcluded

Yes

Search terms within the usernames.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms isfound. Terms must be separated by the ; character.

Alphanumeric No

Recipient Recipient selection. AllIncludedExcluded

Yes

Search terms within recipients.It is possible to search for multiple search terms sepa-

Alphanumeric No


238

rately, but the search will terminate if one of the terms isfound. Terms must be separated by the ; character.


Yes

Search terms within status.It is possible to search for multiple search terms sepa-rately, but the search will terminate if one of the terms isfound. Terms must be separated by the ; character.

Alphanumeric No

Alert threshold Triggers an alert if more than 'XX' tRFC transactionshave been in an error state since the last check.


Yes




• The check verifies the table of the RFC calls and reports tRFC transactions present.

• The check monitors the tRFC transactions from all clients.

Example:

LIX. SAP - Transmission requests (SOST)

Objective:


238

To monitor the status of send requests (SOST).

Generic settings:



• Graphics: No



Specific settings:



Send method Selection of the send method. All typesFaxE-mailX.400SAP OfficePager (SMS)Printer

Yes

Alert threshold Triggers an alert if more than 'XX' messages have been in an error state since the last check.


Yes




• The check monitors the send table, and reports any error messages that have been triggered since

the last check.



• Messages that can be viewed in the send table are those that apply to the user and client specified

in the SAP instance.

Example:

LX. SAP - Idocs (WE05)


238

Objective:

To monitor IDOC status (WE05).

Generic settings:

• Equipment availability : Yes

• Reverse status : No

• Graphics : No



Specific settings:


SAP instance SAP Instance to be monitored. Yes

Direction Idoc way. InboundOutboundBoth

Yes

Check period Since the last checkIn the last 'XX' minutes

Yes

Search partner Emitter / Receiver partner type filter AllIncludedExcluded

Yes

Search terms.It is possible to search for multiple terms separately. Terms must be separated by the “;” character.

Alphanumeric No

Search terms with a regular expression No

Search basic Basic type filter AllIncludedExcluded

Yes

Search terms.It is possible to search for multiple terms separately. Terms must be separated by the “;” character.

Alphanumeric No


Search Message Message type filter. AllIncludedExcluded

Yes

Search terms.It is possible to search for multiple terms separately, but the search will terminate after the first occurrence. Terms must be separated by the “;” character.

Alphanumeric No


Exit code Exit code filter. AllIncludedExcluded

Yes

Search terms.It is possible to search for multiple terms separately, but the search will terminate after the first occurrence. Terms must be separated by the “;” character.

Alphanumeric No


238

Alerts threshold Permitted number of Idoc range (minimum or maximum values)


Yes

Configuration Alerts :


Additional information :

• This check only considers Idocs in the SAP client of the current session.

• The log of the check shows the informations in the following order:

◦ ID

◦ Message type

◦ Return code

◦ Date and time of creation

◦ Basic type

◦ Emitter partner

◦ Receiver partener

Example :


238

LXI. SAP - Transports statuses (STMS)

Objective:

To monitor transports statuses (STMS).

Generic settings:

• Equipment availability : no

• Reverse status : No

• Graphics : No



Specific settings:


SAP instance SAP Instance to be monitored. Yes

System SAP System SID (System Identifier) to check. Alphanumeric Yes

Direction Transports way. InboundOutboundBoth

Yes

Alerts threshold Threshold permitted before triggering the alert (maxi-mum).

0000, 0004, 0008

Yes

Configuration Alerts :


Additional information :

• This check controls the history of Imports or Exports transports that have occurred since the last

execution check.

Example :

LXII. SAP - XML Messages monitoring (SXMB_MONI)

Objective:

To monitor the status of XML messages (SXMB_MONI).


238

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Selection of error types to search for. All errorsSystem errorApplication error

Yes




• The check will report on the following errors:

◦ "System error" statuses:

▪ System Error - Manual Restart Possible

▪ System Error - After Automatic Restart

▪ System Error (WS)

▪ System Error - Restart Not Possible

◦ "Application Error" statuses:

▪ Application Error - Manual Restart Possible

▪ Application Error - After Automatic Restart

▪ Application Error (WS)

▪ Application Error - Restart Not Possible

• The "All errors" status will report on all error statuses, both "System Errors" and "Application

Errors."



Example:


238

LXIII. SAP - NetWeaver Gateway - Error log

Objective:

Check the presence of error messages in the transaction “/IWFND/ERROR_LOG”.

Generic settings:



• Graphics: No


• Available in the reports: Yes (Daily reports > Status of custom checks)

Specific settings:



Alert threshold Alert if there are error messages in the log since thelast execution of this check.




Example:

LXIV. SAP - CCMS Monitor (RZ20)

Objective:

To detect alerts triggered in the CCMS (RZ20).

Generic settings:



• Graphics: No



Specific settings:


238



Monitoring infra-structure

Selection of the motoring infrastructure.May be entered manually or selected via the "List" button.

Yes

Monitor Monitor selectionMay be entered manually or selected via the "List" button.

Yes

Alert threshold The check triggers a notification when a message is sent to the monitor at any alert level (1 - yellow or 2 - red).



• The Ensemble monitor hierarchy / Monitor could not be found.


• The monitoring infrastructure is equivalent to the root of the hierarchy.

• he monitor corresponds to the level directly below the monitoring infrastructure:

• All control points beneath the monitor can trigger an alert. In order to target a specific control point,

you must create a "monitoring infrastructure" hierarchy and attach the alert to the hierarchy.



Example:


238

JAVA application - JMX

I. Prerequisites

• The application must be present in the infrastructure (Infrastructure - JAVA application

management)

• Application access must be correctly configured.

II. JMX - MBean request

Objective:

Monitor the attribute value of a MBean object.

Generic settings:



• Graphics: Yes


• Available in the reports: Yes

Specific settings:


Java Application Java application to be monitored. Yes

Object name Full name of the object to which the attribute belongsEx: com.koaly:type=checkScheduler.scheduledExecutor

Yes

Attribute name Name of the attribute whose value is to be checked Yes

Alert threshold Validity range (minimum, maximum or different from). Integer be-tween 0 and 999 999 999

Yes

Value “true” or “false”. Boolean Yes

Value returned (different or contains) Alphanumeric Yes

Number of times to run in excess of the threshold before generating an alert.


Yes

Do not raise an alerte No


• Issues when connecting to the Java application.

• The object or the attribute does not exist.


238


• The alert threshold type is automatically displayed according to the returned value type:

◦ Integer

◦ Boolean

◦ Alphanumeric

• The option “Do not raise an alert” can be used when you just want a graph without alert.

• The option “Keep the chart result (metrics)” is available only for numerical value.

• In the field “Object name” you must incidate the full name of the object. To search this object it is

possible to use a software like “VisualVM” and follow steps below:

◦ Connect to the JMX application with VisualVM (local or remote connection):

◦ In the Mbeans tree search for the MBean you want to monitor:

◦ In the MBean properties go to the “Metadata” tab and take the full value of the “ObjectName”

field, this string of characters must be indicated in the “Object name” field o fthe check:


238

◦ In the check configuration, click on the list button to display the popup, enter the full name of

the object then click on the “Search” button, the list of attributes of the object and their value

appears:

◦ Select the attribute to be checked and close the popup by clicking on “Select”.

Example :


238

III. JMX - CPU Usage

Objective:

To monitor CPU usage by the Java application.

Generic settings:



• Graphics: No



Specific settings:


Java application Selection of the Java application. Yes

Alert threshold Range of usage levels (minimum or maximum values). Integer be-tween 0 and 100

Yes

Number of instances that the check may be run, returning a result in outside the range, before triggering the alert.

Integer be-tween 1and 99

No


• Unable to connect to the Java application.


Example:


238

IV. JMX - Heap memory usage

Objective:

To monitor the amount of memory allocated to the JVM.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Range of usage levels (minimum or maximum values). Integer be-tween 0 and 100

Yes



No




• The check applies to the maximum memory allocated to the JVM and not the total memory of the

device.

Example:


238

V. JMX - Thread count

Objective:

To monitor the number of threads used by the Java application.

Generic settings:



• Graphics: No



Specific settings:



Alert threshold Range of usage levels (minimum or maximum values). Integer be-tween 0 and 999 999 999

Yes



No




Example:


238

Email

Objective:

To search for messages in a mailbox and to trigger an alert if certain criteria are met.

Generic settings:



• Graphics: No



Specific settings:


Protocol Protocol selection. POP3POP3 (SSL)IMAPIMAP (SSL)

Yes

SSL Certificate fingerprint

SSL Certificate fingerprint in SHA-1 format Alphanumeric No

Server Mail server Alphanumeric Yes

Port. Integerbetween 1 and 65535

Yes

Username Username for the e-mail account Alphanumeric Yes

Password E-mail account password Alphanumeric Yes

Options Ignore e-mails that are marked as read.Delete e-mails that are found from the server.

Yes/No No

Alert threshold Search terms in the sender address (FROM: field). Alphanumeric No


Search terms in the e-mail subject. Alphanumeric No



• Unable to connect to the e-mail account.


• The check processes e-mails that have arrived since the last check.



• When the check finds an e-mail that matches the search criteria, it is switched to "Read" status.

• The certificate fingerprint must be specified for self-signed or expired certificates.


238

Example:


238

Custom command (from monitoring server)

Objective:

To run a command or script on the monitoring engine and retrieve a return code.

Generic settings:



• Graphics: No



Specific settings:


Command line Command or script to run Alphanumeric Yes

Argument 1 to 12 Specify the arguments Alphanumeric No

Alert threshold Return codes to trigger an alert Numeric No


• The command or script does not exist.


• The "Command line" field must contain the complete path of the script to be run. Example: "c:\php\

php.exe" when the monitoring engine is running on a Windows system.

• When the monitoring engine is running on a Linux system, the system will execute the command

with the default shell. To choose a particular shell, fill the fields like this :

◦ “Command line”: Put the shell to use (ex: /bin/bash)

◦ “Argument 1” : Indicate the script (ex: /home/user/my_script.sh)

• The "Working directory" field refers to the "current" directory when the script runs: for more detail,

please see: https://en.wikipedia.org/wiki/Working_directory

• The "Alert threshold" should be completed as follows:

◦ The ".." characters allow for a range of codes. For example, "1..3" includes all codes between 1

and 3 inclusive. Note that "5..2" is invalid and logical sequences must be followed.

◦ The "," character indicates multiple codes. For example. "12,-5" will cover codes "12" and "-5".


238

https://en.wikipedia.org/wiki/Working_directory

Example:


238

Group check

Objective:

To select multiple checks within an organization and to send a specific alert if the number of check

simultaneously in error exceeds the threshold in an error state.

Generic settings:



• Graphics: No



Specific settings:


Target alerts Alert selectionThe order in which checks are run can be changed by moving the checks up or down using arrow keys.

Yes

Alert threshold Number of checks in an error state (minimum or maxi-mum values).


Yes


• “Meta check targets has not target, please make sure the check configuration is OK (NB: targets

must be executable on the engine with ID x): This alert appears when at least one selected check is

not running on same monitoring engine where the check is deployed. See the additional information

below.


• Only checks within a single organization and running on same monitoring engine can be selected to

create a multiple check.

• The multiple check follows its own run schedule and does not follow those of the selected checks.

• The multiple check does not run the selected checks, it collects the last status of each selected

checks and compare the number of checks in error with the threshold.

Example:


238


238

Annexes

I. Regular expressions

Regular expressions to use are those that apply to Java.

The site below allows you to test quickly whether the regular expression specified in the check is

appropriate:

http://www.regexplanet.com/advanced/java/index.html

Example:

• "Regular expression" field: specify the regular expression as it is entered in the check.

• In the "Entry"* field: enter multiple test cases, some (but not all) of which should be processed.

• Table: output of the regular expression on the "Entry*" field, indicating the entries where the regular

expression has found the search terms.

Some common regular expression symbols:


238

http://www.regexplanet.com/advanced/java/index.html

• "^ ": indicates the start of the string E.g.: "^error" will only process lines that start with "error."

• "$" indicates the end of the string. E.g.: "timeout$" will only process lines that end in "timeout."

• "." indicates any character.

• "*": indicates 0, 1, or multiple occurrences of the previous character. An example, when combined

with the previous character: "Success.*" will find "Success" and "Successful"

• "+" indicates one or more instances of the previous character. E.g.: "0+1" will find "01", "0001",

"000001", and so on.

• "Line (?!<value>)" Exclude all the line if the <value> is found in the line.

II. Date and time format

Dates and times used by the SimpleDateFormat Java class are described in the link below:

http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text

III. OID Examples

Please see below for some examples of generic OIDs:

• 1.3.6.1.4.1.2021.10.1.3.1 => system load over one minute

• 1.3.6.1.4.1.2021.10.1.3.2 => system load over five minutes

• 1.3.6.1.4.1.2021.10.1.3.3 => system load over 15 minutes

• 1.3.6.1.4.1.2021.11.51.0 => available CPU time

• 1.3.6.1.4.1.2021.4.4.0 => free swapfile space

• 1.3.6.1.4.1.2021.4.6.0 => RAM in use

• 1.3.6.1.4.1.2021.4.11.0 => free RAM

• 1.3.6.1.4.1.2021.4.15.0 => cache memory

• 1.3.6.1.4.1.2021.4.5.0 => total device memory

• 1.3.6.1.2.1.1.3.0 => system start date and time

• 1.3.6.1.4.1.2021.9.1.7.1 => free disk space

• 1.3.6.1.4.1.2021.9.1.8.1 => disk space in use

• 1.3.6.1.4.1.2021.9.1.9.1 => percentage disk space utilization

Note: for disk OIDs, the final digit corresponds to the disk number.

IV. Windows - WMI Performance Counters

It may happen that some Windows controls do not work (setting alert 110 - Internal Error) while others work.

See the next 2 parts.

A. Test the query

When the alert message indicates the WMI query used:


238

http://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html#text

<p:ParameterInfo>SELECT * FROM Win32_PerfFormattedData_PerfOS_Element WHERE…

Test the request via Wbemtest or PowerShell on the monitored equipment.

For simplicity, do not include the possible "WHERE" clause.

B. Rebuild Performance Counters

If the previous test is in error, perform the following actions on the monitored server.

Rebuild performance counters:

cd c:\windows\system32lodctr /Rcd c:\windows\sysWOW64lodctr /R

Then resynchronize the counters with WMI:

WINMGMT.EXE /RESYNCPERF

Stop / Restart the "Performance Logs and Alerts" service.

Stop / Restart the "Windows Management Instrumentation" service.

V. SAP - DB - Return codes

List of return codes for backups and archives:

SAP return codes Return code to enter into the alertthreshold

Meaning

0000 0 Success

0001 1 Warning

0003 3 Error

0005 5 Error

9999 9999 In progress

Note: do not include the zeroes in four-digit SAP return codes when noting the return

code in the alert threshold.

VI. SAP - Process chain - Return code

List of return codes for process chain :


G Successful

F Successful

A Running


238

R Arbored

X Arbored

VII. Running checks manually

In the Actions menu for the alert, the "Run" command runs a check. When a check is run manually, the

scheduled check is not affected. Data is retrieved based on the last time that the alert was run

automatically, and consequently, if certain checks have never run automatically, the "Run" command will not

appear in the action menu.

Document end


238

Monitoring - Check configuration - Cockpit ITSM · Network I. Network - Bandwidth Objective: To...

Documents

Transcript of Monitoring - Check configuration - Cockpit ITSM · Network I. Network - Bandwidth Objective: To...