From a JZR recording, the Jeyzer Replay displays the internal dynamics of the monitored process through a viewer.
Viewer is prototype application at this stage.
This is the movie of the incident occurrence.
Command
To start the Jeyzer Replay execute the command jeyzer-replay.bat or jeyzer-replay.sh, located under the analyzer\bin directory of your Jeyzer installation.
By default, it is configured to perform the replay of the Jeyzer demo features application recording.
Prerequisites
These environment variables must be set to target the right profile :
JEYZER_TARGET_PROFILE: the target master profileJEYZER_TARGET_NAME: the application node name.
Identifies the process instanceJEYZER_RECORD_DIRECTORY: the Jeyzer snapshot recording directory
Installation
Jeyzer Installer : Select the Jeyzer Analyzer Console component.
The Jeyzer Installer will guide you in the high level setup.
Check the quick_start.html at the Jeyzer installation root : it contains useful paths.
Configuration
Jeyzer Replay configuration relies on :
The following environment variables control the Jeyzer Replay :
| Variable | Description | Default value |
| JEYZER_GRAPH_REFRESH_PERIOD | The graph refresh period | 4 seconds |
| JEYZER_DYNAMIC_GRAPH_MODE | Indicates if the actions must be merged or not Choose the action_merged if the process did execute a large number of similar actions : thread counter is then displayed. Possible values : action_single, action_merged | action_single |
Set it externally or within the jeyzer-replay.sh/bat
Graph generation configuration
The graph generation is controlled through standard configuration files available in the analyzer/config/graph/player directory of your Jeyzer installation.
This configuration location can be customized in the <JEYZER_TARGET_PROFILE>_analysis.xml available in the master profile directory.
See the function graph player and the contention graph player sections for more details.
Display
Each thread or thread aggregation is shown as a filament with a thread name at one end and the thread state at the other end.
Functions and operations are displayed in the middle, respectively in blue and green circles : circle size is growing with time to represent activity concentration.
Thread name is displayed with a pink square.
Square becomes red in case of high CPU usage.
Thread state (running, locked, deadlock) is displayed respectively in green, orange and red.
Previous activity of the threads can be displayed as phantomized : nodes are then greyed out and will stay for a configurable amount of time.
No activity detection message is displayed if no active threads are found.
Missing recording snapshot file message is displayed if a recording snapshot hiatus is found.
Logging
Jeyzer Replay relies on the logback framework.
The replay-logback.xml drives the console and file logging.
It is located in the analyzer/config/log directory of your Jeyzer installation.
Logging is set to INFO by default, which is not invasive.
Logging settings can be changed at runtime (no need to restart).
Log file is generated under the recording directory which is by default :work/recordings/<application recording>/log
Outputs
There are no outputs.