Skip to content

Capture span's (and not transaction's) context for errors on span #192

@SergeyKleyman

Description

@SergeyKleyman

Derived from https://github.com/elastic/apm-dev/issues/390.

Currently .NET agent captures only transaction's context for a error even if the error in captured on a span which has its own context - span's context is just ignored. All this is according to current intake API spec.

Java agent team considers to include span's context in the captured error as well in some way - elastic/apm-agent-java#279. We might want to do that as well.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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