Caché Monitoring Guide - InterSystems Documentation

More documents

Recommendations

Info

Monitoring Caché Using SNMP • Finally, the individual data objects contained in that table, including any that are designated as indices. • The notifications (traps) are defined as individual entries at the same hierarchical level as the “table”. For more information, see Caché SNMP Traps in this appendix. • Caché-specific auxiliary objects sent via notifications (traps) are defined as individual entries at the same hierarchical level as the “table”. For more information, see Caché SNMP Traps in this appendix. For example, encode the size of a database as: 1.3.6.1.4.1.16563.1.1.3.1.6.4.84.69.83.84.1 This translates to: iso.org.dod.internet.private.enterprises.intersystems.iscCache.cacheObjects .cacheDBTab.cacheDBRow.cacheDBSize.TEST(instname).1(DBindex) B.4.1 Ensemble MIB Structure In addition to the Caché managed object data defined in ISC-CACHE.mib, Ensemble also has the information defined in ISC-ENSEMBLE.mib available. Ensemble uses the same IANA private enterprise number as Caché, 16563 which represents intersystems. Below this, Ensemble implements its enterprise private subtree as follows: • The level below intersystems is the “product” or application ID level. For Ensemble this is .2 (iscEnsemble). This serves as the MIB module identity. • The next level is the “object” level, which separates data objects from notifications. For Ensemble, these are: .1 (ensObjects) and .2 (ensTraps). By convention, the intersystems tree uses a brief lowercase prefix added to all data objects and notification names. For Ensemble this is ens. • Subsequent levels follow the same implementation as Caché described in the Caché MIB Structure section. B.4.2 Extending the Caché MIB Application programmers can add managed object definitions and extend the MIB for which the Caché subagent provides data. This is not intended to be a complete MIB editor or SNMP toolkit; rather, it is a way to add simple application metrics that you can browse or query through SNMP. Note: The objects must follow the basic Caché SNMP structure, there is limited support for SNMP table structures (only integer-valued indexes are supported), and SNMP traps are not created (see the %Monitor.Alert class). A basic understanding of SNMP structure of management information is helpful. To create these objects do the following: 1. Create Caché object definitions in classes that inherit from the %Monitor.Adaptor class. See the Caché Class Reference for details about adding managed objects to the %Monitor package. 2. Execute an SNMP class method to enable these managed objects in SNMP and create a MIB definition file for management applications to use. The method to accomplish this is MonitorTools.SNMP.CreateMIB(). See the MonitorTools.SNMP class documentation in the Caché Class Reference for details of the CreateMIB() method parameters. The method creates a branch of the private enterprise MIB tree for a specific application defined in the %Monitor database. In addition to creating the actual MIB file for the application, the method also creates an internal outline of the MIB tree. 112 Caché Monitoring Guide
Caché MIB Structure The Caché subagent uses this to register the MIB subtree, walk the tree for GETNEXT requests, and reference specific objects methods for gathering the instance data in GET requests. All the managed object definitions use the same general organization as the Caché enterprise MIB tree, that is: application.objects.table.row.item.indices. The first index for all tables is the Caché application ID. All applications must register with the IANA to obtain their own private enterprise number, which is one of the parameters in the CreateMIB() method. To disable the application in SNMP, use the MonitorTools.SNMP.DeleteMIB() method. This deletes the internal outline of the application MIB, so the Caché subagent no longer registers or answers requests for that private enterprise MIB subtree. For an example of defining a user Monitor class, see Sample User-defined SNMP Monitor Class in this chapter. B.4.3 Caché SNMP Traps In addition to the object data and metrics available through SNMP queries, Caché can send asynchronous alerts or SNMP traps. The following table describes the Caché-specific SNMP traps. Table II–1: Caché SNMP Notification Objects (Traps) Trap Name (Number) cacheStart (1) cacheStop (2) cacheDBExpand (3) cacheDBOutOfSpace (4) cacheDBStatusChange (5) cacheDBWriteFail (6) cacheWDStop (7) cacheWDPanic (8) cacheLockTableFull (9) cacheProcessFail (10) cacheECPTroubleDSrv (11) cacheECPTroubleASrv (12) cacheAuditLost (13) cacheDaemonFail (14) Description The Caché instance has been started. The Caché instance is in the process of shutting down. A Caché database has expanded successfully. There is a potential problem in the future expansion of a Caché database; the database is approaching its maximum size or the disk is nearly full. The read/write status of a Caché database has been changed. A write to a Caché database has failed. It includes the Caché error code for the failed write. The Write Daemon for a Caché instance has stalled. The Write Daemon for a Caché instance has entered “panic” mode; that is, the Write Daemon is out of buffers and must write database blocks directly to disk without first committing them to the Write Image Journal (WIJ) file. The lock table for a Caché instance is full, which causes subsequent Locks to fail. A process has exited Caché abnormally (due to an access violation). For detailed information, see the cconsole.log file. A connection to this ECP Data Server for a Caché database has encountered a serious communication problem. For detailed information, see the cconsole.log file. A connection from this ECP Application Server to a remote Caché database has encountered a serious communication problem. For detailed information, see the cconsole.log file. Caché has failed to record an Audit event. The most likely cause is a problem with space for the Audit database, which requires operator assistance. A major Caché system process (daemon) has died because it encountered an unhandled error. Caché Monitoring Guide 113
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:
Examining Routine Performance Using
Page 68 and 69: Examining Routine Performance Using
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: Caché MIB Structure 3. When you ed
Page 121 and 122: Sample User-defined SNMP Monitor Cl
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?