Patent Application
20210173761
In order to improve the quality of software applications, software developers attempt to understand how the applications perform in the hands of users including customers and clients. While laboratory or development testing, such as debugging and logging, during application development is important in improving quality, laboratory testing alone is seldom sufficient for many modern applications. Modern software applications, especially mobile applications, are highly interactive, and a full range of user interactions are difficult to simulate in a laboratory or during development. Also, a number of environmental conditions effect user experience with applications. For example, network connectivity, GPS-signal quality, and device hardware all vary widely. Some platform APIs can even change behavior depending on the amount of power left in the device battery. These diverse environmental conditions are difficult to reproduce in a laboratory. Thus, many software developers endeavor to collect diagnostic and performance trace data from the field.
Platform support for tracing application performance in the field, however, is typically inadequate. Major platforms, including mobile platforms, provide application crash logs to developers, but developers report difficulty in identifying the causes of crashes from many logs. Further, such data, which may also include unresponsive events and exceptions, does not provide much assistance in detecting performance issues. Analytics frameworks are designed to collect usage analytics such as user demographics rather than performance data. This information typically does not effectively provide information about specific user activity within the application.
Instead, developers that seek meaningful information regarding application performance will include custom tracing code in the application, which is no easy task. For example, even a simple user request in an application triggers multiple asynchronous calls, with complex synchronization between threads, and identifying performance bottlenecks in such code requires correctly tracking causality across asynchronous boundaries. This challenging task is made even more difficult because tracing overhead is preferably kept to a minimum to avoid impact on application performance and also to limit the consumption of scarce resources such as battery and network bandwidth.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
A telemetry system, including implementation processes, is described. The telemetry system can communicate with one or more instrumented applications to collect data regarding events from the field and forward correlated and coalesced data to analytics applications for rich analysis. The telemetry system is configured to be operated with event definitions having one or more schema sections for declaring and populating data from an event, which is an instantiation of the event definition. The event definition can capture actions or interactions an event author (such as the application developer) wishes to track. The disclosure also includes aspects of a system, method, and computer readable medium for use with a telemetry system that can include automatically, i.e., explicitly, populating a base field of a schema in an event definition using a logging library of the telemetry system for an event of an instrumented application. A conditional field of the schema in the event definition may be automatically populated using the logging library in response to a selected condition for the event.
An event definition can include multiple schema sections configured to include data from an event. In the examples, an event definition includes a first section schema having fields that are automatically populated by the logging library without input from an event author such as an application developer. For example, the first section schema can include a schema having base fields for data that are general to all events such as system data. The first section schema can also include conditional fields, or extension fields, that may also be automatically populated by the logging library but in response to a particular condition. Examples of conditions can include environmental conditions, usage conditions, or both. In one example, an event in application engineered or ported for a particular operating system includes base fields for all events and conditional, or extension fields, related to that particular operating system. An event in the same application engineered or ported for another operating system can include the base fields for all events and conditional fields related to that other operating system.
Defining and using common definitions in the conditional fields of the first schema enables telemetry providers and consumers with consistent environmental or usage information across telemetry items. Structured descriptions of the conditional fields provide for strong correlation and flexible sets of extensions that can be used in different environments or in nested environments, such as applications executing in an operating system executing in a virtual machine. Common tooling and analytical applications can leverage data regardless of where the telemetry originates.
An event can also include a second section schema that includes fields selected by the event author. For example, a domain section schema includes fields that have broad applicability. In one example, an event author can select zero or more domain section schemas, but the event author does not control the name of the fields or the data types of the fields. Instead, the fields and types in the selected domain schemas are predefined, and the logging library populates the fields with data. The second section schema can further include a custom schema having fields and types defined by the event author that can be applicable to the event but not otherwise included in the system schema and the domain schema.
In one example, the telemetry system includes a high-volume, low latency event and telemetry platform. The telemetry system can be applied to drive one or more client and services ecosystems. Example systems or processes of the disclosure are able unify real-time, interactive, event driven workflows from customer to cloud or computer network and back to customer with comprehensive batch telemetry. A strong common schema, with strongly-typed fixed and flexible data fields to fully describe data enables rich analysis. The systems and processes described provide for application developers to quickly and easily create new instrumentation points with relatively low overhead. The strong common schema provides for data to be efficiently collected across multiple platforms.
The accompanying drawings are included to provide a further understanding of embodiments and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments and together with the description serve to explain principles of embodiments. Other embodiments and many of the intended advantages of embodiments will be readily appreciated, as they become better understood by reference to the following detailed description. The elements of the drawings are not necessarily to scale relative to each other. Like reference numerals designate corresponding similar parts.
In the following Detailed Description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims. It is to be understood that features of the various exemplary embodiments described herein may be combined with each other, unless specifically noted otherwise.
The exemplary computer system includes a computing device, such as computing device 100. In a basic hardware configuration, computing device 100 typically includes a processor system having one or more processing units, i.e., processors 102, and memory 104. By way of example, the processing units may include two or more processing cores on a chip or two or more processor chips. In some examples, the computing device can also have one or more additional processing or specialized processors (not shown), such as a graphics processor for general-purpose computing on graphics processor units, to perform processing functions offloaded from the processor 102. The memory 104 may be arranged in a hierarchy and may include one or more levels of cache. Depending on the configuration and type of computing device, memory 104 may be volatile (such as random access memory (RAM)), non-volatile (such as read only memory (ROM), flash memory, etc.), or some combination of the two. The computing device 100 can take one or more of several forms. Such forms include a tablet, a personal computer, a workstation, a server, a handheld device, a consumer electronic device (such as a video game console or a digital video recorder), or other, and can be a stand-alone device or configured as part of a computer network, computer cluster, cloud services infrastructure, or other.
Computing device 100 can also have additional features or functionality. For example, computing device 100 may also include additional storage. Such storage may be removable and/or non-removable and can include magnetic or optical disks, solid-state memory, or flash storage devices such as removable storage 108 and non-removable storage 110. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any suitable method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Memory 104, removable storage 108 and non-removable storage 110 are all examples of computer storage media. Computer storage media includes RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, universal serial bus (USB) flash drive, flash memory card, or other flash storage devices, or any other storage medium that can be used to store the desired information and that can be accessed by computing device 100. Accordingly, a propagating signal by itself does not qualify as storage media. Any such computer storage media may be part of computing device 100.
Computing device 100 often includes one or more input and/or output connections, such as USB connections, display ports, proprietary connections, and others to connect to various devices to provide inputs and outputs to the computing device. Input devices 112 may include devices such as keyboard, pointing device (e.g., mouse), pen, voice input device, touch input device, or other. Output devices 111 may include devices such as a display, speakers, printer, or the like.
Computing device 100 often includes one or more communication connections 114 that allow computing device 100 to communicate with other computers/applications 115. Example communication connections can include an Ethernet interface, a wireless interface, a bus interface, a storage area network interface, and a proprietary interface. The communication connections can be used to couple the computing device 100 to a computer network, which can be classified according to a wide variety of characteristics such as topology, connection method, and scale. A network is a collection of computing devices and possibly other devices interconnected by communications channels that facilitate communications and allows sharing of resources and information among interconnected devices. Examples of computer networks include a local area network, a wide area network, the Internet, or other network.
Instrumentation refers to augmenting an application with code that generates data that can be used to monitor or measure the performance and usage of the application, to diagnose errors, to write trace information, and the like. Programmers implement instrumentation in the form of code instructions that monitor specific components in a system. When an application contains instrumentation code, it can be managed using a management tool to review the performance of the application. Applications can be instrumented for logging and telemetry, which are typically oriented around the internal structure of the application during development and to collect data once the application is released to actual users.
Telemetry is automated remote measurement and data collection. For example, telemetry data can represent information not discoverable during application development such as which configurations customers prefer, how are customers using features in the application, what are the circumstances surrounding errors or crashes, and other information. Telemetry data can include anonymous software versioning information, resource usage, memory access, operating systems in use, and many other examples. Telemetry system 200 provides the tools to collect data and to condense the collected data into analytics, or human-decipherable reports. An instrumented application 206a-206c can include a telemetry layer.
In some examples, the user of the instrumented applications 206a-206c can determine which telemetry information to provide to a telemetry system 200. For example, the user can select to retain particular information locally, such as personal or sensitive information, and allow other information to be provided to the analytics software application. The user can choose to not upload such information as telemetry data, and the telemetry system 200 will not have access to personal or sensitive data.
Telemetry design leads to events, or actions the instrumentation will track, and applications are typically instrumented to track a series of distinct actions of or interactions with the application. Telemetry instrumentation is provided by event authors, such as application developers or component developers, and in some examples is imposed on event handlers. In one example, an application developer may wish to track several dozen events in an application. An event definition is a description of a specific event, and includes a list of fields set forth in a contract called a schema that can provide a system for declaring and populating structured data in the example. An event includes actual instantiation of a set of data described in the event definition, and this set of data is logged and transmitted to the telemetry system 200. An event is emitted in response to selected actions or interactions, and the data payload of the event, or event payload, describes attributes and semantics about the stimulus that triggered its creation, effects of the event, or both. An event author creates the event definition and the instrumentation code to populate and transmit the event to the telemetry system 200.
Telemetry system 200 includes, for example, a receiving/formatting system 220, logging library 222, processing system 224, real-time system 226, and event store 228. Telemetry data sent by client devices 204a-204c is received at telemetry system 200, which can then forward events to subscriber devices 208a-208b with low latency. Subscribers, using analytics application 210a-210b, can declare filters to receive relevant data. Telemetry system 200 can be configured to operate with one or more schemas of declaring and populating structured or unstructured data. In one example, receiving/formatting system 220 can be a web service that accepts events provided by client devices 204a-204c over the Internet. Logging library 222 uploads data to the receiving/formatting system 220. Receiving/forwarding system 220 can provide data to processing system 224 for rich analytics, batch processing, and reporting. Receiving/forwarding system 220 can also, or alternatively, provide data to real-time system 226 for real-time, or near real-time, indexing, querying, monitoring, and alerting. For example, real-time system 226 can include an operational deadline from event to system response that is greater than instantaneous. Event store 228 can provide reference information about events to the telemetry system 200.
Logging library 222 emits a client event format to receiving/formatting system 220 at 304. In one example, the different logging libraries dependent on platform can include a common file format to describe event definitions and a format for serialization. In one example, the format to describe event definitions can include a serialization framework for schematized data such as Bond available from Microsoft, Inc. The file format for serialization of payload can include a data-interchange format such as JavaScript Object Notation, or JSON. Receiving/formatting system 220 emits an ingested event format, at 306. Fields of the schema can continue to be populated with data at ingestion. For example, ingestion data can be provided to the first section schema to determine quality of the pipeline. Ingested events can be formatted in JSON and provided to real-time systems, at 308, or batch processing systems, at 310, for example, to allow analytical applications 210a-210b to query for data.
Field definitions in the example include a name and a type. Types can include basic data types (such as Boolean, various integer types, floating point numbers, strings), containers (lists, vectors, sets, maps), as well as complex types. In one example, types can be selected from those supported in the serialization framework. Not all complex types, however, supported in the serialization framework may be supported in the data-interchange format. In such cases, complex types in the serialization format can be converted to string type.
The example of an event represented in JSON includes:
First section schema 402 includes fields 422 defined by and automatically populated by the logging library 222 present on the local system where events are sent in the pipeline, such as in pipeline 300. In one example, first section schema 402 captures common correlating fields and can relate to the system of the instrumented software application, such as applications 206a-206c, and can represent system data. First section schema 402 can also capture information injected by event ingestion components in pipeline 300. In some examples, first section schema 402 can include fields 422 the logging library obtains from a caller in addition to values that are automatically filled. First section schema enables correlation and is available for automatic instrumentation using the logging library 222.
In one example, the first section schema 402 can include an event envelope semantic. The event envelope includes a data payload used to transmit event information between components of the pipeline 300. The payload can include the original event and a defined set of event sections. The event envelope semantic can include fields 422 such as schema version, name of the event, time (including date), sample rate, sequence to track order of uploaded events, instrumentation key, flags, device identifier that can be resilient to system builds or hardware replacements, operating system, operating system versions including branch and build information, application identifier, application version, and user identifier.
Fields 422 in first section schema 402 includes base fields 432 and can include conditional fields 442, or extension fields. Base fields 432 are typically general to all events from the instrumented application, and can include items such as event time and event name. The design of the schema 402, including the selection of the particular fields 422 to include, can be guided by various principles such as consistent identifiers across diverse applications and platforms such as operating systems as well as care taken to consider the effect on application overhead. In one example, all events use the same base fields 422.
Conditional fields 442, or extension fields, can be populated using the logging library similarly to base fields 432 but are automatically or explicitly populated in response to a selected condition for the event. For example, conditional fields could be populated in the ingest section, such as fields related to Internet Protocol of sender, as well as the logging library. The ingest section can be filled at ingestion time. Column for the ingest section can include time when event was received by the receiving/formatting system 220, the remote address seen by the receiving/formatting system 220 when the event was accepted, event authentication, and event quality.
Conditional fields 442 or extensions are used to describe data related to device, operating system, application, user, cloud environment, and other particular aspects of the application environment. For example, a set of conditional fields 442 may relate to a particular platform that is included in events occurring on that platform. Conditional fields 442 enable telemetry providers and consumers to work with consistent environmental information across telemetry items. An event may include zero or more automatically populated conditional fields 442 in addition to the base fields 432 automatically populated by the logging library.
Conditional fields 422 can be statically determined or dynamically determined. Statically determined conditional fields 422 are populated for all application events for a given environmental subset of an instrumented application. For instance, all examples of an instrumented application can include a set of base fields 432. Examples of the application engineered or ported for a particular platform, such as an operating system sold under the trade designation Azure available from Microsoft, can include the set of base fields 432 and also conditional fields 422 that relate to features of Azure environments. Examples of the application engineered or ported for an operating system sold under the trade designation Windows available from Microsoft can include the set of base fields and also conditional fields 442 that relate to features of Windows environments. Examples of statically determined conditional fields can include fields based on a particular device, platform, operating system, cloud environment, or telemetry client. In this respect, an instrumented application can include base fields and conditional fields that are determined at application design related to the environmental consideration of the application. A schema 402 can include zero, one, or more statically determined conditional fields.
Dynamically determined conditional fields are populated for all events of a given use subset for an instrumented application. For example, an instrumented mobile application can include a set of base fields 432 that are common for all events. Events that occur while the application is connected to a Wi-Fi communication technology can trigger a set of conditional fields related to Wi-Fi usage as well as the base fields that are automatically populated by the logging library. Events that occur while the application is connected to an LTE communication technology can trigger creation of a set of conditional fields related to LTE usage as well as base fields that are automatically populated by the logging library. Also, an application designed to be primarily used off line, such as a word processor, can include a set of base fields for all events as well as a set of conditional fields that are automatically populated for events that occur when the application is connected to a network. Other examples are contemplated.
Second section schema 404 includes optional domain schema 414, custom schema 416, or both. Second section schema 404 includes fields 424, 426 that are populated by code written by the event author rather than the logging library 222. In one example, second section schema 404 include domain schema 414 having predefined fields 424, such as by the telemetry system 200 or other centralized groups, and the event author does not control the name of the fields 424 or data types of the fields 424. Custom schema 416 is created by an event author and can be used for scenarios or aspects of events that are application-specific and for which no domain field 424 exists. Templates can be applied to second section schema 404 to support resuse of fields 424, 426 that are commonly defined across several events. Templates support defining a set of fields that can be consistently reused across multiple event definitions and, in some example, when multiple event definitions include different domain fields 424.
In one example, domain schema 414 is relevant to a particular scenario or aspects of events that are common across many different applications. For example, fields 424 in domain schema 414 can include logging an error, application start event, application end event, web services API (application program interface) call success, API call failure, and many other examples. A wide variety of applications and events can define events from domain schema fields 424 and thus include similar fields and data. Thus, a set of common reports and analytics can be built to consume all events from all applications on platforms that use the same domain schema 414. Event templates are analogous to abstract classes that allow, for example, a centralized group to share a set of fields that several related events include. In one example, domain fields 424 can be late-bound and chosen when the event is defined. Domain schemas 414 are generalized to enable broad applicability. For example, a domain schema MediaUsage can exist rather than more specific domain schemas such as play song, stop song, play video, stop video, or the like, which are more specific but use a schema per media player, for example.
Custom schema 416 is created and defined by the event author. In one example, the event author can determine the name and data type of the custom fields 426. The event author is also responsible for populating the custom fields 426 when an event is instantiated.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that a variety of alternate and/or equivalent implementations may be substituted for the specific embodiments shown and described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the specific embodiments discussed herein. Therefore, it is intended that this invention be limited only by the claims and the equivalents thereof
This patent application is a continuation of Ser. No. 14/885,969 filed Oct. 16, 2015, entitled “TELEMETRY SYSTEM EXTENSION,” now allowed, which is incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14885969 | Oct 2015 | US |
| Child | 17183229 | US |
