Skip to content

Conversation

@agithomas
Copy link
Contributor

  • Enhancement

Proposed commit message

Add alert templates for the Amazon Bedrock agentcore runtime.

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

  • Integration testing

How to test this PR locally

  • elastic-package build && elastic-package stack up -v -d --services package-registry

Screenshots

Not applicable.

"timeWindowSize": 5,
"timeWindowUnit": "m",
"esqlQuery": {
"esql": "// Alert triggers when system errors occur during AWS Bedrock AgentCore runtime invocations.\n//\n// System errors correspond to InvocationError.Internal - Internal server error (500).\n// These are server-side errors indicating infrastructure or service issues.\n//\n// The alert is grouped by cloud account, region, and agent endpoint name (aws.dimensions.Name)\n// to pinpoint the specific agent endpoint experiencing issues.\n//\n// To reduce alert noise, increase the threshold (e.g., `total_system_errors > 5`) to only\n// alert on sustained error patterns rather than transient service disruptions.\n\nFROM metrics-aws_bedrock_agentcore.metrics-*\n| WHERE aws.dimensions.Operation == \"InvokeAgentRuntime\"\n| STATS total_system_errors = sum(aws.bedrock_agentcore.metrics.SystemErrors.sum) BY cloud.account.id, cloud.region, aws.dimensions.Name\n| WHERE total_system_errors > 0"
Copy link
Contributor

Choose a reason for hiding this comment

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

To reduce alert noise, increase the threshold (e.g., total_system_errors > 5) to only.

Should the default threshold itself configured to >5 and suggest user to modify? WDYT?

Copy link
Contributor Author

@agithomas agithomas Nov 21, 2025

Choose a reason for hiding this comment

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

There are pros and cons for both approaches.

If >0, no errors go un-noticed and is much suited for the new deployments. Users can increase the threshold based on their noise level. It's good for low-traffic agents.

Copy link
Contributor

@muthu-mps muthu-mps left a comment

Choose a reason for hiding this comment

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

LGTM!

@elasticmachine
Copy link

elasticmachine commented Nov 21, 2025

💔 Build Failed

Failed CI Steps

History

conditions:
kibana:
version: "^8.19.0 || ^9.1.0"
version: "^8.19.0 || ^9.2.1"
Copy link
Contributor

Choose a reason for hiding this comment

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

Is this bump necessary? In other alerts PRs we kept 9.1.x. cc: @muthu-mps

Copy link
Contributor

@gpop63 gpop63 left a comment

Choose a reason for hiding this comment

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

Alerts look good!

@andrewkroh andrewkroh added the Integration:aws_bedrock_agentcore Amazon Bedrock AgentCore label Nov 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration:aws_bedrock_agentcore Amazon Bedrock AgentCore

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants