# US 2025/0168091 A1 · Application transaction recommendation engine based on endpoint flows

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

- Number: US 2025/0168091 A1
- Document ID: US20250168091A1
- Status: Published application
- Kind: A1
- Application number: 18/442,346
- Filed: 2024-02-15
- Published: 2025-05-22
- Earliest claimed: 2023-11-20
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Ryan Nicholas TERBUSH; Jason LO
- Web page: https://patentgrep.com/patent/US20250168091A1

## CPC

- H04L 43/062: related to network traffic
- H04L 43/10: Active monitoring, e.g. heartbeat, ping or trace-route
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one embodiment, a method comprises: evaluating, by a device while traversing a plurality of ordered telemetry spans of a given telemetry trace, whether any of the plurality of ordered telemetry spans are starting points for a respective endpoint flow that represents a possible path taken within a particular application flow; determining, by the device and based on evaluating, one or more particular endpoint flows to be included within a particular application transaction reporting structure associated with the particular application flow; and reporting, by the device, metrics corresponding to the one or more particular endpoint flows within a context of the particular application transaction reporting structure.

## Claims

### Claim 1

A method, comprising:
evaluating, by a device while traversing a plurality of ordered telemetry spans of a given telemetry trace, whether any of the plurality of ordered telemetry spans are starting points for a respective endpoint flow that represents a possible path taken within a particular application flow;
determining, by the device and based on evaluating, one or more particular endpoint flows to be included within a particular application transaction reporting structure associated with the particular application flow; and
reporting, by the device, metrics corresponding to the one or more particular endpoint flows within a context of the particular application transaction reporting structure.

### Claim 2 (depends on 1)

The method as in claim 1, further comprising:
reporting the metrics based on corresponding starting points for the one or more particular endpoint flows; and
reporting additional metrics from subsequent spans of the plurality of ordered telemetry spans following the corresponding starting points for each of the one or more particular endpoint flows within a context of a previous endpoint flow.

### Claim 3 (depends on 2)

The method as in claim 2, wherein:
the given telemetry trace includes one or more transitions to establish a plurality of trace paths for the given telemetry trace,
the subsequent spans of the plurality of ordered telemetry spans are divided into corresponding paths of the plurality of trace paths, and
reporting the additional metrics from subsequent spans of the plurality of ordered telemetry spans are further based on the corresponding paths of the subsequent spans.

### Claim 4 (depends on 1)

The method as in claim 1, wherein evaluating is based on one or more evaluation criterion chosen from a group consisting of: a name of the respective endpoint flow; a position of a respective telemetry span among the plurality of ordered telemetry spans of the given telemetry trace; a span type associated with the respective telemetry span among the plurality of ordered telemetry spans; resource attributes associated with the respective endpoint flow; and attributes associated with the plurality of ordered telemetry spans.

### Claim 5 (depends on 1)

The method as in claim 1, further comprising:
ingesting the plurality of ordered telemetry spans of the particular application flow from a plurality of sources across a computer network.

### Claim 6 (depends on 1)

The method as in claim 1, wherein evaluating is based on attributes containing business data or request routing data, or both.

### Claim 7 (depends on 1)

The method as in claim 1, further comprising:
detecting metric variance within a given endpoint flow of the one or more particular endpoint flows; and
splitting the given endpoint flow into first and second separated endpoint flows based on the metric variance.

### Claim 8 (depends on 1)

The method as in claim 1, further comprising:
detecting high cardinality between a plurality of the one or more particular endpoint flows; and
combining the plurality of the one or more particular endpoint flows into a single combined endpoint flow.

### Claim 9 (depends on 1)

The method as in claim 1, wherein the plurality of ordered telemetry spans comprise one or more of OpenTelemetry data, metrics, events, logs, or traces.

### Claim 10 (depends on 1)

The method as in claim 1, wherein evaluating is based on applying a machine learning model to the plurality of ordered telemetry spans.

### Claim 11 (depends on 1)

The method as in claim 1, further comprising:
recommending the one or more particular endpoint flows to be included within the particular application transaction reporting structure associated with the particular application flow; and
receiving confirmation of the one or more particular endpoint flows to be included within the particular application transaction reporting structure associated with the particular application flow prior to reporting the metrics corresponding to the one or more particular endpoint flows within the context of the particular application transaction reporting structure.

### Claim 12 (depends on 1)

The method as in claim 1, further comprising:
identifying the one or more particular endpoint flows, wherein identifying is based on common session identifiers or client identifiers within the plurality of ordered telemetry spans of the given telemetry trace.

### Claim 13 (depends on 1)

The method as in claim 1, further comprising:
reporting further additional metrics corresponding to a secondary endpoint flow detected within the given telemetry trace within the context of the particular application transaction reporting structure.

### Claim 14

An apparatus, comprising:
one or more network interfaces to communicate with a network;
a processor coupled to the one or more network interfaces and configured to execute one or more processes; and
a memory configured to store a process that is executable by the processor, the process comprising:
evaluating, while traversing a plurality of ordered telemetry spans of a given telemetry trace, whether any of the plurality of ordered telemetry spans are starting points for a respective endpoint flow that represents a possible path taken within a particular application flow;
determining, based on evaluating, one or more particular endpoint flows to be included within a particular application transaction reporting structure associated with the particular application flow; and
reporting metrics corresponding to the one or more particular endpoint flows within a context of the particular application transaction reporting structure.

### Claim 15 (depends on 14)

The apparatus as in claim 14, the process further comprising:
reporting the metrics based on corresponding starting points for the one or more particular endpoint flows; and
reporting additional metrics from subsequent spans of the plurality of ordered telemetry spans following the corresponding starting points for each of the one or more particular endpoint flows within a context of a previous endpoint flow.

### Claim 16 (depends on 15)

The apparatus as in claim 15, wherein:
the given telemetry trace includes one or more transitions to establish a plurality of trace paths for the given telemetry trace,
the subsequent spans of the plurality of ordered telemetry spans are divided into corresponding paths of the plurality of trace paths, and
the additional metrics from subsequent spans of the plurality of ordered telemetry spans are further based on the corresponding paths of the subsequent spans.

### Claim 17 (depends on 14)

The apparatus as in claim 14, wherein evaluating is based on one or more evaluation criterion chosen from a group consisting of: a name of the respective endpoint flow; a position of a respective telemetry span among the plurality of ordered telemetry spans of the given telemetry trace; a span type associated with the respective telemetry span among the plurality of ordered telemetry spans; resource attributes associated with the respective endpoint flow; and attributes associated with the plurality of ordered telemetry spans.

### Claim 18 (depends on 14)

The apparatus as in claim 14, wherein evaluating is based on attributes containing business data or request routing data, or both.

### Claim 19 (depends on 14)

The apparatus as in claim 14, to the process further comprising:
recommending the one or more particular endpoint flows to be included within the particular application transaction reporting structure associated with the particular application flow; and
receiving confirmation of the one or more particular endpoint flows to be included within the particular application transaction reporting structure associated with the particular application flow prior to reporting the metrics corresponding to the one or more particular endpoint flows within the context of the particular application transaction reporting structure.

### Claim 20

A tangible, non-transitory, computer-readable medium having computer-executable instructions stored thereon that, when executed by a processor on a computer, cause the computer to perform a method comprising:
evaluating, while traversing a plurality of ordered telemetry spans of a given telemetry trace, whether any of the plurality of ordered telemetry spans are starting points for a respective endpoint flow that represents a possible path taken within a particular application flow;
determining, based on evaluating, one or more particular endpoint flows to be included within a particular application transaction reporting structure associated with the particular application flow; and
reporting metrics corresponding to the one or more particular endpoint flows within a context of the particular application transaction reporting structure.
