BMC Patrol monitoring for NSO

[ron.whitt]

We're having BMC Patrol setup on an NSO server to monitor the application performance.  We're being asked for certain application parameters, which are of interest to Patrol.  I have the ask listed below.  Has anyone set up BMC Patrol, if so, what were the parms you used to feed Patrol?

• Web / Application Service (mandory non-system level filesystem mount points):

         Typical Filesystem Mount Points for each instance are

• WebSphere Filesystem mount point
• Application Filesystem mount point
• Log Filesystem mount point
• Example: /appvol, /appvol/GWS/HQS

• Process (application processes for each instance can be monitored)
  
  • Example
  • Process String: /opt/IBMIHS70/bin/httpd.*LWSGWSABM1HK
  • Process String: /opt/WebSphere70/AppServer/java/bin/java.*LASGWSABM1HK

• Database Service:
  • Database filesystem mount points for each instance can be monitored.
  • Example:
  • ora_pmon_abc
• File System
• Database processes of each DB instance can be monitored.

• Log (application log messages):

[Jan Lindblad · Accepted solution]

I am not aware of any BMC Patrol usage with NSO, but then again, I would not be the person to know about any such cases.

---

• Web / Application Service (mandory non-system level filesystem mount points):

         Typical Filesystem Mount Points for each instance are

• WebSphere Filesystem mount point
• Application Filesystem mount point
• Log Filesystem mount point
• Example: /appvol, /appvol/GWS/HQS 

---

There is no websphere in NSO. The directories are specified at installation time, but an NSO System Installation has these default directories:

InstallDir - /opt/ncs

ConfigDir  - /etc/ncs

RunDir     - /var/opt/ncs

LogDir     - /var/log/ncs

• Process (application processes for each instance can be monitored)
  
  • Example
  • Process String: /opt/IBMIHS70/bin/httpd.*LWSGWSABM1HK
  • Process String: /opt/WebSphere70/AppServer/java/bin/java.*LASGWSABM1HK 

---

The NSO processes have the following strings as part of their command line:

- "lib/ncs/erts/bin/ncs.smp" (unless running the single core version, which doesn't have .smp at the end)

- "inet_gethost"

- "lib/ncs/lib/core/ncs/priv/snmp-config-transform"

- "com.tailf.ncs.NcsJVMLauncher"

- "lib/ncs/lib/core/sls/priv/webapp-runner.jar"

There may be additional transient processes depending on the setup, e.g. ncs_cli processes as operators log onto the shell.

Database Service:

• Database filesystem mount points for each instance can be monitored.

• Example:
• ora_pmon_abc

• File System
• Database processes of each DB instance can be monitored.

• Log (application log messages): 

---

The CDB database is built-in to NSO (for performance), so there is no separate process. There is a database directory is inside the NSO RunDir, often called ncs-cdb. Database related log messages are in the same log files as the rest of NSO.

Hope this helps.

[ron.whitt]

Thanks Jan! the number of beers I owe you keeps growing

For others viewing this post.  This was a request on a commercial deployment.  The deployment team said the info Jan gave was exactly what they needed.