1. White Star Software
  2. Advanced Alerting Configuration

User Experience

User Experience

These daemon processes measures database read performance 3 ways:

  1. shared memory
  2. client-server via the localhost network connection (lh)
  3. client-server over a true network connection, executed from another server in the LAN (cs).

Shared Memory

Measurement is automatically done by the pt3agent.

Localhost

Measurement is done by a local and independently running _progres -p zippyng.p daemon process, typically launched through schedule.cfg. It creates a file $PROTOP/log/zippyng.[friendlyName].lh.log which is read by the appropriate pt3agent which in turn uploads the data to the ProTop web portal.

To enable User Experience Localhost in etc/schedule.cfg, edit etc/schedule.[site].cfg and add the following line:

#### *nix

 0,15,30,45 * * * * zippyng.sh <friendlyName> lh <service> >> ${PTTMP}/tasksched.err 2>&1 [NOALERT] 

#### Windows

 0,15,30,45 * * * * cmd /c zippyng.bat [friendlyName] lh [service] >> %TMPDIR%\tasksched.zippyng.err 2>&1 & [NOALERT] 

Client Server

Measurement is done by an independently running _progres -p zippyng.p daemon process, running on another server in the LAN. Similar to User Experience Localhost, the process is typically initiated via schedule.cfg and creates a [PROTOPDIR]/log/zippying.[friendlyName].cs.log file. However, since the corresponding pt3agent is not running on the remote server, the log file needs to be copied to the database server.

To enable User Experience client-server in schedule.cfg:

  1. Configure the remote copy command by creating the file [PROTOPDIR]/bin/zipenv (%PROTOP%\bin\zipenv.bat on Windows) and inserting the following line:

    *nix:

    Replace [SERVER] below with the server name or address of the DB server where the pt3agent is running.

    NOTE ssh keys must be setup to allow password-less ssh from the remote server to the DB server.

    export ZIPSYNC="rsync -avzqe ssh ${LOGDIR}/zippyng.${FRNAME}.log [SERVER]:/logdir 1>${TMPDIR}/zippyng.${FRNAME}.err 2>&1" 

    Windows:

    Replace the highlighted text with the correct UNC path to the %PROTOP%\log directory on the DB server where the pt3agent is running.

    Test permissions as the DBMonitor and zippy process will run using the SYSTEM account.

    Typically you will need to enable “Everyone - write” permissions (in french “tout le monde”).

    set ZIPSYNC=copy /y %LOGDIR%\zippyng.!FRNAME!.log \\ServerName\d$\protop\log\zippyng.!FRNAME!.log >> %PTTMP%\zipsync.copy.err 2>&1" 
  2. NOTE: If the other server is configured for ProTop with the same siteName, skip this step as the dblist.cfg file will be downloaded from the ProTop web portal. Otherwise, copy the appropriate resource line from [PROTOPDIR]/etc/dblist.cfg on the DB server to [PROTOPDIR]/etc/dblist.cfg on this server.

  3. Edit schedule.[site].cfg and uncomment/modify zippyng.sh line

    *nix

    0,15,30,45 * * * * zippyng.sh [friendlyName] cs [host] [service] >> ${PTTMP}/tasksched.err 2>&1 [NOALERT] 

    Windows

    0,15,30,45 * * * * cmd /c zippyng.bat [friendlyName] cs [host] [service] >> %TMPDIR%\tasksched.zippyng.err 2>&1 & [NOALERT] 
  4. Verify data is flowing to the portal by selecting the resource from the Portal Dashboard (click the resource name or right click on the resource line and select Trend Data) and you will be directed to ProTop Trends. Here you should see User Exp data reported in the BogoMIPS graph on the Main Dashboard. It is the second graph under General info at the top of the page.

Note:

  • [friendlyName] = friendly name in dblist.cfg
  • [host] = hostname of the database server
  • [service] = service name or port number of the remote database

Parameter Files (pf) for User Experience Monitoring

If a resource has a type defined in [PROTOPDIR]/etc/dblist.cfg, and there is a parameter file named [PROTPDIR]/etc/type.pf, it is added to the _progres command line for all three types of user experience monitoring listed above.