# US 2025/0094124 A1 · Merging and visualizing observability data sets

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

- Number: US 2025/0094124 A1
- Document ID: US20250094124A1
- Status: Published application
- Kind: A1
- Application number: 18/467,332
- Filed: 2023-09-14
- Published: 2025-03-20
- Earliest claimed: 2023-09-14
- Assignees: Rubrik, Inc.
- Applicants: Rubrik, Inc.
- Inventors: Shubham Doshi; Nikita Dwivedi; Akash Gupta; Gaurav Maheshwari
- Web page: https://patentgrep.com/patent/US20250094124A1

## CPC

- G06F 7/14: Merging, i.e. combining at least two sets of record carriers each arranged in the same ordered sequence to produce a single set having the same ordered sequence
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- 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

A method for data processing is described. The method may include retrieving, from a cloud storage environment accessible to a data management system (DMS), two or more observability data sets associated with a set of time intervals within a selected time range. The observability data sets may contain a set of time-partitioned data blocks that include tracing data associated with operations performed by one or more nodes of a node cluster of the DMS during the selected time range. The method may further include merging the tracing data by selecting a first subset of overlapping time-partitioned data blocks, omitting a second subset of the overlapping time-partitioned data blocks, and retaining one or more non-overlapping time-partitioned data blocks. The method may further include transmitting data corresponding to a visualization of the merged tracing data.

## Claims

### Claim 1

A method for data processing, comprising:
retrieving, from a cloud storage environment accessible to a data management system (DMS), two or more observability data sets associated with a plurality of time intervals within a selected time range, the two or more observability data sets comprising a plurality of time-partitioned data blocks that include tracing data associated with operations performed by one or more nodes of a node cluster of the DMS during the selected time range;
merging, by a triage service of the DMS, the tracing data present in the two or more observability data sets based at least in part on selecting a first subset of overlapping time-partitioned data blocks that correspond to an overlapping time interval between the plurality of time intervals, omitting a second subset of the overlapping time-partitioned data blocks that correspond to the overlapping time interval, and retaining one or more non-overlapping time-partitioned data blocks that correspond to an earlier time interval or a later time interval of the plurality of time intervals; and
transmitting, by the DMS, data corresponding to a visualization of the merged tracing data associated with the selected time range.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
detecting, by the DMS, a failure or performance issue associated with at least one operation performed by the one or more nodes of the node cluster, wherein the selected time range corresponds to the detected failure or performance issue.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
generating, by the DMS, the visualization of the merged tracing data as part of a performance investigation related to the detected failure or performance issue.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
acquiring, by a distributed tracing service of the DMS, the tracing data from one or more processing services provided by the one or more nodes of the node cluster; and
uploading, to the cloud storage environment, the two or more observability data sets containing the tracing data.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
downloading, by the DMS, the two or more observability data sets from the cloud storage environment using a tracing support library; and
writing, by the DMS, the tracing data from the two or more observability data sets to a data file using the tracing support library, wherein the triage service uses the data file to merge the tracing data associated with the selected time range.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
storing, by the DMS, the two or more observability data sets in a first type of cloud storage for a first duration of time; and
archiving, by the DMS, the two or more observability data sets in a second type of cloud storage after the first duration of time.

### Claim 7 (depends on 6)

The method of claim 6, wherein the two or more observability data sets are retained in the second type of cloud storage for a second duration of time indicated by a cloud retention policy of the DMS.

### Claim 8 (depends on 6)

The method of claim 6, wherein retrieving the two or more observability data sets comprises:
asynchronously restoring, by the DMS, at least one observability data set from the second type of cloud storage to the first type of cloud storage using one or more application programming interfaces (APIs) provided by the cloud storage environment, wherein at least some of the merged tracing data is from the at least one observability data set restored from the second type of cloud storage.

### Claim 9 (depends on 1)

The method of claim 1, wherein merging the tracing data comprises:
combining the plurality of time-partitioned data blocks of the two or more observability data sets into a non-time-partitioned visualization of the merged tracing data.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
retrieving, by an authorized user of the DMS, an authentication token from an identity-based secrets and encryption management system integrated with the DMS; and
transmitting, to an endpoint associated with a tracing support library provided by the DMS, a request to fetch, download, extract, or restore the two or more observability data sets from the cloud storage environment, wherein the request comprises the authentication token retrieved from the identity-based secrets and encryption management system.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
verifying, by the endpoint associated with the tracing support library, an identity of the authorized user based at least in part on the authentication token provided with the request and a set of cloud credentials obtained from the identity-based secrets and encryption management system; and
retrieving, by the endpoint associated with the tracing support library, the two or more observability data sets from the cloud storage environment using the set of cloud credentials obtained from the identity-based secrets and encryption management system.

### Claim 12 (depends on 1)

The method of claim 1, wherein at least some of the plurality of time-partitioned data blocks are immutable.

### Claim 13 (depends on 1)

The method of claim 1, wherein at least one observability data set comprises block storage containing one or more compacted or non-compacted time-partitioned data blocks, write ahead log block storage containing one or more partial or full write ahead log blocks, an append file containing trace data, or a combination thereof.

### Claim 14 (depends on 1)

The method of claim 1, wherein a difference between a trace data retention period and an observability data set collection period corresponds to a duration of overlap between the two or more observability data sets.

### Claim 15 (depends on 14)

The method of claim 14, wherein the subset of overlapping time-partitioned data blocks correspond to the duration of overlap between the two or more observability data sets.

### Claim 16 (depends on 1)

The method of claim 1, wherein the subset of overlapping time-partitioned data blocks comprise compacted data blocks, non-compacted data blocks, write ahead log blocks, an append file, or any combination thereof.

### Claim 17 (depends on 1)

The method of claim 1, wherein overlapping time-partitioned data blocks corresponding to the later time interval are selected for inclusion within the merged tracing data and overlapping time-partitioned data blocks corresponding to the earlier time interval are omitted from the merged tracing data.

### Claim 18 (depends on 1)

The method of claim 1, wherein merging the tracing data comprises:
retaining a first set of write ahead log blocks that correspond to the earlier time interval; and
omitting a second set of write ahead log blocks that correspond to the later time interval.

### Claim 19

A data management system (DMS), comprising:
one or more memories storing processor-executable code; and
one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the DMS to:
retrieve, from a cloud storage environment accessible to the DMS, two or more observability data sets associated with a plurality of time intervals within a selected time range, the two or more observability data sets comprising a plurality of time-partitioned data blocks that include tracing data associated with operations performed by one or more nodes of a node cluster of the DMS during the selected time range;
merge, by a triage service of the DMS, the tracing data present in the two or more observability data sets based at least in part on selecting a first subset of overlapping time-partitioned data blocks that correspond to an overlapping time interval between the set of time intervals, omitting a second subset of the overlapping time-partitioned data blocks that correspond to the overlapping time interval, and retaining one or more non-overlapping time-partitioned data blocks that correspond to an earlier time interval or a later time interval of the set of time intervals; and
transmit, by the DMS, data corresponding to a visualization of the merged tracing data associated with the selected time range.

### Claim 20

A non-transitory computer-readable medium storing code that comprises instructions executable by one or more processors to:
retrieve, from a cloud storage environment accessible to a data management system (DMS), two or more observability data sets associated with a plurality of time intervals within a selected time range, the two or more observability data sets comprising a plurality of time-partitioned data blocks that include tracing data associated with operations performed by one or more nodes of a node cluster of the DMS during the selected time range;
merge, by a triage service of the DMS, the tracing data present in the two or more observability data sets based at least in part on selecting a first subset of overlapping time-partitioned data blocks that correspond to an overlapping time interval between the plurality of time intervals, omitting a second subset of the overlapping time-partitioned data blocks that correspond to the overlapping time interval, and retaining one or more non-overlapping time-partitioned data blocks that correspond to an earlier time interval or a later time interval of the plurality of time intervals; and
transmit, by the DMS, data corresponding to a visualization of the merged tracing data associated with the selected time range.
