Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45288

Responding time graphs should ignore samples with error - Customisable by user

      Current Behaviour : Responding time graphs of each URI generated by Performance Plugin includes responses with errors. This current behaviour is described in the resolved issue JENKINS-26988.
      From our point of view, this behaviour does not give a good view of the quality of the service and leads to confusion. This behaviour should be customisable by the user
      => [Ignores or includes errors in response time]

      Example :
      -> The 2 regular criterias for a Service Level Agreement are Response Time and Error Rate.
      -> Errors can either be timeout of the 3rd party (leads to extra long response time) or Front end global error (leads to extra short response time).
      => In case of Error Rate increase between 2 builds, the responding time graphs are highly modified and show an unstability of response times, even if the application have super stable response time (success cases).

      As attached,

      • an example of the current behaviour (responding time including error response)
        => At first view, a high instability of response time !!
      • the same result source (.csv) but for not successfull responses we have suffixed the URI by _error
        => High stability of response time (120sec) but an high rate of errors

      Best regards,

      Quentin

          [JENKINS-45288] Responding time graphs should ignore samples with error - Customisable by user

          Quentin Bernard created issue -
          Quentin Bernard made changes -
          Attachment New: AFTER - errors URI prefixed by _errors.png [ 38737 ]
          Attachment New: BEFORE - errors into Responding Time Graphs.png [ 38738 ]
          Description New: +*Current Behaviour*+ : Responding time graphs of each URI generated by Performance Plugin includes responses with errors. This current behaviour is described in the resolved issue JENKINS-26988.
          From our point of view, this behaviour does not give a good view of the quality of the service and leads to confusion. This behaviour should be customisable by the user
          => [Ignores or includes errors in response time]

          Example :
          -> The 2 regular criterias for a Service Level Agreement are Response Time and Error Rate.
          -> Errors can either be timeout of the 3rd party (leads to extra long response time) or Front end global error (leads to extra short response time).
          => In case of Error Rate increase between 2 builds, the responding time graphs are highly modified and show an unstability of response times, even if the application have super stable response time (success cases).

          As attached,
          - an example of the current behaviour (responding time including error response)
          => At first view, a high instability of response time !!
          - the same result source (.csv) but for not successfull responses we have suffixed the URI by _error
          => High stability of response time (120sec) but an high rate of errors


          Best regards,

          Quentin

          Labels New: jmeter performance
          Andrey Pokhilko made changes -
          Issue Type Original: Bug [ 1 ] New: Improvement [ 4 ]

          Artem Fedorov added a comment -

          This feature was added in https://github.com/jenkinsci/performance-plugin/pull/134 and will be available in version 3.3
          Thanks

          Artem Fedorov added a comment - This feature was added in https://github.com/jenkinsci/performance-plugin/pull/134  and will be available in version 3.3 Thanks
          Artem Fedorov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            undera Andrey Pokhilko
            quentinb Quentin Bernard
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: