Amazon Bedrock - Add Guardrails metrics

[agithomas]

• Enhancement

Proposed commit message

Add guardrails dataset for guardrail metrics

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 with Guardrail API
• Integration testing without using Guardrail API
• Agent invocation testing
• Input data guardrail testing
• Output data guardrail testing

How to test this PR locally

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

Screenshots

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[muthu-mps]

Can we exclude the guradrail_ from guardrails.guardrail_content_source for all dimension fields? This would make the field name consistent with the rest of the fields. WDYT?

[agithomas]

I had the below reasoning to follow this naming convension

1. When i looked at the AWS documentation, i could see the dimension names Operation and GuardrailContentSource. If we format the name of the field as ContentSource or 'arn`, in the context of LLM application ,where content source can also mean the source of knowledge, arn can be the arn of the model or arn of agent and so on. So, i think, it is best to keep the name as guardrail_content_source or guardrail_arn to make it less ambiguous for the user.

2. We don't have a description of the dimension fields.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: cbd975a94fbce71824283572315dffe57145f68c

History

• 💚 Build #20111 succeeded 8a666d5433d8eb1c8427daf6cb708874f82072c1
• 💔 Build #20108 failed 8bffc6f004789102797c09db624128aea5e20411

[elastic-sonarqube]

Quality Gate failed

Failed conditions
26.9% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube

[muthu-mps]

LGTM!

[elastic-vault-github-plugin-prod]

Package aws_bedrock - 0.19.0 containing this change is available at https://epr.elastic.co/package/aws_bedrock/0.19.0/