EV Observe - Synthetic Monitoring Module - Viewer

Last modified on 2023/09/28 16:52

   The Viewer is part of the load testing features.

The Viewer allows you to have a complete view of all the RDP sessions open on Injectors and control load tests by launching the different scenarios.

Description of the screen

          Viewer.png

List of machines

  • Machine Key: Key of the machine on which the RDP session is open.
  • MachineName: NetBIOS name of the machine.
  • SessionName: Logon used to open the RDP session.
  • SessionStatus: Real-time session state (Opened, PlayerIdel, etc.).
  • ScriptName: Name of the loaded scenario.
  • ActiveTransaction: Name of the transaction that is running.
  • Result: Status of the scenario at the end (Success, Failed, etc).
  • JobQ_IsActive: State of the scheduler of the scenario (active or non-active).
  • JobsInQueue: Number of iterations remaining to play.
     

Contextual menu for a machine
Right-click on a line to open a contextual menu.
         Viewer - Contextual menu for a machine.png

Best Practice icon.png  You can select multiple lines to apply the same actions to selected machines.

  • Load Task: Allows to load a task related to the scenario to be played on the selected RDP sessions. Once loaded, the task remains pending.
  • Load and Execute Task: Allows to start a task immediatly on the selected RDP sessions.
  • Start Job Queue: Conditions for launching the scenarios related to the selected RDP sessions.
    • 0: Allows to launch the scripts every x seconds.
    • Range(s): Allows to launch the scenarios all seconds randomly between 2 values.
       

      Note: It concerns the same Injector RDP sessions.

    • Range by MachineKey(s): Allows to launch the scenarios all seconds randomly between 2 values.
       

      Note: It concerns RDP sessions of several Injectors.

    • Only when scenarios are loaded and ready to be played on the selected machines, you can define a time interval (in seconds) for scenario startup on the different RDP sessions.
       

      example  The scenario on the session No. 2 will start 10 seconds later than on the session No. 1.

  • Unload Player Batch: Allows to unload scenarios on the selected RDP sessions.
  • Interrupt Job Queue: Allows to interrupt scenarios in progress on the selected RDP sessions.
  • Exec back Cmd: Allows to run a BACK command.
  • ClearQueue: Allows to remove pending iterations (JobsInQueue).
  • End Sessions(s): Allows to close RDP sessions.
  • Reload: Allows to refresh the treeview.

Loading a scenario

You can load a scenario in two different ways: natively or learning batch mode.

  • Native mode: In case of error, the scenario will stop.
  • Learning batch mode: In case of error, the scenario will stop and return the hand to the user to define the actions to be taken, in the same way as the learning mode.
    The user can edit the scenario within the session, for example by adding an image or changing the precision.
    Once the scenario is complete, there are two possible cases:
    • Changes do not require recompilation: The scenario modified in the session is directly available for the other sessions. There is nothing else to do.
    • Changes require recompilation: The system will unload the scenario from the other sessions and recompile it. The task must be reloaded and launched. Then the scenario is loaded and ready to be played.
Tags:
Powered by XWiki © EasyVista 2024