Skip to content

Profiling concurrent transactions #2209

@stefanosiano

Description

@stefanosiano

Problem Statement

Our profiler works with only one transaction at a time.
The sdk has several options, including one that automatically starts a transaction on some ui interaction.
If I add a button which on click manually starts a transaction to be profiled, an automatic transaction is started first, so that one is profiled. When the manual transaction is started, the automatic one hasn't finished, yet, so the profiler ignores the manual transaction, since it doesn't have the notion of scope.

We're going to leave this issue until fixed, which is currently a wip.

Solution Brainstorm

we wrote this doc

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions