Skip to content

Commit

Permalink
Fix linting issue
Browse files Browse the repository at this point in the history
  • Loading branch information
kalyanaj committed Oct 17, 2023
1 parent 2101bdb commit c39b87c
Showing 1 changed file with 7 additions and 6 deletions.
13 changes: 7 additions & 6 deletions docs/trace/links-creation-with-new-activities/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,20 +7,21 @@ situation when you want to create a new trace with a new root activity
BEFORE invoking each of the fanned out operations, and at the same time
you want each of these new traces to be linked to the original activity.

To give an example, let's say you have a:
- Service A that receives a request for an operation that impacts 1000s of
To give an example, let's say:

- Service A receives a request for an operation that impacts 1000s of
resources.
- Let's say Service A fans out calls to Service B for each of these resource
- Service A then fans out calls to Service B for each of these resource
operations.

If you used the same trace for the entire flow, then you would likely end up
with a single very large trace with several 1000s or tens of 1000s of spans.
This can make visualizing and understanding the trace difficult.

Further, it may make it difficult to do programmatic analytics at the
*individual* resource operation level (for each of the 1000s of resources)
as there would be no single trace that corresponds to each of the individual
resource operations.
*individual* resource operation level (for each of the 1000s of resource
operations) as there would be no single trace that corresponds to each
of the individual resource operations.

Instead, by creating a new trace with a new root activity before the fanout
call, you get a separate trace for each of the resource operations. In
Expand Down

0 comments on commit c39b87c

Please sign in to comment.