Microsoft Technology Licensing, LLC

Neil Evan Lydick

Hua Wang

Michael F Speer

Jagadeesh Kalki

Christopher Andrew Boyd

Vijaykumar K Aski

Ling Yan

Ciaran Murphy

Adrian Kyle Wirpel

Artur Perez

A remote monitoring and management (RMM) system is configured to receive a stream of events generated in response to interactions of users from multiple tenants with one or more applications and store the events in a database. A plurality of different insight types is defined for one or more event types for the events. Insights of the different insight types are generated based on the events in the database, the event types of the events, and numbers of events of the event types. The insights are ranked using an artificial intelligence (AI) model trained to generate a predicted success score for each of the insights. A predetermined number of top insights are selected based on the ranking of the insights and aggregated into a feed. The feed is to at least one computing device associated with the RMM system.

Multi-tenant feed and insights platform

A method may include receiving, at a server device, a request to extract configuration settings of a source tenant organization from a data store; in response to the request at the server device, recursively accessing the configuration settings of the source tenant organization; generating, at the server device, a configuration tree data structure based on the accessed configuration settings, the configuration tree data structure organized as a plurality of key-value pairs; selecting, at the server device, a target tenant organization; based on the configuration tree data structure, generating, at the server device, a deployment order including chained API calls directed towards the target tenant organization; executing, at the server device, the chained API calls.

Tenant configuration state extraction and variance detection

The disclosed techniques assist in diagnosing performance problems of a software application. A profiling module dynamically instruments the application at runtime by intercepting a request to compile one of the application's functions and augmenting the function with performance measuring code. This way, instrumentation is installed without recompiling the application. The execution time of a synchronous function is tracked by adding a local variable that stores function entry time, and by inserting code at each function exit point that computes the elapsed time. The execution time of an async function that executes across multiple threads is measured by repurposing a state machine value to also store the initial function entry time. Instrumented functions that are executed at a rate exceeding a threshold are un-instrumented to avoid self-inflicted performance problems. Function invocations associated with a particular activity, such as responding to a particular web request, may be correlated.

Automatic performance telemetry

Methods, systems, and computer storage media for providing a multi-tenant system that executes graph language requests using graph operations of a graph language. A graph language request&#x2014;that configures tenant data for tenants in a multi-tenant system&#x2014;is executed using a graph operations engine. The graph operations engine receives and parses a graph language request that includes a list of tenants and a definition of data operations. The set of data operations of the definition are executed on a tree of data operation nodes comprising a plurality of leaf nodes and a root node. Executing the data operations is based on graph language actions (e.g., composition, transformation, and aggregation) that support asynchronously returning results data associated with configuring the Tenant data. Executing the data operations of the definition causes generation of results data (e.g., root node results or leaf node results) configuration of the tenant data in the multi-tenant system.

Graph operations engine for tenant management in a multi-tenant system

Techniques for implementing a low-latency query processor accommodating an arbitrary number of data rows with no column indexing. In an aspect, data is stored across a plurality of component databases, with no requirement to strictly allocate data to partitions based on row keys. A histogram table is provided to map object relationships identified in a user query to the component databases where relevant data is stored. A server processing the user query communicates with component databases via an intermediary module. The intermediary module may include intermediary nodes dynamically assigned to connect to the component databases to retrieve and process the queried data.

Growing community of inventors

Bothell, WA, United States of America

Neil Evan Lydick