Skip to content

Conversation

@gpop63
Copy link
Contributor

@gpop63 gpop63 commented Dec 16, 2025

Overview

This PR adds the gateway_application_logs data stream.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

  • Closes elastic/obs-integration-team/issues/699

Screenshots

@gpop63 gpop63 self-assigned this Dec 16, 2025
@gpop63 gpop63 added Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations] Integration:aws_bedrock_agentcore Amazon Bedrock AgentCore enhancement New feature or request labels Dec 16, 2025
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@gpop63 gpop63 marked this pull request as ready for review December 17, 2025 15:45
@gpop63 gpop63 requested a review from a team as a code owner December 17, 2025 15:45
type: keyword
description: ID of the processed request.

- name: body
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we extract the key parts of this and store them in ECS fields?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, you may store the log data entirely in the messsage field

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @gpop63

Copy link
Contributor

@agithomas agithomas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@andrewkroh andrewkroh added the documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. label Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:aws_bedrock_agentcore Amazon Bedrock AgentCore Team:Obs-InfraObs Observability Infrastructure Monitoring team [elastic/obs-infraobs-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants