|
|
|
||||||||
|
|
|
|
|
|
|
|
|
||
|
|
|
|
|
||||||
|
|
|
||||||||
|
|
|
|
|
||||||
Use the 1.0 Vista Installation And Configuration Guide to install and configure Vista. Use the 2.0 Vista User's Guide to learn more about using the product. Although broken down into two major pieces, this help file is one html file, allowing for easier searches with the browser's Find command. Here is a complete outline of this docomument.
The Vista - Performance Analysis Portal is an easy to use interface for creating and viewing plots using data gathered by the Capacity Data Collector. Since the Web Cruncher is web based, performance data can be shared or viewed anywhere. Read this guide to install and configure Vista. Although this document tries to be complete, the user will be much more prepared if familiar with Wham's Distributed Resource Monitor (DRM) and Capacity Data Collector (CDC) products.
1.2 InstallationThe Capacity Data Collector (CDC) gathers data for and must be installed before installing Vista. For CDC installation instructions, please see the documentation for that product (CDC-guide.pdf).
1.2.2 Solaris
On Solaris, the Vista setup file is a package called WHdrmweb.
After the CDC is installed, cd to the directory containing the WHdrmweb
file. As root, use the pkgadd command:
pkgadd -d WHdrmweb allVista will be installed to /opt/whamtools/webcruncher. Vista is not actually run from this location. To uninstall the package, use the command:
pkgrm WHdrmwebAfter the package is installed, Vista must be configured. This process is described in detail in the 1.3. Configuration section. 1.2.3 AIX
On AIX, the Vista setup file is an install image called whamtools.drm.webcruncher. After the CDC is installed, cd to the directory containing the whamtools.drm.webcruncher file. As root, use the installp command:
installp -a -d whamtools.drm.webcruncher allVista will be installed to /usr/lpp/whamtools/webcruncher. Vista is not actually run from this location. To remove the install image, use the installp command with the -u option:
installp -u whamtools.drm.webcruncherAfter the package is installed, Vista must be configured. This process is described in detail in the 1.3. Configuration section. 1.3 Configuration
Vista does not run from the install procedure's target directory. Instead, a configured version is created from the installed files and copied to a new location. To create this configured version, cd to the install target directory (either
/opt/whamtools/webcruncher for Solaris or /usr/lpp/whamtools/webcruncher for AIX). read the following information, then run the configWC script and answer the questions. Use full paths for all path related questions.These questions include:
Data collection, batch plot creation and data maintenance are all performed out of cron.
Here are the items that should be placed in the crontab:
1.3.2.1 Crontab Entry For Data Collection
If Vista is configured at
/usr/local/webcruncher, then use:0 * * * * /usr/local/webcruncher/bin/rundrmhist.shThis line uses the CDC to store collected data in your arch directory. The above line executes rundrmhist.sh once at the beginning of each hour to collect data for that hour. For this example, the arch directory is /usr/local/webcruncher/arch. Perhaps you want 2 hours worth of data once a day or 8 hours of data gathered in two runs of drm_hist. This line of the crontab in conjunction with hist.conf's
RunTime
variable determine when and how much data is collected.
Remember to replace /usr/local/webcruncher with your actual path!
1.3.2.2 Crontab Entry For Data Maintenance
If Vista is configured at
20 * * * * (cd /usr/local/webcruncher/bin;./comparch.sh;./cachedisknet)
Remember to replace
/usr/local/webcruncher with your actual path! At twenty minutes past each hour, any newly collected data will be compressed. Also, the list of network and disk devices are saved.
1.3.2.3 Crontab Entry For Batch Plots
The Static Data Viewer depends on the batchplot program to create the batch plots defined in the
Static Data Configurator. If Vista is configured at
59 23 * * * (cd /usr/local/webcruncher/bin;./batchplot)causes the plot files to be created starting at one minute till midnight every evening. Remember to replace /usr/local/webcruncher with your actual path! 1.3.3 Vista End User Editable conf Files
For most configurations, running configWC should be sufficient. Perhaps you might want to collect data in 8 hour blocks or use already existing data with Vista. There are a few important conf files that allow for customization.
1.3.3.2 global.sh
Both configurable options and path information for Vista are stored here. In global.sh, the ROOT_DIR marks the root
of the install. Usually all other directories are based on this root. An example of this
structure as defined by global.sh might be:
ROOT_DIR="/usr/local/webcruncher"
RAW_DIR="${ROOT_DIR}/arch"
RPT_DIR="${ROOT_DIR}/rpt"
BIN_DIR="${ROOT_DIR}/bin"
HELP_DIR="${ROOT_DIR}/help"
CONF_DIR="${ROOT_DIR}/conf"
TMP_DIR="${ROOT_DIR}/tmp"
LOG_DIR="${ROOT_DIR}/logs"
DEMO_DATA="${CONF_DIR}/demo.dat"
PLOTCACHE_DIR="${ROOT_DIR}/htdocs/plotcache"
SP_DIR="${ROOT_DIR}/htdocs/staticplots"
PLOTICUS_DIR="${ROOT_DIR}/ploticus"
HIST_CFG="${CONF_DIR}/hist.conf"
GLOBAL_SH="${CONF_DIR}/global.sh"
You may wish to customize your installation by changing the RAW_DIR
or RPT_DIR paths
in global.sh. For example, if a Data Set Directory already exists,
you can set RAW_DIR equal
to the path to this directory instead of using the default arch directory.
Note that the configWC script
does this for you in the case that you are already collecting data with
drm_hist. Paths that might be changed include:| RAW_DIR | place where Vista looks for raw data from drm_hist (the CDC). The RAW_DIR is a Data Set Directory. This concept is discussed further in the CDC documentation and also in the Vista product help. |
| RPT_DIR | place for Vista intermediate data. Also used by drm_hist to store reports. |
| TMP_DIR | location for temporary files. |
| LOG_DIR | log files for the web server as well as webcruncher.log (WC's log file) are here |
| PLOTCACE_DIR |
Finished plots are saved here so that if a plot is requested
again, the graphics file is still available.
This directory must be visible on the web! If your webroot is /bdrake/webroot, then PLOTCACHE_DIR must begin with /bdrake/webroot. |
| SP_DIR |
This directory holds the graphics files generated by the Static Data Viewer's
batchplot program. The Static Data Viewer looks here for plots. This directory must be visible on the web! If your webroot is /bdrake/webroot, then SP_DIR must begin with /bdrake/webroot. |
This file contains all settings used when executing drm_hist via
the rundrmhist.sh script--another
way to say when gathering data. Although the drm_hist GUI may be used to
create this config file, a default is provided that is easily edited by
hand. Hosts from which to collect data are listed here as well as the length
of the sample to collect. The variables are:
| BothHosts | Hosts collecting both system and process data |
| SysHosts | Hosts collecting only system data |
| DataSize | Maximum data size in bytes of raw data stored under the DataDir |
| DataRmSz | Data size to be removed to maintain the maximum data size |
| DataDir | Data directory, should be the same as the RAW_DIR in global.sh. |
| RunTime | Sample run time. The default is an hour. If wanting data for 2 Hour chunks or 8 hour chunks, this is the value to change. |
| Interval | Data sampling interval |
| SampPerInt | The Number of samples per interval time |
| ReportType | Data Report type |
| TopNumber | Top processes number--this many processes will be displayed in the drm_hist reports listing top CPU consumers, etc... |
| DestDir |
Data Report Directory for daily spread sheet, can be the same as the
RPT_DIR in global.sh. |
httpd.conf is an Apache config file but is important to Vista since Vista is an Apache module built into the web server. Among other things, the web server's Port is specified in this file. Note that only root may start Apache for ports less than 1024. If installing WC to an NFS mounted drive, the LockFile directive should be uncommneted in this file to place the lock file on a local drive. If you do not do this, the parent httpd will exit with undefined results. see the comments in conf/httpd.conf.
1.4 Getting Started
After you have installed the package, run configWC, modified your crontab, and performed any
customization of paths, Vista is ready to run. Assume that global.sh
sets BIN_DIR to
/usr/local/webcruncher/bin.
Then Vista is started via:
/usr/local/webcruncher/bin/apachectl startand stopped with:
/usr/local/webcruncher/bin/apachectl stop1.4.2 Making Changes
After making any configuration changes, apache should be stopped and then started again. Use
apachectl stop and then apachectl start for this purpose. 1.4.3 Using VistaFor this example, pretend the domain name of the machine running Vista is fries.wham.com. Also assume that the web server has been started and is running on port 8001. Then from any browser, go to http://fries.wham.com:8001/. From there you may select the Interactive Data Viewer, Static Data Configurator, Static Data Viewer, or this Help page. Remember to replace fries.wham.com:8001 with the domain name or IP address (and port if not 80) of your newly installed Vista server.
IMPORTANT NOTES--THINGS THAT COULD DERAIL YOUR FIRST PLOT:If any of the above are FALSE, you will get a Plot Failed, plot was empty. message. Once data collection becomes regular, viewing plots is easy, since the Vista user knows when and what type of data is being collected.
1.4.4 Supported BrowsersOpera and Konqueror are not supported. All later versions of Netscape and IE are supported with one exception. IE 5.5 has a bug affecting javascript popup windows and is therefore NOT SUPPORTED. IE 5.5 users should switch to the latest greatest IE, move back to 5.0, or use Netscape.
1.4.5 Bug Reports / SupportPlease report any bugs to Brett Drake or Adriane Sullivan. A current list of contacts is available at WHAM's Contacts Page.
1.4.6 ConclusionIf you want to see plots now, select the IDV and fill in the requested fields. To learn more about viewing plots on the fly, look at the Interactive Data Viewer help section. Thanks for using the1.0 Vista Installation And Configuration Guide! The2.0 Vista User's Guide is the remainder of this help file.
Vista's main components are the Interactive Data Viewer for defining and viewing data plots on the fly, the Static Data Configurator for defining plots to be created in batches, and the Static Data Viewer for viewing the batched plots.
2.1.1 Interactive Data Viewer (IDV)To view a plot, go to the Interactive Data Viewer and fill in the requested fields.
2.1.1.1 Fields / FunctionalityThe Host field contains all the hosts for which there is data. Just because a host is present, does not mean that the data you request must be present. For instance, a request could be made for process data for a nonexistent process. Furthermore, process data may not even be collected for that host (check the hist.conf configuration file). Finally, data may not exist for a certain date range. All of these problems generate a Plot Failed:Plot was empty. message.
Process ,Device, and Top Number fields are sometimes required depending on the metric. (BBD metric category here)
Note that drm_hist's TopNumber is not the default for this field! drm_hist's TopNumber relates to the CDC, whereas Vista's Top Number prompt relates only to the top plot that is currently being defined.
Begin and End are the starting and ending date and times, inclusive.
Sample Size allows the user to change the number of points that get used for the plot. If Sample Size is set to Default, the data's original sample size is used. The data's sample size is determined by hist.conf's
Interval and SampPerInt variables. The Vista defaults for these variables are 5 for Interval and 300 for SampPerInt. 5 minutes = 300 seconds. 300 / 300 = 1 sample per second. Interval may be set as low as 1 with a SampPerInt equal to 60. 1 minute = 60 seconds. 60 / 60 = 1 sample per second. These cases might appear to be same, but they are not.Each Interval will produce 1 data point which is an average of that interval. So for the first case (
Interval = 5, SampPerInt = 300), for an hour's worth of data, we would graph 60 / 5 = 12 points of data. For the second case (Interval = 1, SampPerInt = 60), for an hour's worth of data, we would graph 60 / 1 = 60 points of data.For viewing a plot spanning a year, a larger interval would be wise since this reduces the number of data points and produces a less cluttered graph. For plots that span minutes, a smaller interval would work best so that the plot has enough points to capture data at a finer level.
In practice, an
Interval of 5 and SampPerInt of 300 or 150 is recommended. Then to change the sample size, just select a new one with the Sample Size field. The data will be averaged to be at the new sample size.Note that data can only be generalized with the Sample Size field. If data with an Interval of 5 minutes is present, these data points are easily changed to 10 minute data. However, 10 minute data can not be made into 5 minute Data.
Plot Size may be Small (380x300 pixels), Medium (491x386 pixels), or Large (619x488 pixels).
Select Reset to clear all the fields.
The Add Column, Delete Column, Add Row, and Delete Row are used for defining multiple plots on a singe page. This feature is useful when needing to show multiple plots defined on the fly (as opposed to using the Static Data Viewer to show a group of the same plots generated in batches). Once you are looking at the necessary plots, bookmark the resulting URL for use later or cut, paste, and email it to a concerned party so that they can view your plots with a single click.
Select the Plot button after you have filled in all other fields.
2.1.1.2 The IDV And The plotcache, arch And rpt Directories (What Happens After The Plot Button Is Pushed?)After Plot is clicked, each plot request must be filled. First, Vista checks the plotcache directory to see if this plot has already been generated. If the plot file is found, that request is done. All IDV fields must match exactly for the plotcache to be reused. The plotcache directory is specified in the global.sh configuration file by the
PLOTCACHE_DIR variable.If the plot isn't in the plotcache yet, then the arch and rpt directories are searched for data that fits the request. The rpt directory is checked for processed data. If the data isn't there, then it is generated from the arch directory and saved in the rpt directory for next time (this one-time process is called generating intermediate data). The arch and rpt directories are global.sh's
RAW_DIR and RPT_DIR variables. 2.1.1.3 The IDV / Browser Relationship (Why Does My Browser Appear Locked Up?)If processing is required, the browser displays Please Wait... messages for unfinished plots and waits till a plot is complete. This wait could be a long time (minutes) depending on how large the date range is, how many plots are being performed in parallel, and most importantly, how much intermediate data must be generated. Although intermediate data generation takes time, it is only performed once per metric category for any specified time frame. While the IDV is creating plots, the browser appears locked up. Since the browser is waiting, the Stop button is active. Selecting the browser's Stop button cancels the plot(s). The page is refreshed each time a plot is completed (if you are only doing one plot, then you are done).
2.1.2 Static Data Viewer (SDV)The SDV makes the plots that are defined by the Static Data Configurator available for viewing.
All plots are organized in an intuitive tree view. All the hosts for which plots have been created are shown with arrows next to them. Click the arrows to expand a tree showing the plot types, with more arrows. Click the plot type arrows to see what metrics are available for that plot type. Click the arrow next to a metric to see the plots available. Click a date link to see the plot in a new browser window.
The SDV looks for plots in the staticplots directory (
SP_DIR from global.sh). The BBD batchplot program runs out of cron to generate the plots. 2.1.3 Static Data Configurator (SDC)Most users may want to check a certain set of metrics on a regular basis. To avoid having to repeatedly fill out the IDV form, there exists the Static Data Configurator. This component controls what plots are automatically created for you usually overnight by the BBD batchplot program. The SDV does not control what data is collected by the CDC--the data must already be collected (BBD see store data).
BBD Update this:First, define groups of hosts and metrics as you choose. Second, add rules using the groups you defined or individual hosts and metrics. Three types of plots can be generated - Daily, Weekly, and Monthly. Daily is a single day from midnight to midnight. Weekly is a single week beginning Monday. Monthly is a single month beginning on the first day of the month. The Daily plots give a more detailed view of the data, whereas the Weekly and Monthly plots allow you to see trends or identify problem days. A rule translated to english might be: "Plot System CPU for myhost1 Daily and keep the last 7 at all times" or "Plot all the metrics in mymetricgroup for all the hosts in myhostgroup Weekly using a 1 hour sample size and keep the last 4 at all times".
Every night, if you have a rule that specifies "Keep Last 7 Daily", for example, a plot will be generated for the previous day. For "Keep Last X Weekly", a plot will be generated for the current week starting Monday. For "Keep last X Monthly", a plot will be generated for the current month beginning on the first. A separate process (sprune? BBD) will delete some plots if there are more than the number you've told it to keep. The "Keep Last" value applies only to a single rule. If you don't specify a "Keep Last" value, it will use the default, which you can set at the top of the page. You cannot specify both Daily and Weekly, for example, in a single rule. You'll have to use two rules to accomplish this.
2.1.4 batchplotFor batch plotting, plots are defined in the Static Data Configurator and are viewable using the Static Data Viewer but how are the plots created?
The batchplot utility creates the plots. Usually, the Vista administrator puts this utility in the crontab on the server so that batchplot can create the plots periodically (see section 1.3.2.3 Crontab Entry For Batch Plots). However, static plots may be generated any time by running batchplot by hand--a quick way to generate bunches of plots whenever they are needed.
The following variables may be present in global.sh and help control the assignment of time ranges to static plots:
| BATCH_DAY_START_HOUR | - | starting hour in military time |
| BATCH_DAY_STOP_HOUR | - | ending hour in military time |
| BATCH_SEVEN_DAY_WEEK | - | use seven day weeks? |
BATCH_DAY_START_HOUR="8" BATCH_DAY_STOP_HOUR="18" BATCH_SEVEN_DAY_WEEK="0"
Note that all values are strings and BATCH_SEVEN_DAY_WEEK should either be "1" for a 7 day week or "0" to produce weekly and monthly plots containing a 5 day week.
batchplot supports the following command line options:
batchplot [-m month -d day -y year[-r hourspan]
When run without arguments, batchplot uses today as the current date when assigning time frames to all plots.
2.1.5 cachedisknet1.3.2.2 Crontab Entry For Data Maintenance briefly discusses running cachedisknet. This utility collects the names of disk and system devices so a drop down list may be provided for metrics which require a disk or network device. The IDV's "can not discover" message means that this utility needs to be run. Placing cachedisknet in the cron will keep all disk and network device lists up to date.
2.1.6 spprune1.3.2.2 Crontab Entry For Data Maintenance briefly discusses running spprune. This utility enforces the "Keep Last" feature for batch plots by removing static plots whose time has expired. Running this script is optional--if this utility is never run, then static plots will not be deleted.
2.1.7 comparch.sh1.3.2.2 Crontab Entry For Data Maintenance briefly discusses running comparch.sh. Running this script is optional. This utility compresses CDC data stored in the RAW_DIR. All RunDirs are compressed for a host except for the latest one. Vista can work with the compressed data, but there is a slight performance hit when generating intermediate data (the one-time process discussed in 2.1.1.2 The IDV And The plotcache, arch And rpt Directories (What Happens After The Plot Button Is Pushed?) and 2.1.1.3 The IDV / Browser Relationship (Why Does My Browser Appear Locked Up?)).
2.2 Storing Data For VistaThe CDC documentation discusses Data Set Directories in chapter 6. Here is an overview of this concept as it relates to Vista.
Each run of drm_hist generates data resulting in the creation of one RunDir per host.
Assume for this example that we have these values:
global.sh:
RAW_DIR="/usr/local/webcruncher/arch"hist.conf:
DataDir:
/usr/local/webcruncher/arch
BothHosts:
bigmac fries
RunTime:
01:00:00
And the rundrmhist.sh script is executed once on July 24, 2000 at exactly 8:00 am.
Then data would be collected and stored in
/usr/local/webcruncher/arch/bigmac/Run964443600and
/usr/local/webcruncher/arch/fries/Run964443600That data is now available to Vista.
964443600 is the number of seconds elapsed from 00:00:00 on January 1, 1970 to 08:00:00 on July 24, 2000.
2.2.2 The rpt Directory (RPT_DIR From global.sh, DestDir In hist.conf)drm_hist creates either daily or weekly reports based on hist.conf's
ReportType variable. Fully described in the CDC documentation, these reports are stored in hist.conf's DestDir in the appropriate host directory. DestDir is usually set to the same value as global.sh's RPT_DIR. 2.2.2.2 Processed DataVista uses the RPT_DIR as a storing place for intermediate plot data. The directory structure created is similar to the one under the RAW_DIR but contains metric or process specific processed data.
2.3 MetricsAs it relates to Vista, a metric is a plot showing measurements that facilitate performance tuning. BBD (link)Sys CPU Usage is an example of a Vista metric. A Sys CPU Usage plot shows four measurements: System, User, Wait, and Idle time as a percentage of total CPU time. These four measurements would be called metrics in the classical sense. Technically speaking, a Vista metric is actually a plot showing one or more metrics. In this documentation and in the Vista product itself, the term metric may be used to refer to a single plot, or it may describe one of the values graphed on a plot.
2.3.1 Metric CategoriesA metric's category is easily defined by the type of additional data required to use that metric. At a lower level, a metric category relates to running a specific option for one of these CDC tools: daily_procrpt, procrpt, spread_sys.awk, or spread_sys.disknet.awk described here.
2.3.1.1 SystemSystem metrics apply to a host (as opposed to a process or group of processes), and therefore require no additional data.
2.3.1.2 Single Process / DBSingle Process / DB metrics apply to a single process by name (not PID). Process prompts may contain a list of process names seperated by commas. Also, the * may be used as a wildcard that matches any string.
2.3.1.3 Web ProcessesWeb metrics usually involve a Web Server, Application Server, and CGI Process List. However, the only required field is the Web Server. In either the IDV or SDV, when prompted for the process for a Web metric, seperate the processes by colons.
Examples:
webproc:appproc:cgi1,cgi2,cgi3
Or:
webproc:apppro*
Disk metrics require that the user choose the disk device or harddrive. In the (BBD link)IDV, the user chooses from the drop-down list provided. The SDV(BBD link) does not provide a drop down list (yet!).
2.3.1.5 NetworkDisk metrics require that the user choose the network device or NIC. In the (BBD link)IDV, the user chooses from the drop-down list provided. The SDV(BBD link) does not provide a drop down list (yet!).
2.3.1.6 Top NTop N metrics do processing of the most significant group of processes. If a user provides a Top Number of 5 for the Top N Processes CPU(BBD link) metric, a histogram will be created showing the top 5 CPU consumers. The Top Number should be a positive integer.
2.3.1.7 Under The Hood (How can I use the data?)Other tools are run besides those mentioned here. This information is provided to assist the end user in using WHAM data for other applications. Vista intermediate data generation by hand is neither supported nor suggested!
| Category | RAW_DIR (src) | CDC Tool | RPT_DIR (dest) |
|---|---|---|---|
| System | sys.tot | spread_sys.awk | sys.tot.smp |
| Disk | sys.tot | spread_sys.disknet.awk | sys.tot.wcdisk |
| Network | sys.tot | spread_sys.disknet.awk | sys.tot.wcnet |
| Process | tmp#/host.proc_rpt | daily_procrpt -n | proc_rpt.smp.process |
| Web | tmp#/host.proc_rpt | daily_procrpt -w -a -c | proc_rpt.web.process |
| DB | tmp#/host.proc_rpt | daily_procrpt -d | proc_rpt.db.process |
| Top N | tmp#/host.proc_rpt | procrpt -R -n | proc_rpt.top |
| Web-specific Metrics |
| Web Get/Send Times |
| Web Time per Get |
| Web Send Data |
| Db Transactions |
| DB Xaction Count |
| DB Xaction Rate |
| DB CPU Utilization |
| DB Service And Delay |
| DB Disk Activity |
| DB Xaction Times CPU |
| DB Xaction Times Disk |