SYSTEM AND METHOD FOR RAPID AND ASYNCHRONOUS MULTITENANT TELEMETRY COLLECTION AND STORAGE

• US 20180322437A1
• Filed: 07/20/2017
• Published: 11/08/2018
• Est. Priority Date: 05/08/2017
• Status: Active Grant

• Current Assignee: DataPipe, Inc. (Apollo Global Management, Inc.)
• Original Assignee: DataPipe, Inc. (Apollo Global Management, Inc.)
• Inventors: MCCLORY, Thomas Patrick, Damania, Jatil Chandrakant, Vidmar, Scott Matthew, Lonstein, Ross Edward
• Granted Patent: US 10,514,967 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 2009/45583 Memory management, e.g. access or allocation
• CPC Class Codes: G06F 2009/45587 Isolation or security of virtual machine instances
• CPC Class Codes: G06F 2009/45591 Monitoring or debugging support
• CPC Class Codes: G06F 2209/501 Performance criteria
• CPC Class Codes: G06F 2209/541 Client-server
• CPC Class Codes: G06F 2209/548 Queue
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/41 Compilation
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 8/77 Software metrics
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5027 the resource being a machine, e.g. CPUs, Servers, Terminals
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 10/06398 Performance of employee with respect to a job function
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 41/5083 : wherein the managed service relates to web hosting
• CPC Class Codes: H04L 63/0236 : Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 63/0281 : Proxies
• CPC Class Codes: H04L 63/1433 : Vulnerability analysis
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Disclosed herein are system, apparatus, article of manufacture, method, and/or computer program product embodiments for rapid, asynchronous multitenant telemetry collection and storage of multiple tenants. An embodiment operates by receiving a telemetry storage request from a telemetry application configured to collect telemetry information from a deployed application and queuing the received telemetry storage request into a gatekeeper command queue. The embodiment further operates by retrieving the received telemetry storage request from the gatekeeper command queue and publishing a decorated telemetry collection event to a global event stream by transmitting the decorated telemetry collection event to an event stream component configured to manage the global event stream.

Claims

1. A system, comprising:

at least one processor; and

a memory operatively coupled to the at least one processor, the at least one processor configured to;

receive, by a gatekeeper command component, a telemetry storage request from a telemetry application configured to collect telemetry information from a deployed application, the telemetry storage request comprising telemetry information and associated telemetry tag information;

queue, by the gatekeeper command component, the received telemetry storage request into a gatekeeper command queue, the gatekeeper command queue configured to store the telemetry storage request,

retrieve, by a gatekeeper worker component, the received telemetry storage request from the gatekeeper command queue, and

publish, by the gatekeeper worker component, a decorated telemetry collection event to a global event stream by transmitting the decorated telemetry collection event to an event stream component configured to manage the global event stream.

2. The system of claim 1, wherein the at least one processor is further configured to:

transmit, by the gatekeeper command component, a telemetry storage success response to the telemetry application indicating that the telemetry storage request has been properly received and queued,

cache, by the gatekeeper worker component, the telemetry information and the associated telemetry tag information into a gatekeeper cache data store,

generate, by the gatekeeper worker component, the decorated telemetry collection event based on the telemetry information and the associated telemetry tag information, and

remove, by the gatekeeper worker component, the queued telemetry storage request from the gatekeeper command queue after the decorated telemetry collection event is published by the event stream component.

3. The system of claim 2, wherein the at least one processor is further configured to:

transmit a telemetry storage failure response to the telemetry application, the telemetry storage failure response indicating that the telemetry storage request has not been queued, wherein the telemetry application is configured to cache the telemetry storage request for re-transmission at a different time period, in response to receiving the telemetry storage failure response.

4. The system of claim 2, wherein the telemetry application comprises:

a logging component configured to collect logs information generated by the deployed application that is associated with an application developer, and

a metrics component configured to collect metrics information generated by the deployed application that is associated with the application developer.

5. The system of claim 4, wherein the at least one processor is further configured to:

retrieve, by a telemetry collection and storage component, the decorated telemetry collection event from the global event stream,

store, by the telemetry collection and storage component, the logs information and associated telemetry tag information to a logs data store, wherein the logs data store is a multitenant searchable data store, and

store, by the telemetry collection and storage component, the metrics information and associated telemetry tag information to a metrics data store configured to store time series information.

6. The system of claim 2, wherein:

the gatekeeper cache data store is configured to store the telemetry information and the associated telemetry tag information received from the telemetry application with high availability and redundancy; and

the at least one processor is configured to store, by a long-term telemetry storage component, the telemetry information and associated telemetry tag information of the decorated telemetry collection event to a long-term telemetry data store, after the decorated telemetry collection event has persisted in the global event stream for a specific time period.

7. The system of claim 2, wherein:

the telemetry application is associated with at least one tenant of at least one deployed application of at least one cluster node in a cluster,

the decorated telemetry collection event includes the telemetry information, the associated telemetry tag information, and decorated telemetry tag information generated based on the telemetry information and the associated telemetry tag information, and

the generated decorated telemetry tag information includes a tenant identifier, wherein the tenant identifier identifies the at least one tenant associated with the at least one deployed application.

8. A computer-implemented method, comprising:

receiving a telemetry storage request from a telemetry application configured to collect telemetry information from a deployed application, the telemetry storage request comprising telemetry information and associated telemetry tag information;

queuing the received telemetry storage request into a gatekeeper command queue, wherein the gatekeeper command queue is configured to store the received telemetry storage request;

retrieving the received telemetry storage request from the gatekeeper command queue; and

publishing a decorated telemetry collection event to a global event stream by transmitting the decorated telemetry collection event to an event stream component configured to manage the global event stream.

9. The method of claim 8, further comprising:

transmitting a telemetry storage success response to the telemetry application indicating that the telemetry storage request has been properly received and queued;

caching the telemetry information and the associated telemetry tag information into a gatekeeper cache data store;

generating the decorated telemetry collection event based on the telemetry information and the associated telemetry tag information; and

removing the queued telemetry storage request from the gatekeeper command queue after the decorated telemetry collection event is published by the event stream component.

10. The method of claim 8, further comprising:

transmitting a telemetry storage failure response to the telemetry application, the telemetry storage failure response indicating that the telemetry storage request has not been queued, wherein the telemetry application caches the telemetry storage request for re-transmission at a different time period, in response to receiving the telemetry storage failure response.

11. The method of claim 9, wherein the telemetry application comprises:

a logging component configured to collect logs information generated by the deployed application that is associated with an application developer, and

a metrics component configured to collect metrics information generated by the deployed application that is associated with the application developer.

12. The method of claim 11, wherein:

the decorated telemetry collection event is retrieved by a telemetry collection and storage component from the global event stream,

the logs information and the associated telemetry tag information are stored by the telemetry collection and storage component in a logs data store configured as a multitenant searchable data store, and

the metrics information and associated telemetry tag information are stored by the telemetry collection and storage component in a metrics data store configured to store time series information.

13. The method of claim 11, wherein:

the gatekeeper cache data store is configured to store the telemetry information and associated telemetry tag information received from the telemetry application with high availability and redundancy, and

the telemetry information and associated telemetry tag information of the decorated telemetry collection event are stored in a long-term telemetry data store by a long-term telemetry storage component, after the decorated telemetry collection event has persisted in the global event stream for a specific time period.

14. The method of claim 9, wherein:

the telemetry application is associated with at least one tenant of at least one deployed application of at least one cluster node in a cluster,

the decorated telemetry collection event includes the telemetry information, the associated telemetry tag information, and decorated telemetry tag information generated based on the telemetry information and the associated telemetry tag information, and

the generated decorated telemetry tag information includes a tenant identifier, wherein the tenant identifier identifies the at least one tenant associated with the at least one deployed application.

15. A tangible computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations comprising:

receiving a telemetry storage request from a telemetry application configured to collect telemetry information from a deployed application, the telemetry storage request comprising telemetry information and associated telemetry tag information;

queuing the received telemetry storage request into a gatekeeper command queue, wherein the gatekeeper command queue is configured to store the received telemetry storage request;

retrieving the received telemetry storage request from the gatekeeper command queue; and

publishing a decorated telemetry collection event to a global event stream by transmitting the decorated telemetry collection event to an event stream component configured to manage the global event stream.

16. The computer-readable device of claim 15, the operations further comprising:

transmitting a telemetry storage success response to the telemetry application indicating that the telemetry storage request has been properly received and queued;

caching the telemetry information and the associated telemetry tag information into a gatekeeper cache data store;

generating the decorated telemetry collection event based on the telemetry information and the associated telemetry tag information; and

removing the queued telemetry storage request from the gatekeeper command queue after the decorated telemetry collection event is published by the event stream component.

17. The computer-readable device of claim 15, the operations further comprising:

transmitting a telemetry storage failure response to the telemetry application, the telemetry storage failure response indicating that the telemetry storage request has not been queued, wherein the telemetry application caches the telemetry storage request for re-transmission at a different time period, in response to receiving the telemetry storage failure response.

18. The computer-readable device of claim 15, wherein:

the decorated telemetry collection event is retrieved by a telemetry collection and storage component from the global event stream,

the telemetry information includes logs information and metrics information,

the logs information and the associated telemetry tag information are stored by the telemetry collection and storage component in a logs data store configured as a multitenant searchable data store, and

the metrics information and associated telemetry tag information are stored by the telemetry collection and storage component in a metrics data store configured to store time series information.

19. The computer-readable device of claim 16, wherein:

the gatekeeper cache data store is configured to store the telemetry information and the associated telemetry tag information received from the telemetry application with high availability and redundancy, and

the telemetry information and associated telemetry tag information of the decorated telemetry collection event are stored in a long-term telemetry data store by a long-term telemetry storage component, after the decorated telemetry collection event has persisted in the global event stream for a specific time period.

20. The computer-readable device of claim 16, wherein:

the telemetry application is associated with at least one tenant of at least one deployed application of at least one cluster node in a cluster,

the decorated telemetry collection event includes telemetry information, the associated telemetry tag information, and decorated telemetry tag information generated based on the telemetry information and the associated telemetry tag information, and

the generated decorated telemetry tag information includes a tenant identifier, the tenant identifier identifies the at least one tenant associated with the at least one deployed application.