Skip to content

Regular spans can't be a child of profiler-inferred spans #1112

@sudhireer868

Description

@sudhireer868

Describe the bug

APM Timeline starts with DB spans and shows them at top, but as per the application execution Java spans should be shown first and then DB spans.

Steps to reproduce

Attached screenshots of our application.

In the below screenshot the transaction starts with DB Span:

APM-SPAN Order Mismatch

Below screenshot shows Java Spans after DB spans:

Java Span Misorder2

Expected behavior

Various spans hierarchy (like JAVA, DB etc) should be as per the application execution flow in the APM timeline.

Debug logs

Click to expand
replace this line with your debug logs

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions