Skip to content

tracing: consider allowing the constant limits of tracing be configurable #87539

@yuzefovich

Description

@yuzefovich

Currently, we have quite a few constants that determine the maximum number of things included into the trace. Once the limit is exceeded, we start dropping things. However, it is quite desirable to increase these limits in some cases (e.g. when collecting a stmt bundle for a statement that reads a lot of data), so it'd be great if we could configure these limits somehow.

Jira issue: CRDB-19404

Epic CRDB-32402

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-observability-infC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)O-supportWould prevent or help troubleshoot a customer escalation - bugs, missing observability/tooling, docsP-3Issues/test failures with no fix SLAT-observabilitytarget-release-26.1.0

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions