Data logging for API usage analytics
Systems, methods, and computer-readable storage mediums for performing specialized data logging on a client device are disclosed. Observability data pertaining to an API on a client device is captured. The observability includes, for each of one or more functions of the API, a number of times the function is used and a number of times each parameter of the function is used. The observability data pertaining to the API is communicated to a target based on a type of the observability data.
1. A system comprising:
one or more computer processors;
one or more computer memories;
a set of instructions stored in the one or more computer memories, the set of instructions configuring the one or more computer processors to perform operations, the operations comprising:
capturing observability data pertaining to an API on a client device, the observability data including, for each of one or more functions of the API, a number of times the function is used and a number of times each parameter of the function is used; and
communicating the observability data pertaining to the API to a target of a plurality of targets based on a type of the observability data, the type being one of a plurality of types, the target configured to provide reporting of one or more bugs pertaining to the API without manual intervention.
2. The system of claim 1 , wherein the type of the observability data is an error, a warning, or a debug message.
3. The system of claim 1 , wherein the plurality of targets includes one or more of a local IDE, a remote debugger, or a third-party application.
4. The system of claim 1 , wherein the observability data further pertains to metrics data associated with a usage of the API on the client device.
5. The system of claim 4 , wherein the metrics data is one or more of counters data or gauges data.
6. The system of claim 1 , wherein the observability data includes information pertaining to when the API was called during an event processing timeline.
7. The system of claim 1 , wherein the observability data further includes information pertaining to a destination for an event that is a subject of a usage of the API.
8. A method comprising:
capturing observability data pertaining to an API on a client device, the observability data including, for each of one or more functions of the API, a number of times the function is used and a number of times each parameter of the function is used; and
communicating the observability data pertaining to the API to a target of a plurality of targets based on a type of the observability data, the type being one of a plurality of types, the target configured to provide reporting of one or more bugs pertaining to the API without manual intervention.
9. The method of claim 8 , wherein the type of the observability data is an error, a warning, or a debug message.
10. The method of claim 8 , wherein the plurality of targets includes one or more of a local IDE, a remote debugger, or a third-party application.
11. The method of claim 8 , wherein the observability data further pertains to metrics data associated with a usage of the API on the client device.
12. The method of claim 11 , wherein the metrics data is one or more of counters data or gauges data.
13. The method of claim 8 , wherein the observability data includes information pertaining to when the API was called during an event processing timeline.
14. The method of claim 8 , wherein the observability data further includes information pertaining to a destination for an event that is a subject of a usage of the API.
15. A non-transitory computer-readable storage medium storing a set of instructions that, when executed by one or more computer processors, cause the one or more computer processors to perform operations for processing an event at a client device, the operations comprising:
capturing observability data pertaining to an API on a client device, the observability data including, for each of one or more functions of the API, a number of times the function is used and a number of times each parameter of the function is used; and
communicating the observability data pertaining to the API to a target of a plurality of targets based on a type of the observability data, the type being one of a plurality of types, the target configured to provide reporting of one or more bugs pertaining to the API without manual intervention.
16. The non-transitory computer-readable storage medium of claim 15 , wherein the type of the observability data is an error, a warning, or a debug message.
17. The non-transitory computer-readable storage medium of claim 15 , wherein the plurality of targets includes one or more of a local IDE, a remote debugger, or a third-party application.
18. The non-transitory computer-readable storage medium of claim 15 , wherein the observability data further pertains to metrics data associated with a usage of the API on the client device.
19. The non-transitory computer-readable storage medium of claim 18 , wherein the metrics data is one or more of counters data or gauges data.
20. The non-transitory computer-readable storage medium of claim 15 , wherein the observability data includes information pertaining to when the API was called during an event processing timeline.