Repository navigation
[amazon_bedrock_agentcore] add gateway_application_logs data stream #15991 - #16587
14 commits merged into
Conversation
ghost
self-assigned this
ghost
added
Team:Obs-InfraObs
🚀 Benchmarks reportTo see the full report comment with |
| type: keyword | ||
| description: ID of the processed request. | ||
|
|
||
| - name: body |
There was a problem hiding this comment.
For the agentcore runtime application log request_payload_object is used as the field name for the flattened field. Can a similar naming convention be followed here, such as payload_object ?
| "body": { | ||
| "id": "7", | ||
| "isError": false, | ||
| "log": "Processing request for tool DocumentRetrieval___fetch_order_details from target XYZPROD001" |
There was a problem hiding this comment.
Can we extract the key parts of this and store them in ECS fields?
There was a problem hiding this comment.
The body.log field does not always follow a consistent format. In some cases, we may be able to extract values such as the tool name and target but these fields will not be present in all gateway logs.
There was a problem hiding this comment.
For the gateway, the tool operation name, target, and outcome of the tool operation (including target invocation results) are important observability information. When present, let's capture it and store them.
There was a problem hiding this comment.
Also, you may store the log data entirely in the messsage field
andrewkroh
added
the
documentation
💚 Build Succeeded
History
cc @gpop63 |
|
Package aws_bedrock_agentcore - 0.7.0 containing this change is available at https://epr.elastic.co/package/aws_bedrock_agentcore/0.7.0/ |
…lastic#15991 (elastic#16587) * add gateway data stream * bump package version * update readme * fix pr id * rename body field * improve pipeline * add gateway suffix * update readme * improve title
Overview
This PR adds the
gateway_application_logsdata stream.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots