SYSTEM FOR DEFINING AND TRACKING TRANSACTIONS OF MOBILE DEVICES
In some examples, transaction data is received in relation to transactions performed by an application on a mobile device. The transactions include interactions between the mobile device and at least one server. The transaction data is aggregated for a time period according to different time increments. The transaction data for the time period is stored in a first table aggregated into time intervals according to a first time increment, and the transaction data for the time period is also stored in a second table aggregated into time intervals according to a second time increment. A user interface can be generated to include transaction information generated using the transaction data aggregated for the time period.
1 . A non-transitory machine readable medium comprising executable instructions, wherein the instructions, when executed by at least one processor, cause at least one computing device to at least:
receive, by a transaction server, transaction data related to transactions performed by an application on a mobile device and monitored using a transaction agent executed on the mobile device, the transactions comprising interactions between the mobile device and at least one server;
aggregate, by the transaction server, the transaction data for a time period according to different time increments, the transaction data for the time period being stored in a first table aggregated into time intervals according to a first time increment, and the transaction data for the time period being further stored in a second table aggregated into time intervals according to a second time increment; and
generate, by the transaction server, a user interface comprising transaction information generated using the transaction data aggregated for the time period.
2 . The non-transitory machine readable medium of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by the transaction server, a crash report related to a crash of the application.
3 . The non-transitory machine readable medium of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by the transaction server, a plurality of breadcrumbs, the breadcrumbs indicating data related to a plurality of events occurring in the application in association with at least one transaction.
4 . The non-transitory machine readable medium of claim 3 , wherein the plurality of events comprises events defined by calls made by the application to a network service.
5 . The non-transitory machine readable medium of claim 3 , wherein the plurality of events comprises events defined by calls made by the application.
6 . The non-transitory machine readable medium of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
transmit, by the transaction server, configuration data that configures the transaction agent to monitor transactions on the mobile device, wherein the configuration data specifies at least one of: a timeout value, a threshold value associated with a slow transaction, a transaction definition, and a transaction value.
7 . The non-transitory machine readable medium of claim 1 , wherein the transaction data comprises a value for the respective transaction.
8 . The non-transitory machine readable medium of claim 7 , wherein the value for the respective transaction is based on a user's interaction with the application.
9 . The non-transitory machine readable medium of claim 7 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
transmit, by the transaction server, configuration data to the mobile device, wherein the configuration data defines the value for the respective transaction.
10 . A method comprising:
receiving, by a transaction server, transaction data related to transactions performed by an application on a mobile device, the transactions comprising interactions between the mobile device and at least one server;
aggregating, by the transaction server, the transaction data for a time period according to different time increments, the transaction data for the time period being stored in a first table aggregated into time intervals according to a first time increment, and the transaction data for the time period being further stored in a second table aggregated into time intervals according to a second time increment; and
generating, by the transaction server, a user interface comprising transaction information generated using the transaction data aggregated for the time period.
11 . The method of claim 10 , wherein the user interface further comprises a list of a subset of the transactions, wherein a transaction is presented in association with a result of the transaction and a user revenue risk associated with failure of the transaction.
12 . The method of claim 10 , further comprising receiving a plurality of breadcrumbs, the breadcrumbs indicating data related to a plurality of events occurring in the application.
13 . The method of claim 12 , wherein the plurality of events comprises events defined by calls made by the application to a network service.
14 . The method of claim 12 , wherein the plurality of events comprises events defined by calls made by the application to a program.
15 . The method of claim 10 , further comprising transmitting configuration data to the mobile device, wherein the configuration data comprises events that define the respective transaction.
16 . The method of claim 10 , wherein the transaction data comprises a value for the respective transaction.
17 . The method of claim 16 , wherein the value for the respective transaction is based on a user's interaction with the application.
18 . The method of claim 16 , further comprising:
transmitting, by the transaction server, configuration data that configures a transaction agent to monitor transactions on the mobile device, wherein the configuration data specifies at least one of: a timeout value, a threshold value associated with a slow transaction, a transaction definition, and a transaction value.
19 . A system, comprising:
at least one processor; and
a data store comprising instructions that when executed by at least one processing unit cause the at least one processing unit to at least:
receive, by a transaction server, transaction data related to transactions performed by an application on a mobile device, the transactions comprising interactions between the mobile device and at least one server;
aggregate, by the transaction server, the transaction data for a time period according to different time increments, the transaction data for the time period being stored in a first table aggregated into time intervals according to a first time increment, and the transaction data for the time period being further stored in a second table aggregated into time intervals according to a second time increment; and
generate, by the transaction server, a user interface comprising transaction information generated using the transaction data aggregated for the time period.
20 . The system of claim 19 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
transmit, to the mobile device, configuration data that configures a transaction agent to monitor transactions on the mobile device, wherein the configuration data specifies at least one of: a timeout value, a threshold value associated with a slow transaction, a transaction definition, and a transaction value.