Fast Monitoring

FAQ (short answers)

1. What is a CRI file?
2. Where do I put my CRI file for automated monitoring?
3. How do I test my CRI file using 2 HBOOK files?
4. How do I test my CRI file by itself?
5. How do I install XxxMonTools to the self-service area?
6. Where do I put reference histogram files for automated monitoring, and how should I merge them?
7. How do I view the live FastMonAuto CMLOG messages remotely?

Links

• Bin-bin comparison documentation (2/11/00)
• Tags for running DhpMonApp (2/11/00)
• Collected softlinks needed for installing new build of FastMon (2/11/00)
• Running CMLogger (2/12/00)
• Directories for Monitoring Data in OEP
• JAS Home Page

A CRI (Comparison Record Info) file is a text file that allows you to specify the comparisons you want to do. Look at DhpToken/ExampleTokenFile.cri for documentation on how to set up a CRI file.

Automated monitoring looks for the file main.cri located in the directory /nfs/bbr-srv02/bfdist/MonitoringData/XxxMonTools/FastMonAuto.

In order to install new CRI files, one should commit and tag their changes to the XxxMonTools package,install the package, and then ask the navigator shifter to restart automated monitoring.

testOprComparison test.hbook ref.hbook my.cri

testDhpTokenFile my.cri

1. Make sure you are on an IR2 machine. bbr-dev20 is a good choice.
2. cd /nfs/bbr-srv02/bfdist/MonitoringData
3. srtpath
   • <return> [accept base release associated with MonitoringData]
   • SunOS58
4. addpkg XxxMonTools VYY-ZZ-WW
5. LiveFastMon-html-install .
6. tcsh
7. chmod -R g+w .
8. exit

Your reference histogram HBOOK file should be located in the /nfs/bbr-srv02/u4/Monitoring/References/Xxx/LiveFastMon directory. The system will look for it under the name LiveFastMon.hbook, but we recommend that you create the actual file with a name incorporating a date or other unique identifier, and then create LiveFastMon.hbook as a symbolic link pointing to the appropriate file. E.g.:

   lrwxrwxrwx   1 walkowia bfactory      22 Feb 25  2002 LiveFastMon.hbook -> svt_refc_25feb02.hbook
   -rw-rw-r--   1 walkowia bfactory   57344 Feb 25  2002 svt_refc_25feb02.hbook
   -rw-r--r--   1 walkowia bfactory   57344 Oct  5  2001 svt_refc_05oct01.hbook
   -rw-r--r--   1 eisner   bfactory   57344 Apr  8  2001 svt_refc_08apr01.hbook

You may use a date, or the number of a run from which a file is derived, or small integer indices, as you please, but we do feel that you will benefit from a level of indirection through the link, which will let you insert and remove changes very easily, and we suggest that you not change the contents of a file under any given name once it has been used. There's plenty of disk space available to store quite a large number of archived references.

NOTE:Once you update your LiveFastMon.hbook link to point to a new file (or have changed the contents of the file, though we discourage this), you MUST run the merge script, which creates one big HBOOK file that DhpMonApp and the reference histogram server looks at. This is the procedure:

1. (For FM Operations Manager) Make sure there is a References symbolic link in /nfs/bbr-srv02/bfdist/MonitoringData
to /nfs/bbr-srv02/u4/Monitoring/References.
2. Make sure you are on an IR2 machine. bbr-dev20 is a good choice.
3. cd /nfs/bbr-srv02/bfdist/MonitoringData/
4. srtpath
   • <return> [accept base release associated with MonitoringData]
   • SunOS58
5. LiveFastMon-hbook-install . LiveFastMon
6. Notify the DQM shift taker in IR-2 that the "LiveFastMon" reference histogram server needs to be restarted to make the changes visible.

1. Check out OepTools V00-02-40 or later, as well as workdir.
2. gmake workdir.setup
3. gmake OepTools.bin
4. cd workdir
5. FastMonAutoCmlog

This will run the browser locally, and start it in update mode. You can change to query mode using the menus. Kill the browser by first disconnecting the server, and then exiting.

Last revised: December 4, 2003

Back to Top