Amazon Technologies, Inc.

John Walter Heitmann

Chiranjeeb Buragohain

Sumit Lohia

Blake Meike

Christopher Reddy Kommareddy

Liang Chen

Alex Maclinovsky

Geoffrey Scott Pare

Zachary S Musgrave

John David Dunagan

Derek Solomon Pai

Viraj Vijay Sanghvi

Michael R Foster

Geoffry Scott Pare

Caitlyn Rose Shim

Luan Khai Nguyen

Brian Jacob Feinstein

Cory Barrett Kendall

Brian J Smith

Geoffrey Eric Endresen

Brian Scott Cripe

Techniques are described for managing program execution capacity, such as for a group of computing nodes that are provided for executing one or more programs for a user. In some situations, dynamic program execution capacity modifications for a computing node group that is in use may be performed periodically or otherwise in a recurrent manner, such as to aggregate multiple modifications that are requested or otherwise determined to be made during a period of time, and with the aggregation of multiple determined modifications being able to be performed in various manners. Modifications may be requested or otherwise determined in various manners, including based on dynamic instructions specified by the user, and on satisfaction of triggers that are previously defined by the user. In some situations, the techniques are used in conjunction with a fee-based program execution service that executes multiple programs on behalf of multiple users of the service.

Dynamically modifying program execution capacity

Technologies are disclosed herein for asynchronous distributed editing of a structured document, such as a trouble ticket. A document management service receives edits to the structured document. The edits to the structured document include data to be stored in fields of the structured document and information identifying the fields into which the data in the edits is to be stored. The edits are synchronized to other instances of the document management service. Edits to the structured document made at the other instances of the document management service are also received and stored. When a request is received for the structured document, the edits to the document made at the various instances of the document management service are sorted based upon the order in which they were created. The edits are applied in the sorted order to generate the structured document.

Distributed asynchronous document editing

Techniques are described for managing program execution capacity, such as for a group of computing nodes that are provided for executing one or more programs for a user. In some situations, dynamic program execution capacity modifications for a computing node group that is in use may be performed periodically or otherwise in a recurrent manner, such as to aggregate multiple modifications that are requested or otherwise determined to be made during a period of time. In addition, various operations may be performed to attribute causality information or other responsibility for particular program execution capacity modifications that are performed, including by attributing a single event as causing one capacity modification, and a combination of multiple events as possible causes for another capacity modification. The techniques may in some situations be used in conjunction with a fee-based program execution service that executes multiple programs on behalf of multiple users of the service.

Attributing causality to program execution capacity modifications

Monitoring data can be sent, received, stored, and accessed with zero setup. Customers can send monitoring data to be stored without the customers having to perform any setup ahead-of-time, such as arbitrary lists of key-value pairs. Customers can perform zero setup pivot queries using stored monitoring data. For example, users can perform pivot queries using any available stored information, such as available metric types and dimensions, without any setup needed ahead-of-time.

Flexible pivot querying of monitoring data with zero setup

Techniques are described for updating resources provided to a user device, using subscription based polling. A user device may send initial requests for resource to a server, each initial request including a resource identifier and a subscriber identifier. In some cases, the subscriber identifier may uniquely identify the communication session. The server maintains subscription information correlated with the subscriber identifier, the subscription information listing which resources the user device has requested and which versions of the resources are currently available on the user device. Updates to the subscribed resources may then be provided to the user device in response to a request for updates that specifies the session identifier but that may not specify the particular subscribed resources.

Subscription based polling for resource updates

Monitoring data can be received and managed in a multi-tenant environment. Monitoring data can be received for multiple tenants. The received monitoring data can be sorted. Sorting can be performed based on various criteria, such as by tenant. The sorted monitoring data can be written to data files. Each data file can store monitoring data for a plurality of tenants. Receiving, sorting, and writing monitoring data can be performed within a multi-tenant monitoring system.

Multitenant monitoring system storing monitoring data supporting flexible pivot querying

One or more event records associated with incidents that may occur in a network may be created and stored in an event sequence with other related event records. Whether the event records are related may be determined based at least in part on a dependency between network elements associated with the incidents. The one or more event records may be executed by event handlers to create additional event records, which may also be stored in an event sequence with related event records. A user may request event sequences for display at a user device. Event sequences may be processed to provide at least a portion of the sequences based at least in part on user-specific information. A user may interact with and/or respond to event records in the network. Such interactions or responses may also be stored as event records in an event sequence.

Systems and methods for tracking and managing event records associated with network incidents

Pivot queries can be performed using stored monitoring data. Pivot queries can be received. Monitoring data can be read from data files. Each data file can store monitoring data for a plurality of tenants. The read monitoring data can be aggregated based on metric types across various dimensions, according to the pivot queries. Results can be presented in various formats, such as charts and graphs. Reading, aggregating, and presenting results can be performed within a multi-tenant monitoring system.

Growing community of inventors

Seattle, WA, United States of America

John Walter Heitmann