Method and apparatus for determining an index, server, and medium

1 . A method for determining an index, comprising:

receiving and storing event information into a memory, wherein the event information is reported by a plurality of clients using an application at a preset event tracking position, the preset event tracking position comprises a start event generation position, a result event generation position and at least one subsequent event generation position corresponding to an index to be determined, and the at least one subsequent event generation position is located behind a first result event generation position matching the index to be determined;

performing, by a server, duplicate removal processing on each piece of event information based on client identifier information in each piece of received event information, and determining a result execution count and a total execution count corresponding to the index to be determined, wherein the client identifier information comprises a session identifier corresponding to a session created when a client performs information interaction with the server;

determining an index result corresponding to the index to be determined based on the result execution count and the total execution count, wherein the index result is used to characterize a running performance of the application; and

optimizing the application based on the index result,

wherein performing, by a server, duplicate removal processing on each piece of event information based on client identifier information in each piece of received event information, and determining a result execution count and a total execution count corresponding to the index to be determined, comprises:

extracting, by the server, client identification information from each piece of event information received; identifying, by the server, duplicate event information reported by a same client; deleting, by the server, duplicate data; and caching, by the server, first event information after performing the duplicate removal processing;

retrieving or filtering, by the server, the first event information by using the session identifier, so as to determine the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information;

determining, by the server, the total execution count corresponding to the index to be determined based on start event information corresponding to each piece of client identifier information after the duplicate removal processing.

2 . The method according to claim 1 , wherein the index to be determined comprises a success rate index or a failure rate index corresponding to a preset behavior.

3 . The method according to claim 1 , wherein the determining the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information comprises:

performing second duplicate removal processing on the first result event information and the subsequent event information corresponding to identical client identifier information, determining a quantity of event information after the second duplicate removal processing, and taking the quantity of event information after the second duplicate removal processing as the result execution count corresponding to the index to be determined.

4 . The method according to claim 1 , wherein the determining, by the server, the total execution count corresponding to the index to be determined based on start event information corresponding to each piece of client identifier information after the duplicate removal processing comprises:

determining, by the server, the total execution count corresponding to the index to be determined based on the start event information, result event information and the subsequent event information corresponding to each piece of client identifier information after the duplicate removal processing.

5 . The method according to claim 4 , wherein the determining, by the server, the total execution count corresponding to the index to be determined based on the start event information, result event information and the subsequent event information corresponding to each piece of client identifier information after the duplicate removal processing comprises:

performing, by the server, second duplicate removal processing on the start event information, the result event information and the subsequent event information corresponding to identical client identifier information, determining a quantity of event information after the second duplicate removal processing, and taking the quantity of event information after the second duplicate removal processing as the total execution count corresponding to the index to be determined.

6 . The method according to claim 1 , wherein the determining the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information comprises:

obtaining time field information in the first result event information corresponding to each piece of client identifier information after the duplicate removal processing;

selecting first information of which elapsed time is less than or equal to preset elapsed time from the first result event information based on the time field information; and

determining the result execution count corresponding to the index to be determined under the preset elapsed time based on a quantity of the first information.

7 . A server, comprising:

one or more processors; and

a memory, configured to store one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a method for determining an index, the method comprising:

receiving and storing event information into the memory, wherein the event information is reported by a plurality of clients using an application at a preset event tracking position, the preset event tracking position comprises a start event generation position, a result event generation position and at least one subsequent event generation position corresponding to an index to be determined, and the at least one subsequent event generation position is located behind a first result event generation position matching the index to be determined;

performing duplicate removal processing on each piece of event information based on client identifier information in each piece of received event information, and determining a result execution count and a total execution count corresponding to the index to be determined, wherein the client identifier information comprises a session identifier corresponding to a session created when a client performs information interaction with the server;

determining an index result corresponding to the index to be determined based on the result execution count and the total execution count, wherein the index result is used to characterize a running performance of the application; and

optimizing the application based on the index result,

wherein performing, by a server, duplicate removal processing on each piece of event information based on client identifier information in each piece of received event information, and determining a result execution count and a total execution count corresponding to the index to be determined, comprises:

extracting, by the server, client identification information from each piece of event information received; identifying, by the server, duplicate event information reported by a same client; deleting, by the server, duplicate data; and caching, by the server, first event information after performing the duplicate removal processing;

retrieving or filtering, by the server, the first event information by using the session identifier, so as to determine the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information;

determining, by the server, the total execution count corresponding to the index to be determined based on start event information corresponding to each piece of client identifier information after the duplicate removal processing.

8 . A non-transitory computer-readable storage medium, storing a computer program, wherein the computer program, when executed by a processor, causes implementing of a method for determining an index, the method comprising:

receiving and storing event information into a memory, wherein the event information is reported by a plurality of clients using an application at a preset event tracking position, the preset event tracking position comprises a start event generation position, a result event generation position and at least one subsequent event generation position corresponding to an index to be determined, and the at least one subsequent event generation position is located behind a first result event generation position matching the index to be determined;

performing, by a server, duplicate removal processing on each piece of event information based on client identifier information in each piece of received event information, and determining a result execution count and a total execution count corresponding to the index to be determined, wherein the client identifier information comprises a session identifier corresponding to a session created when a client performs information interaction with the server;

determining an index result corresponding to the index to be determined based on the result execution count and the total execution count, wherein the index result is used to characterize a running performance of the application; and

optimizing the application based on the index result,

wherein performing, by a server, duplicate removal processing on each piece of event information based on client identifier information in each piece of received event information, and determining a result execution count and a total execution count corresponding to the index to be determined, comprises:

extracting, by the server, client identification information from each piece of event information received; identifying, by the server, duplicate event information reported by a same client; deleting, by the server, duplicate data; and caching, by the server, first event information after performing the duplicate removal processing;

retrieving or filtering, by the server, the first event information by using the session identifier, so as to determine the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information;

determining, by the server, the total execution count corresponding to the index to be determined based on start event information corresponding to each piece of client identifier information after the duplicate removal processing.

9 . The server according to claim 7 , wherein the index to be determined comprises a success rate index or a failure rate index corresponding to a preset behavior.

10 . The server according to claim 7 , wherein the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information comprises:

performing second duplicate removal processing on the first result event information and the subsequent event information corresponding to identical client identifier information, determining a quantity of event information after the second duplicate removal processing, and taking the quantity of event information after the second duplicate removal processing as the result execution count corresponding to the index to be determined.

11 . The server according to claim 7 , wherein the determining the total execution count corresponding to the index to be determined based on start event information corresponding to each piece of client identifier information after the duplicate removal processing comprises:

determining the total execution count corresponding to the index to be determined based on the start event information, result event information and the subsequent event information corresponding to each piece of client identifier information after the duplicate removal processing.

12 . The server according to claim 11 , wherein the determining the total execution count corresponding to the index to be determined based on the start event information, result event information and the subsequent event information corresponding to each piece of client identifier information after the duplicate removal processing comprises:

performing second duplicate removal processing on the start event information, the result event information and the subsequent event information corresponding to identical client identifier information, determining a quantity of event information after the second duplicate removal processing, and taking the quantity of event information after the second duplicate removal processing as the total execution count corresponding to the index to be determined.

13 . The server according to claim 7 , wherein the determining the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information comprises:

obtaining time field information in the first result event information corresponding to each piece of client identifier information after the duplicate removal processing;

selecting first information of which elapsed time is less than or equal to preset elapsed time from the first result event information based on the time field information; and

determining the result execution count corresponding to the index to be determined under the preset elapsed time based on a quantity of the first information.

14 . The non-transitory computer-readable storage medium according to claim 8 , wherein the index to be determined comprises a success rate index or a failure rate index corresponding to a preset behavior.

15 . The non-transitory computer-readable storage medium according to claim 8 , wherein the determining the result execution count corresponding to the index to be determined based on first result event information and subsequent event information corresponding to each piece of client identifier information in the first event information comprises:

performing second duplicate removal processing on the first result event information and the subsequent event information corresponding to identical client identifier information, determining a quantity of event information after the second duplicate removal processing, and taking the quantity of event information after the second duplicate removal processing as the result execution count corresponding to the index to be determined.

16 . The non-transitory computer-readable storage medium according to claim 8 , wherein the determining the total execution count corresponding to the index to be determined based on start event information corresponding to each piece of client identifier information after the duplicate removal processing comprises:

determining the total execution count corresponding to the index to be determined based on the start event information, result event information and the subsequent event information corresponding to each piece of client identifier information after the duplicate removal processing.