Currently, we "pop" the last message in a conversation and only add that as the gen_ai.request.messages value in order to manage the size of the span (we don't want to accidentally exceed it).
The ability to include the full conversation history is blocked by the "span first" feature. Once it's released, we need to revisit this to ensure that we're retaining the entire conversation history passed in contents in generate_content calls on the gen_ai.request.messages attribute on spans.
Currently, we "pop" the last message in a conversation and only add that as the
gen_ai.request.messagesvalue in order to manage the size of the span (we don't want to accidentally exceed it).The ability to include the full conversation history is blocked by the "span first" feature. Once it's released, we need to revisit this to ensure that we're retaining the entire conversation history passed in
contentsingenerate_contentcalls on thegen_ai.request.messagesattribute on spans.