Process Monitoring - Heartbeat for HP NonStop process monitoring
The three proactive modules: process monitor, file metrics monitor and the file existence monitor are known collectively as the Reflex 80:20 Heartbeat.
The Process Monitoring facility will track a list of nominated processes and raise an EMS event if the process does not exist. The module will then create a separate event once the process reappears. If a process terminates before it has issued a diagnostic message then this occurrence will be trapped by the Process Monitor software.
This pair of “up” and “down” events can be used to animate an OverDrive Status Monitor icon representing the process and force the icon to turn red (down) and grey (up). If the icon is positioned in a Service class then the impact on the application of losing this process can be assessed at a glance.
A range of process characteristics are also monitored and if any of them are exceeded a further event can be created. The process is still running but is classed as under threat so this is a “vulnerable” condition and consequently we can use this event to create a blue (vulnerable) OverDrive icon in the Status Monitor.
The attributes reviewed for a process are ;
- Busy
- Looping or Suspect (e.g. gone into INSPECT)
- Memory pages
- Global Data Size
- Native Heap Size
- Process running time
- Process execution time
To restrict the number of messages created by this function you can monitor processes within a specified time period. This time period can be altered to suit the varying availability of your application and this is achieved by running a Reflex 80:20 batch utility to switch monitoring on and off for a group of processes. Some installations have automated the execution of this utility via the Taskmaster which is driven by an event created when the application closes down.
OSS (Open System Services) processes can also be monitored by Reflex. The process status agent will show information relating to the actual OSS process.
Reflex Dashboard has additional information to obtain the underlying object name which is useful for OSS programs where the a object will be the Java virtual machine and the actual program is an argument sent to the java virtual machine object.
Reflex does not use the HP NonStop Tandem MEASURE subsystem as part of day-to-day, core monitoring of the NonStop platform(s). However, Measure can be run up on an authorised user's request from the Reflex Dashboard display, or via a monitored Process Object component in the Status Monitor view.
Measure requests can be issued for a selected process and / or the files and processes opened by that selected process. Each request can be run for a user defined period, e.g. 30 seconds (this value can be amended via the Admin Parameter: MEASUREMENT-DURATION) and will provide a measurement counters snapshot, where if required, the counter results can be saved as a CSV file for later analysis.
The Measure counter / attributes returned for each type of request are as follows:
'OPEN' Measure Counter list:
1. Date
2. Time
3. Duration
4. System
5. OSVersion
6. FormatVersion
7. DataVersion
8. CPU
9. PIN
10. Fnum
11. Filename
12. FileSysName
13. FileType
14. DeviceType
15. FileBusyTime
16. Reads
17. Writes
18. UpdatesOrReplies
19. DeletesOrWriteReads
20. InfoCalls
21. RecordsUsed
22. RecordsAccessed
23. DiscReads
24. Messages
25. LockWaits
26. TimeoutsOrCancels
27. Escalations
28. OpenerProcessname
29. OpenerProgramname
30. DeviceName
31. OpenerDevicename
32. BytesF
33. DBIOReads
34. DBIOWrites
35. DBIORecordBytes
36. DBIOWriteBytes
37. FileCRVSN
38. OpenerOSSPID
39. OpenerCRVSN
40. FileOpenType
41. IPAddress
42. ReadBytes
43. WriteBytes
44. OSSCacheReads
45. OSSCacheWrites
46. OSSCacheReadBytes
47. OSSCacheWriteBytes
48. OSSBlockReads
49. OSSBlockReadBytes
50. OSSFlowControls
51. MiscCalls
'PROCESS' Measure Counter list:
1. Date
2. Time
3. Duration
4. SystemName
5. OSVersion
6. FormatVersion
7. DataVersion
8. CPU
9. PIN
10. ProcessName
11. ProgramFileName
12. Priority
13. UserID
14. CreatorID
15. AncestorCPU
16. AncestorPIN
17. AncestorSystemName
18. AncestorProcessName
19. DeviceName
20. HometermSystemName
21. Hometerm
22. CPUBusyTime
23. ReadyTime
24. MemQTime
25. Dispatches
26. PageFaults
27. USEMS
28. PagesQTime
29. PagesStart
30. PagesEnd
31. ExtSegsQTime
32. AbsSegsQTime
33. AbsSegsStart
34. AbsSegsEnd
35. RecvQTime
36. MessagesSent
37. MessagesRecvd
38. MsgsSentQTime
39. SentBytesF
40. RecvdBytesF
41. ReturnedBytesF
42. ReplyBytesF
43. SentCBytes
44. ReceivedCBytes
45. ReturnedCBytes
46. ReplyCBytes
47. MQCAllocations
48. MQCAllocFailures
49. MQInuseQTime
50. Checkpoints
51. AllocSegCalls
52. FileOpenCalls
53. InfoCalls
54. ProgramAccelerated
55. NativeProcess
56. SystemProcess
57. AccelBusyTime
58. TNSBusyTime
59. NativeBusyTime
60. CompTraps
61. BeginTrans
62. AbortTrans
63. OSSPid
64. CRVSN
65. OSSTTYReads
66. OSSTTYWrites
67. OSSTTYReadBytes
68. OSSTTYWritesBytes
69. OSSTTYWaitTime
70. OSSDevNullOps
71. OSSNSDDCalls
72. OSSNSRequests
73. OSSNSMessagesBytes
74. OSSNSWaitTime
75. OSSNSRedirects
76. Launches
77. LaunchWaitTime
78. OpenCloseWaitTime
79. IPUSwitches
80. GMOMNode
81. GMOMCPU
82. GMOMPin
83. GMOMJobId
84. GMOMSysName
85. GMOMProcessName
86. IPUs
To gain full access to the Reflex process module example screenshots, please register with this website (click the 'Register' link - at top right of page).
NOTE: Please provide a company / organisation email address during the registration process.
Once your website registration is approved (usually within 24 hours), then 'Login' to the website and navigate to this Reflex for NonStop process monitoring web page and the example screenshots will be available for viewing at the bottom of the page.
If you are already a member of this website, 'Login' as normal.
To gain full access to the Reflex process module demonstration files, please register with this website (click the 'Register' link - at top right of page).
NOTE: Please provide a company / organisation email address during the registration process.
Once your website registration is approved (usually within 24 hours), then 'Login' to the website and navigate to this Reflex process monitoring web page and the demonstration files will be available for download at the bottom of the page.
If you are already a member of this website, 'Login' as normal.
Hardware and software pre-requisites for the Reflex product are detailed below:
• HP NonStop (ServerNet or Integrity platforms)
• Guardian D38 Operating System (or above)
• TMF
• SQL runtime system (SQL/MP runtime), or alternatively, NonStop SQL product
• Pathway (TS/MP)
• TCP/IP
• Non-RDF/DRNET Audited Volume *
* It is recommended that Reflex is installed on a Non-RDF/DRNET Audited Volume. If this is a cause for concern, please contact Insider Technologies Ltd to discuss further.
Reflex is installed using a menu driven TACL macro for easy deployment. The macro will perform checks and output the results of each stage of the Reflex product install so that if problems are encountered they can be resolved easily.
Windows Platform for GUI Install:
• Modern Pentium PC Specification
• 32Mb on-board RAM
• 20Mb free hard disk space
• Minimum 17” monitor recommended
• Graphics Resolution: 1027 x 768 x 16 minimum
• Windows XP, Vista, 7
* For escalation of HP NonStop issues to enterprise management solutions, email or mobile SMS, a dedicated Windows box is required.