Skip to content

Document AnyValue attribute limits #4487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lmolkova opened this issue Apr 24, 2025 · 0 comments
Open

Document AnyValue attribute limits #4487

lmolkova opened this issue Apr 24, 2025 · 0 comments
Labels
spec:logs Related to the specification/logs directory Stale triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted

Comments

@lmolkova
Copy link
Contributor

lmolkova commented Apr 24, 2025

#4485 suggests using the following limits for complex attribute values:

Attribute value length limit SHOULD be applied to all leaf string nodes in
AnyValue which SHOULD be truncated to the configured limit.

Leaf nodes of an AnyValue attribute SHOULD count toward the attribute count limit.
If the limit is reached, the SDK MUST drop the entire AnyValue attribute;
partial exports are not allowed.

As well as potential ability on AnyValue to estimate its total size (which can be done at the construction time for performance reasons).

We can consider a separate set of attribute limits specifically for complex values, including a total size limit and ability to estimate AnyValue object size.

It's related to #4006 - a similar set of limits would be applicable to the log body with a caveat that log bodies may need a separate limit since log bodies are expected to be larger than attributes and backends tolerate large log bodies much better.

Regardless of the #4485 outcome, we need to define limits at least for the log attributes.

@lmolkova lmolkova added the spec:logs Related to the specification/logs directory label Apr 24, 2025
@mx-psi mx-psi added the triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted label Apr 28, 2025
@github-actions github-actions bot added the Stale label Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:logs Related to the specification/logs directory Stale triage:deciding:community-feedback Open to community discussion. If the community can provide sufficient reasoning, it may be accepted
Projects
None yet
Development

No branches or pull requests

2 participants