Please or Register to create posts and topics.

Jeyzer 2.6 release available !

Check it out on Docker or download the Jeyzer installers.

Release notes :

Jeyzer Analyzer

  • Automatic loading of master profiles (JEYZ-39)
    This new functionality permits to dynamically load a master profile based on a remarkable pattern found in the recording.
    In practice, the analysis is started using the generic profile in the Jeyzer Web Analyzer and will end up by generating the JZR report using the right applicative profile.
    This new functionality is possible thanks to the profile redirection mechanism : a generic profile (such as Portal) will usually provide the profile redirection
    while the applicative profiles (ex : AMQ) will provide one or several remarkable patterns.
    Those remarkable patterns are typically application package or class unique names (ex for AMQ : org.apache.activemq.console.Main).
    The master profile redirection is optional. If not defined, the current master profile cannot participate in a profile redirection process.
    The master profile redirection is only supported by the Jeyzer Web Analyzer.
    The JZR Session details sheet indicates if the profile redirection occured by providing the initial generic profile name and final applicative profile name.
    To support the profile redirection mechanism, add the following entry in the <profile>_analysis.xml in your generic profile :
    <profile_redirection enabled="true">
    To declare the remarkable patterns of an application, add the following entry in the <profile>_analysis.xml in your applicative profile :
    <id_pattern value="org.my_application"/>
    As part of this implementation, the existing discovery mode has been renamed as discovery rules and moved within the discovery configuration section :
    <discovery_rules enabled="true"/>
    The discovery_mode section is however still supported as part of the backward compatibility.
  • JZR report : group sequence sheet (JEYZ-38)
    The group sequence sheet focuses on similar stacks and is therefore very useful when dealing with large multi-threaded/asynchronous based applications.
    Each group of similar stacks will have its own cell in the report for a given recording snapshot.
    When a group is observed on consecutive recording snapshots, the related cells get displayed on the same line : it constitutes a group action.
    The group sequence sheet is a new type of sheet inspired from the sequence sheet and therefore follows the same configuration structure.
    To display it, add the <sheet sheet_config_file="${JEYZER_ANALYZER_CONFIG_DIR}/report/sheet/group-sequence/group-sequence-stack-groups.xml"/> in your JZR report configuration.
    To accomodate the display, new row headers and cell attributes have been created :
    Row header
    group_id : displays the group action id.
    group_size : displays the total number of stacks within the group action.
    Cell attribute
    group_size : displays the stack group size. Example : x25
    Group sequence sheets do not support freeze, CPU, memory and MX attributes as those do not make sense.
  • JFR analysis support extended (JEYZ-31)
    JFR can now be provided as zip file.
  • Analysis stack ordering support (JEYZ-36)
    It is now possible to sort the stacks in the analysis by thread name, thread id or recording appearance (original behavior).
    The sorting key (thread_name, thread_id or recording) can be specified in the analysis profile (<profile>_analysis.xml) :
    <sorting key="thread_name"/>
    If not available, the sorting key is defined in the default setup (default_setup.xml) which is thread_id.
  • The Task sequence lock_state cell rule is now displaying the class name on which the lock is put on. (JEYZ-33)
    It is appended at the end of the lock information, in lower font size.
  • Instana file format analysis support (JEYZ-32)
  • Bug fix JEYZ-35 : Task sequence default sorting was done in reverse order
  • Bug fix JEYZ-40 : JZR recording parsing failed when the analysis profile contains a txt file regex pattern
  • Bug fix JEYZ-41 : Failed to generate the Action distinct profiling sheet due to comparison violation error
  • Bug fix JEYZ-42 : The daylight saving time was incorrectly handled in the monitoring event time display

Jeyzer Analyzer Web server

  • Automatic loading of master profiles (JEYZ-39, see Jeyzer Analyzer).
    The profile redirection applies on the master profile repositories accessed by the Jeyzer Analyzer Web server,
    assuming those master profiles are configured correctly.
  • Improve the end user notification when recording contains no parseable files (JEYZ-37)
    Make the notification as a warning instead of error, and list the supported file formats.

Jeyzer Monitor

  • New system monitoring rule : Recording size
    If the number of recording snapshots (thread dumps) is larger or lower than the specified threshold, generate an event. (JEYZ-34)
    A default standard rule has been added to emit an info message to recommend going for a proper periodic recording instead of single thread dump.
  • New standard monitoring rule stickers :
    Environment : Java agent presence, windows service, debugging in progress..
    Analysis : recording size..

Jeyzer Recorder

  • Nothing new
    PS : the Jeyzer Recorder installer has been updated to ship the 2.6 version of the Jeyzer demos (as below)

Jeyzer Demos

  • The Demo features MX provides now remarkable patterns for the profile redirection (JEYZ-39)
  • The Recording size monitoring rule is now supported inside the demos (JEYZ-34)

Jeyzer Base repository

  • Automatic loading of master profiles (JEYZ-39) :
    - The Portal generic profile supports the profile redirection.
    - All base production master profiles do provide now remarkable patterns for the profile redirection.
  • Daml master profile added
  • Hybris (SAP product) master profile added
  • Postgresql shared profile added
  • Logback shared profile added
  • Instana (Java agent) shared profile added
  • Tanuki shared profile added

Upgrade instructions (optional)

  • Profile redirection :
    Update the <application>_analysis.xml file of your generic master profiles to add the profile redirection (as indicated above).
    Verification : generate a JZR report, in the Session info / Analysis section, check that the Master profile discovery field is set to active.
    Update the <application>_analysis.xml file of your application master profiles to add the remarkable patterns (as indicated above).
    Verification : generate a JZR report using a master profile configured for the profile redirection (like the Portal one).
    In the Session info, check that the Redirected master profile field is set with the application master profile.
    Update all the <application>_analysis.xml files to handle the discovery mode configuration declaration change (as indicated above).
  • Group sequence sheet
    Add the group sequence sheet to your JZR report definitions (as indicated above).
    Verification : generate a JZR report and check that the Stack groups sheet is now available.