Abstract: A method of rendering a service graph illustrating dependencies between a frontend and a backend of an application comprises generating a plurality of frontend traces from a plurality of frontend spans and generating a plurality of backend traces from a plurality of backend spans ingested from the application. The method also comprises aggregating frontend metrics data using the plurality of frontend traces and backend metrics data using the plurality of backend traces. The method further comprises determining connection information between one or more frontend traces of the plurality of frontend traces and corresponding backend traces of the plurality of backend traces. The method also comprises rendering the service graph using the connection information and the aggregated frontend and backend metrics data.

Abstract: A method of rendering a service graph responsive to a query comprises generating a plurality of frontend traces and a plurality of backend traces associated with an application or website. The method also comprises determining connection information between one or more frontend traces of the plurality of frontend traces and corresponding backend traces of the plurality of backend traces. Further, the method comprises consolidating the one or more frontend traces with the corresponding backend traces to form one or more end-to-end traces using the connection information. Responsive to the query, the method comprises retrieving a set of exemplary end-to-end traces from the one or more end-to-end traces and rendering a service graph in accordance with constraints applied in the query using the set of exemplary end-to-end traces and the connection information.

Abstract: A method of rendering a service graph responsive to a query comprises generating a plurality of frontend traces and a plurality of backend traces associated with an application or website. The method also comprises determining connection information between one or more frontend traces of the plurality of frontend traces and corresponding backend traces of the plurality of backend traces. Further, the method comprises consolidating the one or more frontend traces with the corresponding backend traces to form one or more end-to-end traces using the connection information. Responsive to the query, the method comprises retrieving a set of exemplary end-to-end traces from the one or more end-to-end traces and rendering a service graph in accordance with constraints applied in the query using the set of exemplary end-to-end traces and the connection information.

Abstract: Resource pool depletion information, including the estimated time until the resource pool is depleted, is derived from resource pool data. Data regarding the size of a resource pool is collected over a period of time. The data may include the resource pool size and other information. One or more functions are then generated to fit one or more sets of data within the collected resource pool data. The best fitting function is selected from the generated functions and used to determine the time at which the particular resource pool will become depleted. Values for the selected function can be generated at future points in time to determine the depletion point of the resource pool. The time information as well as depletion confidence values are provided to a user or otherwise processed.

Abstract: Network performance is monitored using timing information retrieved from a client device, server in communication with the client, or both. Client side timing information is retrieved using performance monitoring code provided by the server. The code may be provided to the client as part of a content response. Once content in the provided content response is loaded, the code sends the timing information to the server. The server may then process the timing information to calculate response time and other time information metrics.

Abstract: Resource pool depletion information, including the estimated time until the resource pool is depleted, is derived from resource pool data. Data regarding the size of a resource pool is collected over a period of time. The data may include the resource pool size and other information. One or more functions are then generated to fit one or more sets of data within the collected resource pool data. The best fitting function is selected from the generated functions and used to determine the time at which the particular resource pool will become depleted. Values for the selected function can be generated at future points in time to determine the depletion point of the resource pool. The time information as well as depletion confidence values are provided to a user or otherwise processed.

Abstract: A system receiving time series data will store the data in a first format suited for quick writing. That data will subsequently be converted from the first format to a second format better suited than the first format for compact storage and queries. Over time, the data in the second format can be aggregated and/or down sampled. In one embodiment, the first format includes a set of blocks of information, with each block of information storing data for a set of metrics during a time period. The second format includes a header, a set of blocks of data and a footer. Each bock of data in the second format stores information for a metric over multiple time periods. The footer includes pointers to each block of data.

Abstract: A system is disclosed for accessing information about an object, where such information is available at the time of creation of the object but not necessarily available at all times later. In one embodiment, existing object code is modified to add the ability to access the information. The modified code is then executed.

Abstract: One or more new methods are added to existing object code. The existing object code includes a first method that is capable of producing a result. New code is added to the first method. The new code provides the result to one or more of the new methods. After the modification, the result (e.g. a return value or exception) from the first method can be accessed and used by other threads, processes, systems, entities etc. that were not originally programmed to access the result or exception.