Caché Monitoring Guide - InterSystems Documentation

More documents

Recommendations

Info

Monitoring Caché Using the Management Portal Note: If you have trouble starting Caché, use any text editor or text viewer to view the cconsole.log file, which is located in the install-dir\mgr directory. The cconsole.log file grows until it reaches a maximum size, when it is renamed cconsole.old at next startup. The value is configurable (default is 5 MB) from the [System] > [Configuration] > [Startup Settings] page of the Management Portal; update the number of MBs for the MaxConsoleLogSize setting. You may also view log information about application errors and ODBC errors from the [System] > [System Logs] > [View Application Error Log] and the [System] > [System Logs] > [View xDBC Error Log] pages of the Management Portal. 10 Caché Monitoring Guide
2 Using the Caché Diagnostic Report InterSystems provides a mechanism to run a diagnostic report on your Caché instance and send the results to the InterSystems Worldwide Response Center (WRC) to help diagnose system problems. You configure and run the Diagnostic Report as a task from the Management Portal. The following sections describe the tasks, settings, and contents of the Diagnostic Report option: • Running the Diagnostic Report Task • Configuring Diagnostic Report Settings • Diagnostic Report Contents • Additional Diagnostic Scripts and Utilities For more information on this task see the %SYS.Task.DiagnosticReport entry in the Caché Class Reference. 2.1 Running the Diagnostic Report Task The most direct way to generate the report is by choosing Diagnostic Report on the Operations menu of the Management Portal [Home] page. On the [System] > [Diagnostic Report] page, enter the appropriate information for the Diagnostic Report task. You can edit this information at any time by returning to this page. If you do not wish to edit any of the fields, click Run to generate the report using the current settings. If you do not enter any information and click Run, the task generates an detailed report and places it in the manager’s directory of the Caché instance (install-dir\mgr) as an HTML file. The file name is in CustomerNameYYYYMMDDHHMM.html format. For example, on September 24, 2007 at 8:46 p.m., running the Diagnostic Report task with a license key issued to MyCompany on an instance installed in C:\MyCache generates a report file named: C:\MyCache\mgr\MyCompany200709242046.html There are several fields on the page you can set that affect when the task runs, where the file is saved, and whether or not to send the file to the WRC. The Configuring Diagnostic Report Settings section describes these settings. If you click Close, your changes are discarded and the report task does not run. Viewing the Diagnostic Report Task History If you click Task History at the top of the [System] > [Diagnostic Report] page you can view previous runs of the Diagnostic Report. This page is part of the Task Manager portion on the Operations side of the Management Portal. See Using the Task Manager in the “Managing Caché” chapter of the Caché System Administration Guide for details. Caché Monitoring Guide 11
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 18 and 19: Using the Caché Diagnostic Report
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:
Page 70 and 71:
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 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
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 and 120:
Caché MIB Structure The Caché sub
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
Page 132 and 133:
Page 134 and 135:
show all

Caché Monitoring Guide - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?