Microsoft Technology Licensing, LLC

Mandyam Kishore

Amol Kulkarni

Dharma Kiritkumar Shukla

Girish Mittur Venkataramanappa

Yann Christensen

Chandra Prasad

Andreas Ulbrich

Erik B Christensen

Aditya G Bhandarkar

Igor Sedukhin

Haoran Andy Wu

Sumit Mohanty

Mariusz Gerard Borsa

Vinod Shanbhag

Leo S Vannelli, Iii

Anubhav Dhoot

Aarthi Rajmohan Saravanakumar

Systems and methods according to various embodiments disclose a worker process manager adapted to spawn one or more worker processes on a server and to load an application on each of the worker processes. The worker process manager is adapted to isolate the one or more worker processes from each other and to control resource usage by the worker processes. A resource manager is adapted to detect applications that overuse system resources. The worker process manager is adapted to isolate worker processes and to control resource usage using one or more of the following techniques: least-privilege execution, messaging isolation, credentials isolation, data isolation, network isolation, fair share resource usage, and managed runtime security. Heuristic algorithms are used to detect applications that frequently overuse system resources that are unchargeable and that cause system unresponsiveness.

Sandboxing for multi-tenancy

A container service is capable of hosting large numbers of middleware components for multiple tenants. A central container manager controls a plurality of compute nodes. The central container manager receives middleware components from external devices or services and assigns the components to containers on one or more designated compute nodes. Each compute node has a container management agent and one or more containers. The container management agents activate and manage the appropriate number of containers to run the assigned middleware components. The container management agent assigns each container on its compute node a limited set of privileges to control access to shared resources. The central container manager and each node's container management agent monitor container load levels and dynamically adjust the placement of the middleware components to maintain balanced operation. The compute nodes are grouped into clusters based upon the type of middleware components hosted on each compute node.

Multi-tenant, high-density container service for hosting stateful and stateless middleware components

Enabling and processing events. To enable events, an application model correlated to an application is declaratively defined. The application model describes operations of the application. One or more event models correlated to the application model are declaratively defined. The event models describe application execution locations where events are desired to be emitted in the execution of the application. Based on the correlation of the event models to the application models, the applications are instrumented with instrumentation code to cause the application to emit events at the execution locations. To process events an application model is defined. The application model includes one or more observation models. The observation models include a correlation of events to the observation model by defining instrumentation models in the application model. An event is received. The event is applied to the observation model based on the correlation. The event is processed according to the observation model.

Model-driven, repository-based application monitoring system

Growing community of inventors

Redmond, WA, United States of America

Mandyam Kishore