# US 2019/0356566 A1 · Extensible, secure and efficient monitoring & diagnostic pipeline for hybrid cloud architecture

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0356566 A1
- Document ID: US20190356566A1
- Status: Published application
- Kind: A1
- Application number: 15/983,280
- Filed: 2018-05-18
- Published: 2019-11-21
- Earliest claimed: 2018-05-18
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Bhatt Rutwick Bharatkumar; Asudani Mohit
- Web page: https://patentgrep.com/patent/US20190356566A1

## CPC

- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- H04L 43/067: using time frame reporting
- G06F 11/3075: {the data filtering being achieved in order to maintain consistency among the monitored data, e.g. ensuring that the monitored data belong to the same timeframe, to the same system or component}
- G06F 16/178: Techniques for file synchronisation in file systems
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 41/0631: using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
- H04L 41/069: using logs of notifications; Post-processing of notifications
- H04L 67/1095: Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems are provided for facilitating the disclosed methods for performing event storage and diagnostic processing within a hybrid cloud environment. Event records are gathered and batched at an on-premises server. The event records are also appended with correlation vector data that enables the event records to be correlated with other events. The batch of event record batches are signed with a security key associated with a cloud storage container and the on-premises server is restricted to writing the batch of event records to the container. In some instances, the size of the batch is based on a duration of time for collecting records, which can be adjusted to accommodate for missing data.

## Claims

### Claim 1

An on-premises computing system that is operating in a hybrid cloud environment, which is connected to a cloud storage and to a cloud file sync service, comprising:
one or more processors; and
one or more computer-readable media having stored thereon instructions that are executable by the one or more processors to configure the computer system to implement a method for performing event storage and diagnostic processing in the hybrid cloud environment, wherein the method includes the on-premises computing system performing at least the following:
identifying a plurality of different monitoring events of one or more machines in the on-premises computing system during a predetermined batch period of time;
generating a plurality of event records corresponding to the plurality of different monitoring events detected during the predetermined batch period of time, wherein generating the plurality of event records includes determining a format to configure each event record with, selectively based on a type of monitoring event associated with each event record, and wherein the plurality of event records include at least two different event record format types;
generating appended event records by appending the event records with correlation vector data that identifies, for each event record, a context associated with the monitored event that is associated with the event record;
generating a batch of event records by batching all of the appended event records that correspond to the different monitoring events that were identified during the predetermined batch period of time;
obtain a security key from the cloud file sync service that is uniquely associated with a corresponding security key provided to the cloud storage for restricting access to a particular storage container associated with the on-premises computing system and that is managed by the cloud storage;
signing the batch of event records with the security key; and
transmitting the batch of event records with the security key to the cloud storage entity and which causes the batch of event records to be stored in the particular storage container.

### Claim 2 (depends on 1)

The computing system of claim 1, wherein the method further includes:
determining that the batch of records is to be replaced;
generating a new batch of records that includes the plurality of event records corresponding to the plurality of different monitoring events detected during the predetermined batch period of time, as well as a new plurality of event records corresponding to a new plurality of different monitoring events detected during a different time than the predetermined batch period of time; and
transmitting the new batch of records to the cloud storage with the security key.

### Claim 3 (depends on 2)

The computing system of claim 2, wherein the determining that the batch of records is to be replaced is based on a communication that is received by the on-premises computing system and that indicates that the batch of records is to be replaced.

### Claim 4 (depends on 1)

The computing system of claim 1, wherein the at least two different event record format types include a bond format type and a compressed format type that contains more data than is included in the bond format type, but which is compressed, wherein the bond format type is used to format low volume monitoring events and wherein the compressed format type is used to format high volume monitoring events.

### Claim 5 (depends on 1)

The computing system of claim 1, wherein the correlation vector data is used to match at least one event record in the batch of records with at least one different event record that is generated and stored separately from the batch of records.

### Claim 6 (depends on 5)

The computing system of claim 5, wherein the correlation vector data includes at least one of a machine identifier, a server identifier, a subscription identifier, an agent identifier or a cluster identifier.

### Claim 7 (depends on 5)

The computing system of claim 5, wherein the correlation vector data includes at least one of a computing environment condition existing during a monitored event or a resource being utilized during processing of the monitored event.

### Claim 8 (depends on 1)

The computing system of claim 1, wherein the security key is operable to restrict access to the particular storage container to only write access by the on-premises computing system.

### Claim 9 (depends on 1)

The computing system of claim 1, wherein the method further includes:
serializing the appended event records prior to transmitting the batch of event records.

### Claim 10 (depends on 1)

The computing system of claim 1, wherein the method further includes the on-premises computing system signing the batch of records with a digital signature associated with another security key associated with the on-premises computing system and that is distinguished from the security key that is uniquely associated with the corresponding security key provided to the cloud storage.

### Claim 11

A method implemented by an on-premises computing system for performing event storage and diagnostic processing in a hybrid cloud environment that includes a cloud storage and a cloud file sync service, the on-premises computing system comprising one or more processors and one or more computer-readable media having stored instructions that are executable by the one or more processors to implement the method, wherein the method includes the on-premises computing system performing at least the following:
identifying a plurality of different monitoring events of one or more machines in the on-premises computing system during a predetermined batch period of time;
generating a plurality of event records corresponding to the plurality of different monitoring events detected during the predetermined batch period of time, wherein generating the plurality of event records includes determining a format to configure each event record with, selectively based on a type of monitoring event associated with each event record, and wherein the plurality of event records include at least two different event record format types;
generating appended event records by appending the event records with correlation vector data that identifies, for each event record, a context associated with the monitored event that is associated with the event record;
generating a batch of event records by batching all of the appended event records that correspond to the different monitoring events that were identified during the predetermined batch period of time;
obtain a security key from the cloud file sync service that is uniquely associated with a corresponding security key provided to the cloud storage for restricting access to a particular storage container associated with the on-premises computing system and that is managed by the cloud storage;
signing the batch of event records with the security key; and
transmitting the batch of event records with the security key to the cloud storage entity and which causes the batch of event records to be stored in the particular storage container.

### Claim 12 (depends on 11)

The method of claim 11, wherein the method further includes:
determining that the batch of records is to be replaced;
generating a new batch of records that includes the plurality of event records corresponding to the plurality of different monitoring events detected during the predetermined batch period of time, as well as a new plurality of event records corresponding to a new plurality of different monitoring events detected during a different time than the predetermined batch period of time; and
transmitting the new batch of records to the cloud storage with the security key.

### Claim 13 (depends on 11)

The method of claim 11, wherein the at least two different event record format types include a bond format type and a compressed format type that contains more data than is included in the bond format type, but which is compressed, wherein the bond format type is used to format low volume monitoring events and wherein the compressed format type is used to format high volume monitoring events.

### Claim 14 (depends on 11)

The method of claim 11, wherein the correlation vector data is used to match at least one event record in the batch of records with at least one different event record that is generated and stored separately from the batch of records and wherein the correlation vector data includes at least one of a machine identifier, a server identifier, a subscription identifier, an agent identifier, a cluster identifier, a computing environment condition existing during a monitored event, or a resource being utilized during processing of the monitored event.

### Claim 15 (depends on 11)

The method of claim 11, wherein the security key is operable to restrict access to the particular storage container to only write access by the on-premises computing system.

### Claim 16 (depends on 11)

The method of claim 11, wherein the method further includes:
serializing the appended event records prior to transmitting the batch of event records.

### Claim 17 (depends on 11)

The method of claim 11, wherein the method further includes the on-premises computing system signing the batch of records with a digital signature associated with another security key associated with the on-premises computing system and that is distinguished from the security key that is uniquely associated with the corresponding security key provided to the cloud storage.

### Claim 18

A computer program product comprising one more hardware storage device having stored instructions that are executable by the one or more processors of a computing system for causing the computing system to implement a method that includes the computing system performing the following:
identifying a plurality of different monitoring events of one or more machines in the computing system during a predetermined batch period of time;
generating a plurality of event records corresponding to the plurality of different monitoring events detected during the predetermined batch period of time, wherein generating the plurality of event records includes determining a format to configure each event record with, selectively based on a type of monitoring event associated with each event record, and wherein the plurality of event records include at least two different event record format types;
generating appended event records by appending the event records with correlation vector data that identifies, for each event record, a context associated with the monitored event that is associated with the event record;
generating a batch of event records by batching all of the appended event records that correspond to the different monitoring events that were identified during the predetermined batch period of time;
obtain a first security key from the cloud file sync service that is uniquely associated with a corresponding security key used to restrict access to a particular storage container associated with the computing system;
signing the batch of event records with the security key; and
transmitting the batch of event records with the security key for storage in the particular storage container.

### Claim 19 (depends on 18)

The computer program product of claim 18, wherein the method further includes:
determining that the batch of records is to be replaced;
generating a new batch of records that includes the plurality of event records corresponding to the plurality of different monitoring events detected during the predetermined batch period of time, as well as a new plurality of event records corresponding to a new plurality of different monitoring events detected during a different time than the predetermined batch period of time; and
transmitting the new batch of records with the security key for storage in the storage container.

### Claim 20 (depends on 19)

The computer program product of claim 19, wherein the method further includes the computing system signing the batch of records with a digital signature associated with a second security key associated with the computing system and that is distinguished from the first security key.
