Caché Monitoring Guide - InterSystems Documentation

More documents

Recommendations

Info

Monitoring Caché Using SNMP Trap Name (Number) cacheLoggedError (15) cacheLicenseExceed (16) cacheAppAlert (100) Description A “severe ” error has been logged in the cconsole.log file. This trap includes the error message defined in cacheSysErrorMsg. A request for a license has exceeded the number of licenses currently available or allowed. This is a generic trap that can be used by Caché applications to generate alerts via SNMP. For detailed information about how this trap can be used, see the %Monitor.Alert.External class method. The following table describes the Caché-specific auxiliary objects that can be sent in the traps described in the preceding table. Table II–2: Caché-specific Auxiliary Objects Sent in Traps Auxiliary Object Name (Number) cacheDBWriteError (1) cacheApp (2) cacheAppSeverity (3) cacheApptext (4) Description The Caché-specific error code for a failed database write. Possible values are: , , , or . A short text string (maximum of 20 characters) that identifies the application that generated (or was the source of) a cacheAppAlert trap. A code that indicates the severity of the problem for a cacheAppAlert trap. The code can be 0 (info), 1 (warning), 2 (severe), or 3 (fatal) A text string description (maximum of 1024 characters) of the problem, error, or event that caused the cacheAppAlert trap. The following table describes the Ensemble-specific SNMP traps. Table II–3: Ensemble SNMP Notification Objects (Traps) Trap Name (Number) ensEvent (1) Description The Caché implementation of SNMP signals an Ensemble_LogEvent each time an Ensemble business host posts an alert to the Ensemble Event Log. B.5 Sample User-defined SNMP Monitor Class This section describes an example of how to define a user Monitor class that you can query via SNMP. The Application Monitor only includes properties with %Monitor data types in the SNMP data. Example Class Following is the sample class for this example: Class SNMP.Example Extends %Monitor.Adaptor { /// Give the application a name. This allows you to group different /// classes together under the same application level in the SNMP MIB. /// The default is the same as the Package name. Parameter APPLICATION = "MyApp"; /// This groups a set of properties together at the "table" level of the /// SNMP MIB hierarchy. The default is the Class name. 114 Caché Monitoring Guide
Sample User-defined SNMP Monitor Class Parameter GROUPNAME = "MyTable"; /// An integer metric counter Property Counter1 As %Monitor.Integer; /// Another integer metric counter Property Counter2 As %Monitor.Integer; /// A status indicator as a string data type Property Status As %Monitor.String; /// The method is REQUIRED. It is where the Application Monitor /// calls to collect data samples, which then get picked up by the /// ^SNMP server process when requested. Method GetSample() As %Status { set ..Counter1=$r(200) set ..Counter2=200+$r(100) set n=$r(4) set ..Status=$s(n=1:"Crashed",n=2:"Warning",n=3:"Error",1:"Normal") Quit $$$OK } } Before compiling this class in a user namespace, Caché must load supporting classes into the user namespace; these classes are required to store the data samples for SNMP. To load the classes, run ^%MONAPPMGR and do the following: • Select option 2, Manage Monitor Classes • Select option 3, Register Monitor System Classes. When you compile the sample class, it creates the SNMP.Sample.Example class to store the sample data. Important: Do not delete generated sample classes explicitly; if you select both the monitor and generated sample classes for deletion, the sample class routines remain although the monitor class routines are deleted, which causes an error. To ensure that all sample class routines are properly removed, delete only the application monitor class that generated it; when you delete the monitor class both the monitor class and generated sample class, as well as related routines for both classes, are deleted. For example, to deleted a sample class (for example, SNMP.Sample.Example), use the Management Portal or Studio to delete the monitor class from which it is generated (that is, SNMP.Example). Run ^%MONAPPMGR to activate the sample class and start the Application Monitor to collect samples: 1. Select option 2, Manage Monitor Classes. 2. Select option 1, Activate/Deactivate a Monitor Class. 3. To see an numbered list of registered Monitor Classes, enter . 4. Enter the number of Monitor Class you want to activate; for example, to activate a user-defined class named SNMP.Example, enter the number next to the class name. 5. Select option 6, Exit (to return to the Application Monitor main menu). 6. Select option 1, Manage Application Monitor. 7. Select option 1, Start Application Monitor. 8. Select option 5, Exit (to return to the Application Monitor main menu). 9. Select option 6, Exit (to exit from Application Monitor main menu). Note: For information about configuring and using the Application Monitor, see Caché Application Monitor in the “Using the Caché Monitor” chapter. Caché Monitoring Guide 115
Page 1 and 2:
Caché Monitoring Guide Version 201
Page 3 and 4:
Table of Contents About This Book .
Page 5 and 6:
B.4 Caché MIB Structure ..........
Page 7:
About This Book This book describes
Page 10 and 11:
Monitoring Caché Using the Managem
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Using the Caché Diagnostic Report
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Using the Caché Monitor The option
Page 26 and 27:
Using the Caché Monitor Option 4)
Page 28 and 29:
Using the Caché Monitor 3.2 Caché
Page 30 and 31:
Using the Caché Monitor Option 3)
Page 32 and 33:
Using the Caché Monitor Option 4 1
Page 34 and 35:
Using the Caché Monitor Input Fiel
Page 36 and 37:
Using the Caché Monitor 3.2.2.1 Ge
Page 38 and 39:
Using the Caché Monitor { // Get f
Page 41 and 42:
4 Gathering Global Activity Statist
Page 43 and 44:
Examples of ^GLOSTAT Output Statist
Page 45 and 46:
Examples of ^GLOSTAT Output Map: 22
Page 47 and 48:
Examples of ^GLOSTAT Output 4.3.6 E
Page 49 and 50:
5 Monitoring System Performance Usi
Page 51 and 52:
Using ^PERFMON If you are running ^
Page 53 and 54:
Using ^PERFMON Format: status = $$R
Page 55 and 56:
Report Examples Metric Number 45 46
Page 57 and 58:
6 Monitoring Routine Performance Us
Page 59 and 60:
Using ^PROFILE Option R X Descripti
Page 61:
^PROFILE Example There are 5 routin
Page 64 and 65:
Examining Routine Performance Using
Page 66 and 67:
Page 68 and 69:
Page 70 and 71: Examining Routine Performance Using
Page 73 and 74: 8 Monitoring Performance Using ^pBu
Page 75 and 76: Scheduling the ^pButtons Utility wi
Page 77 and 78: Customizing the ^pButtons Utility I
Page 79 and 80: Customizing the ^pButtons Utility s
Page 81 and 82: Performance Reports Created by ^pBu
Page 93 and 94: 9 Monitoring Performance Using ^mgs
Page 95 and 96: Column RemRrefs * RouLaS RemRLaS *
Page 97: Considering Seizes, ASeizes, and NS
Page 100 and 101: Monitoring Caché Mirroring Perform
Page 102 and 103: Monitoring Caché Mirroring Perform
Page 104 and 105: Caché History Monitor • SYS.Hist
Page 107 and 108: A Monitoring Caché Using BMC PATRO
Page 109 and 110: Caché PATROL Knowledge Modules Arg
Page 111 and 112: Caché Metrics Used with BMC PATROL
Page 113 and 114: Caché Metrics Used with BMC PATROL
Page 115 and 116: B Monitoring Caché Using SNMP This
Page 117 and 118: Caché MIB Structure 3. When you ed
Page 119: Caché MIB Structure The Caché sub
Page 123: Sample User-defined SNMP Monitor Cl
Page 126 and 127: Monitoring Caché Using WMI 3. Sele
Page 128 and 129: Monitoring Caché Using WMI %SYS>Do
Page 130 and 131: Monitoring Caché Using Web Service
show all

Caché Monitoring Guide - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?