chore: Adjust llm.tools semantic convention example #1180
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adjusting the example for llm.tools to make it consistent with how other list of object semantic conventions are repented in the documentation, so that it doesn't convey that there's something actually different in its structures compared to any other list of objects semantic convention, such as llm.input_messages and llm.output_messages. Ultimately, these open inference semantic conventions are flattened and not nested when ingested via OTLP (e.g.
llm.tools.0.tool.id,
llm.tools.1.tool.id` for semantic conventions that use list of objects), so there is no actual difference in the structure of the data between semantic conventions of the same type.Furthermore, some systems may choose to represent conventions like a list of objects as a single column as opposed to a flattened set of values, so this doc change also ensures that users know they can expect to consistently handle conventions of the same type (e.g. list of objects).