US 11,836,034 B2
Determining probable root cause of performance issues
Avi Ulman, Yehud (IL)
Assigned to Micro Focus LLC, Santa Clara, CA (US)
Appl. No. 16/094,052
Filed by ENTIT SOFTWARE LLC, Sanford, NC (US)
PCT Filed Apr. 22, 2016, PCT No. PCT/US2016/029035
§ 371(c)(1), (2) Date Oct. 16, 2018,
PCT Pub. No. WO2017/184180, PCT Pub. Date Oct. 26, 2017.
Prior Publication US 2020/0327004 A1, Oct. 15, 2020
Int. Cl. G06F 11/07 (2006.01); G06F 11/36 (2006.01); H04L 41/0631 (2022.01); H04L 67/02 (2022.01)
CPC G06F 11/079 (2013.01) [G06F 11/3636 (2013.01); H04L 41/0631 (2013.01); H04L 67/02 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A method to determine a probable root cause of a performance issue affecting a Hypertext Transfer Protocol (HTTP) transaction, the method comprising:
processing, using a processor, a set of calls for the HTTP transaction, wherein each call of the set of calls is associated with a set of parameters;
determining, using the processor, that a performance metric associated with the HTTP transaction is below a predetermined level; and
in response to determining that the performance metric is below the predetermined level, level:
identifying, using that the processor, a first plurality of calls of the set of calls for the HTTP transaction associated with the performance issue and a second plurality of calls for the HTTP transaction not associated with the performance issue;
identifying, using the processor, one or more parameters common to the set of parameters associated with each call of the first plurality of calls associated with the performance issue;
determining, using the processor, each of the identified one or more parameters common to the set of parameters associated with each call of the first plurality of calls are not in the set of parameters associated with each call of the second plurality of calls; and
based on determining each of the identified one or more parameters common to the set of parameters associated with each call of the first plurality of calls are not in the set of parameters associated with each call of the second plurality of calls, determining that the identified one or more parameters common to the set of parameters associated with each call of the first plurality of calls are the probable root cause of the performance issue affecting the HTTP transaction.