Recording

  2. Home
  4. Docs
  6. Recording
  8. Monitoring
  10. Simple monitoring

Simple monitoring

Simple monitoring focuses on one Java application.

Important : if you deploy the Jeyzer Monitor in production, we do recommend to install it on a different server than the production one, typically a monitoring server, this to limit at the minimum the performance impact.
This server must have access to the Jeyzer recording directory.

Deployment steps

  • Install the Jeyzer Monitor with the Jeyzer Installer.
    Select the Jeyzer Monitor component when requested.
    Choose to create your first master profile when requested.
    Let’s call it first-profile. It will serve as template hereafter.
  • Deploy the master profile of your application within the profiles/external/master directory of your Jeyzer installation.

    PS : if your master profiles are already accessible from on a shared drive, update the JEYZER_EXTERNAL_MASTER_PROFILES_DIR variable in the analyzer/bin/set-jeyzer-paths.bat.
    This step applies if you intend to use the Jeyzer Web Analyzer.
  • Create the monitoring start script.
    In the analyzer/bin/preset/first-profile directory of your Jeyzer installation, duplicate the directory and rename it to reflect your application.
    This directory contains a first-profile_monitor.bat suffixed file. Rename it as well.
    Edit the file and set the JEYZER_TARGET_PROFILE with the name of your master profile : it must be the directory name of the master profile you deployed previously.

    Adapt the JEYZER_MONITOR_SCAN_PERIOD to your needs : by default the Jeyzer Monitor will scan the recording every 5 minutes which is appropriate.
    It must be higher than the Jeyzer Recorder period (JEYZER_RECORD_PERIOD) and lower than the archiving offset (JEYZER_RECORD_ARCHIVE_TIME_OFFSET).

    The JEYZER_RECORD_DIRECTORY is pointing to the directory that contains the JZR snapshots (and not the archive directory that contains the JZR recordings) : change it if it resides in a different location (which would be issued from another Jeyzer installation).

    The JEYZER_TARGET_PROFILES_DIR is pointing to the master profile root directory (that should now contain your master profile) : change it if’s located in a different location (like a shared drive).
  • Test the monitoring : execute the script you created previously.
    Check the monitoring outputs : by default the Jeyzer Monitor log, the analysis outputs are generated under the recording directory of the monitored application : work/recordings/<master profile name>
    The monitoring web outputs are by default generated under the Tomcat deployed by the Jeyzer installer : web/apache-tomcat-9.0.41/jeyzer-webapps/jeyzer-monitor
  • Once ready, call the monitoring start script from your running platform (APM, cron tab, QA script..).
    If the monitored application is not yet available, the Jeyzer Monitor will simply wait for it.