Abstract: A method of operating a telemetry system includes automatically 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, and automatically populating a conditional field of the schema in the event definition using the logging library in response to a selected condition for the event.

Abstract: A method of operating a telemetry system includes automatically populating a first set of fields in a schema of an event definition using a logging library of the telemetry system, and receiving the set of fields via a request message in an application protocol.

Abstract: A method of operating a telemetry system includes automatically populating a first set of fields in a schema of an event definition using a logging library of the telemetry system, and populating a second set of fields in the schema selected by an event author.

Abstract: A method of operating a telemetry system includes automatically 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, and automatically populating a conditional field of the schema in the event definition using the logging library in response to a selected condition for the event.

Abstract: A method of operating a telemetry system includes automatically 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, and automatically populating a conditional field of the schema in the event definition using the logging library in response to a selected condition for the event.

Abstract: In one embodiment, a metric collection system may collect application metrics across multiple data centers in specific time intervals. A local collection point 108 may establish an absolute reference time for a local data center 102. The local collection point 108 may determine a source reporting interval for an application 106 based on the absolute reference time. The local collection point 108 may receive a source metric report 300 for the application 106 based on the source reporting interval.

Abstract: Various embodiments provide session-based filtering to filter messages in a cooperative manner between a client and a service provider. In at least some embodiments, a service provider can establish a messaging session with a client and deliver messages to the client. The client can implement various client-side techniques to filter some of the messages based on various client designated criteria. The service provider can obtain feedback from the client indicative of one or more of the delivered messages that have been filtered. The service provider can dynamically create a session-based list based on the feedback and use the list during the session to block messages on the server-side according to the client designated criteria. When the session concludes, the session-based list can be discarded. In this manner, message filtering can occur without persistent storage of state data for the filtering at the service provider.

Abstract: A notification service receives messages including various data from application services, and provides notifications including that data to the appropriate computing devices. Each computing device includes a notification system that receives notifications from the notification service and provides those notifications to the appropriate applications on the computing device. If an application is not allowed to run on a computing device, the notification system on the computing device provides an indication to the notification service to block notifications for the application on the computing device. The notification service ceases providing notifications to a computing device targeting applications for which notifications are blocked on the computing device until an indication is received from the computing device to unblock notifications for the application.

Abstract: A method of operating a telemetry system includes receiving an automatically populated set of fields in a schema of an event definition, and providing a response message in an application protocol. The set of fields are automatically populated using a logging library of the telemetry system.

Abstract: A method of operating a telemetry system includes automatically populating a first set of fields in a schema of an event definition using a logging library of the telemetry system, and populating a second set of fields in the schema selected by an event author.

Abstract: A method of operating a telemetry system includes automatically 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, and automatically populating a conditional field of the schema in the event definition using the logging library in response to a selected condition for the event.

Abstract: A method of operating a telemetry system includes automatically populating a first set of fields in a schema of an event definition using a logging library of the telemetry system, and receiving the set of fields via a request message in an application protocol.

Abstract: A notification service receives messages including various data from application services, and provides notifications including that data to the appropriate computing devices. Each computing device includes a notification system that receives notifications from the notification service and provides those notifications to the appropriate applications on the computing device. If an application is not allowed to run on a computing device, the notification system on the computing device provides an indication to the notification service to block notifications for the application on the computing device. The notification service ceases providing notifications to a computing device targeting applications for which notifications are blocked on the computing device until an indication is received from the computing device to unblock notifications for the application.

Abstract: A notification service receives messages including various data from application services, and provides notifications including that data to the appropriate computing devices. Each computing device includes a notification system that receives notifications from the notification service and provides those notifications to the appropriate applications on the computing device. If an application is not allowed to run on a computing device, the notification system on the computing device provides an indication to the notification service to block notifications for the application on the computing device. The notification service ceases providing notifications to a computing device targeting applications for which notifications are blocked on the computing device until an indication is received from the computing device to unblock notifications for the application.

Abstract: Various embodiments provide session-based filtering to filter messages in a cooperative manner between a client and a service provider. In at least some embodiments, a service provider can establish a messaging session with a client and deliver messages to the client. The client can implement various client-side techniques to filter some of the messages based on various client designated criteria. The service provider can obtain feedback from the client indicative of one or more of the delivered messages that have been filtered. The service provider can dynamically create a session-based list based on the feedback and use the list during the session to block messages on the server-side according to the client designated criteria. When the session concludes, the session-based list can be discarded. In this manner, message filtering can occur without persistent storage of state data for the filtering at the service provider.

Abstract: Stateless application notifications are described that enable third parties to provide messages to client applications. A communication channel can be established between a notification service and an application. Upon request, the notification service can generate obfuscated routing data for the channel, which can be in the form of a channel handle or token. The routing data can be encrypted and digitally signed to obscure the content and format of the routing data from third parties. An application service possessing the obfuscated routing data can package a notification with the data and send the package to the notification service for delivery. The application service does so without knowing the channel particulars encoded by the obfuscated routing data. The notification service that produces the obfuscated routing data can decrypt and interpret the data, and deliver the notification on the channel to an appropriate endpoint application on behalf of the application service.

Abstract: Various embodiments provide session-based filtering to filter messages in a cooperative manner between a client and a service provider. In at least some embodiments, a service provider can establish a messaging session with a client and deliver messages to the client. The client can implement various client-side techniques to filter some of the messages based on various client designated criteria. The service provider can obtain feedback from the client indicative of one or more of the delivered messages that have been filtered. The service provider can dynamically create a session-based list based on the feedback and use the list during the session to block messages on the server-side according to the client designated criteria. When the session concludes, the session-based list can be discarded. In this manner, message filtering can occur without persistent storage of state data for the filtering at the service provider.

Abstract: Various embodiments enable automatic cooperative logging of information associated with a connection between at least two computing devices. In some cases, a first computing device can automatically trigger logging on a second computing device upon detection of at least one scenario. Alternately or additionally, the second computing device can respond to the first computing device with additional and/or supplemental logging requests.

Abstract: Various embodiments enable automatic cooperative logging of information associated with a connection between at least two computing devices. In some cases, a first computing device can automatically trigger logging on a second computing device upon detection of at least one scenario. Alternately or additionally, the second computing device can respond to the first computing device with additional and/or supplemental logging requests.

Abstract: A content item hosted by a content item source (such as a weblog post of a weblog) may receive updates (e.g., comments submitted by users), and may be discussed among users in a chat group of a chat service. The content item source and the chat service may coordinate to notify users of updates to the content item, and to share content regarding the content item. When a user requests to subscribe to updates of the content item, the content item source may invite the user to join a chat group of the chat service created for discussion of the content item. Additionally, updates to the content item received by the content item source may be automatically posted as messages in the chat group, and messages posted in the chat group regarding the content item may be automatically posted as updates to the content item at the content item source.