Skip to content

Introduce a substitute value for AnnotatedValue.removed_because_over_size_limit and AnnotatedValue.removed_because_raw_data #6175

@ericapisani

Description

@ericapisani

We generally try to avoid setting none or empty strings on span attributes because it doesn't provide any meaningful information to users and increases the size of the envelope.

In scenarios where, within an integration, we are setting the request body data on a span attribute, and that request data is removed/annotated for some reason, we should set a value to indicate the reason why that data was removed.

Metadata

Metadata

Assignees

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