Status

DONE

AuthorKorina Charokopou

Feature No.

ODP-6437 - Getting issue details... STATUS

Test Case No.

ODP-7398 - Getting issue details... STATUS

General Description of the Feature

This feature is relevant to the consulting and support teams that need to be able to record on demand logs relevant to performance issues.

With the development and enablement of this "Performance logger", admin users having the relevant permission, can enable the logger, to provided Users. The logger will remain active for 10 minutes and during this time a log is recorded with all the actions the given user is performing including mainly results about the system performance.

Performance logger activation

To enable the recording, the user must select the action "Start Performance Recording", which is located at the bottom of the Profile Menu.

When activated, a red banner is displayed at the center bottom of the screen which includes the following:

  1. The Session Code
  2. A count-down timer displaying the remaining time from the activation or last refresh.
  3. A "Stop" button, which stops the recording before the end of the timer. 
  4. A "Refresh" button, which refreshes the remaining timer, if more time than 10 minutes is required. On each refresh the time will start again from the 10 minutes mark.
  5. An arrow that shows/hides the red recording fly-out.

The recording can stopped with two ways:

  1. from the stop button on the recording fly-out.
  2. from the action "Stop Performance Recording" at the bottom of the Profile Menu.

Once the recording has stopped, the recording fly-out will change into a banner that remains visible until the user refreshes the page. The banner includes the following message, which can be used to communicate the relevant recording to the 3rd level support for further investigation to the performance issues the user faced.

Message: "Please contact support with the following recording session code: <<code>>"

Performance recording - logs

Once the recording is ready, relevant logs can be found in the Mongologs. Results related with the session code should be recorded and available under the relevant DB in the collection "MonitorProfilerResult".

  • This collection can be filtered as “Simplified” or “Sessions”, where it shows all the requests made to OneDealer or grouped based on the session ID respectively.
  • Sub-filters can also be used, to filter based on the user and the session ID.
  • Each request can be examined even more with the action "View Profiler Result" (on right-click of the relevant request). A new page with the timings of the selected specific request, opens, providing more in depth information.

Business Benefit

A tool implementation that provides the possibility the 1st level support, to quickly enable a logging and generate a "log file" containing all necessary performance information. This log code can be handed over to the 3rd level support, to be analyzed properly and efficiently.


Configuration 

Business Cases:

  • 70000 - AccessPerformanceLogger

Systemic (IT: appSettings.config)

  • Key: MonitorProfilerStorage
    • possible values “None” & “Mongo”
Write a comment…