The LDAD System Monitor and Control System is a Web-based system that allows the site to monitor LDAD connectivity and processes. The Monitor checks on all LDAD processes, systems, and data to provide a visual interface of current LDAD performance for the site LDAD Administrator. The primary interface is via a WWW browser to the LDAD Monitor Summary portion of the AWIPS System Monitor. This page summarizes all LDAD monitor pages. In addition to monitoring, the LDAD System Monitor allows the Administrator to administer the system. The LDAD Site Administrator can start/stop processes, edit the system configuration file, etc. Figure 8.1 shows the LDAD Summary Monitor. From this page, the LDAD Administrator can access all aspects of LDAD configuration using the hyperlinks.
The Summary Monitor application, MakeSUMMpage, runs on the as1 server and uses configuration file ~ldad/data/summary.conf for various parameters including the pages to monitor. The standard monitor includes external (ls1) and internal (ds/as) processes, and data acquisition (ingest on ls1) and dissemination (transfer to ls1 for BBS access). The Internal Process and System page comes from as1, while the other three are retrieved via HTTP protocol from ls1. By default, the monitor updates every 5 minutes. If any of the pages is out of date (i.e., older than the run_interval specified in summary.conf), MakeSUMMpage will not generate its line on the summary.
The overall/summary state of each sub-monitor is displayed on the left with the standard state icons. On the right are 4 columns, designated R, Y, B, G for Red, Yellow, Blue, and Green, respectively. The numbers below the column represent the number of items that are in each of the states for each sub-monitor. This gives the Site Administrator some indication of the relative problem and allows for prioritization for problem solving. (If any item is in ? state - e.g., a data file not found, it does not register in any column.)
There are two Process and System pages, Internal and External, each of which displays the state of all appropriate LDAD processes and hardware systems. These pages are intended to be used primarily by the LDAD Site Administrator. There are three tables on each page:
The Internal Process and System monitor is illustrated here.
Clicking any of the system hyperlinks creates a telnet session to that system. This allows the administrator to quickly get to the appropriate system.
The Process Monitor application, MakePROCpage, runs on as1, using /awips/fxa/htdocs/ldadMon/conf/proc_internal.conf as its configuration file for various parameters including the systems and processes to monitor. Since it is run by user fxa (an entry in fxa's crontab, startLdadMon.sh, checks every 10 minutes to make sure it's running), fxa user requires the appropriate rhosts entry for any system on which you need the LDAD Process Monitor to check.
MakePROCpage also runs on ls1, reading ~ldad/data/proc_external.conf. Section 9.8.2 lists these configuration files and their default settings. (For more information on the rhosts entries see the LDAD Installation Manual.)
The Internal page includes a link to the LDAD Administration functions shown below in Figure 8.4. This link requires authentication: the user must provide the LDAD Administrator username and password via the dialog shown in Figure 8.3. The Internal page also includes a Restart Processes link. Here again, a valid username and password is required.
Using the Administration interface, the LDAD site administrator can start/stop processes and edit configuration files. Clicking on a start or stop link will call the appropriate function on the respective system for that process to be started or stopped. LDAD uses many configuration files for the data decoding and storage processes. Even the monitor and administration applications use configuration files that sites can configure to fit their needs.
Follow these steps to retrieve and edit a configuration file.
The LDAD Restart Page shown in Figure 8.5 includes a more limited set of functions that can be accessed using the standard awipsusr account. This page allows users to restart LDAD processes.
The LDAD Administration and Restart Process pages are generated by CGI processes /awips/fxa/htdocs/ldadAdmin-cgi/ldadAdmin.pl and ldadRestart.pl, respectively. These processes use /awips/fxa/htdocs/ldadMon/conf/ldadAdmin.conf and ldadRestart.conf, respectively. These are fully described in Tables 9.5 and 9.6).
The Help function is not yet implemented.
The Data Acquisition Monitor, Figure 8.6, lists all the LDAD data that are being acquired and uses standard state icons to show data availability, i.e. current, late, none, etc. In addition, it shows a brief message and the last update time for each data set.
Note that this refers to arrival of data on ls1 and their transfer to ds1. It's possible, of course, for files to arrive but not get processed.
LDAD obtains data from many providers; the Site Administrator can click on any data link to display information regarding that data provider, including name of provider, address, point of contact, telephone number, etc. Of course, it's up to each site to set up this information in ldadProvider.txt (via the LDAD Provider List link on the Administration page).
The Data Acquisition Monitor application, MakeLDApage, runs on ls1 and uses ~ldad/data/lda.conf as its configuration file for various parameters including the datasets to monitor, their timeout values, and the messages to post when they are late. One edits lda.conf by selecting Data Acquisition from the LDAD Admin page.
The Data Dissemination Monitor is similar to the Data Acquisition Monitor in all respects except that it uses ldd.conf as the configuration file for the MakeLDApage application.
QCMS summary files are stored in the text database. Files are named <nnn>QC[HDWM]LLL, where nnn is a 3-digit number (leading zeros) corresponding to a dataset's ordinal position in as2:/awips/ldad/MSAS/fslparms/sfchqcin.dat (e.g., NPN is 003); H is for hourly QC summaries, D for daily, W for weekly, and M for monthly; and LLL is the WFO ID. A sample, part of a 005QCHBOU product, is shown in Figure 8.7. "ASOS" (the 5th entry in sfchqcin.dat) is the provider name for all stations in the message.
ASOS HOURLY QUALITY CONTROL MESSAGE (PAGE 1 OF 4)
**********************************************************************
* 19-MAY-1999 * SLP * POT TEMP * DEW PNT * DD * FF *
* 1900 UTC * (MB) * (DEG F) * (DEG F) * (DEG) * (KNTS) *
**********************************************************************
* TOTAL OBS * 463 * 665 * 665 * 597 * 597 *
* QST OBS * 7 * 10 * 5 * 10 * 10 *
* PERCENT QST * 1.51 * 1.50 * 0.75 * 1.68 * 1.68 *
**********************************************************************
************************** EASTERN * REGION ***********************
* KBHB * * -9( 7)* * * *
* KMTN * * * * -10 * 3 *
* KNEL * * -9( 6)* * * *
************************** CENTRAL * REGION ***********************
* KBJC * * * * -170 * -4 *
* KCEZ * * * -20( 9)* * *
* KCGX * * 8( 6)* * * *
* KEEO * * * 10( 8)* -100 * 4 *
**********************************************************************
ERROR = ANALYSIS - OBSERVATION OB ERROR ( ERROR THRESHOLD )
|
QCMS generates status messages for up to 20 providers, automatically updating sfchqcin.dat as providers are found in the netCDF files. If more than 20 are found, all additional providers' QC information will be lumped into products 000QC[HDWM]LLL.
The LDAD Scheduler is the user interface component of LDAD that provides access to maintain the LDAD database. Through this interface, you can incorporate new data sources into the system and set up operating environments for external users. Also here you can schedule dial-out and ftp sessions to collect data from remote systems.
To start the Scheduler, select Collection/Dissemination... from the D2D Surface menu.
See the AWIPS D2D User's Manual for instructions for using the Scheduler.
An e-mail address for the LDAD Site Administrator is provided as an input field for most configuration files. This is also true for the LDAD start and stop scripts. If these scripts or monitoring systems detect an error in performing their function, an e-mail is sent to the LDAD Site Administrator (username ldad). LDAD Site Administrators are advised to check their e-mail regularly for LDAD problem reports.
 |
 |
 |
