Skip to content

Summarize traces to a single event #1523

@mterhar

Description

@mterhar

Is your feature request related to a problem? Please describe.

The problem with sampling based on TraceID is that sometimes traces are related.
The problem with dropping all evidence of a trace is that there may be clues about it that you'd want to keep handy.

Describe the solution you'd like

This mechanism in the pr linked below is a way to have refinery use the spans in its cache to send some record of what it saw to Honeycomb.

Describe alternatives you've considered

Session awareness seems to require buffering spans for too long.

Link awareness will end up propagating too far and keeping too many spans in some cases.
#882

Additional context

In the PR, there is quite a bit more context: #1508

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions