Adding Monitors, Automatic field FER creation information to 3 Amazon apps

Author: chetanchoudhary-sumo

docs/integrations/amazon-aws/amazon-bedrock.md

@@ -388,6 +388,14 @@ import AppInstall from '../../reuse/apps/app-install-v2.md';
 
 <AppInstall/>
 
+As part of the app installation process, the following fields will be created by default:
+
+* `account`: The friendly name or alias assigned to the AWS account.
+* `region`: The geographical region where the AWS resource is located (for example, us-east-1 or eu-west-2).
+* `accountid`: The unique 12-digit identifier for the AWS account where the resource is present.
+* `namespace`: The AWS service namespace that the resource or metric belongs to (for example, AWS/EC2 or AWS/S3).
+* `modelid`: A specific identifier for the LLM Model within an AWS Bedrock.
+
 ## Viewing the Bedrock dashboards  
 
 We highly recommend you view these dashboards in the [AWS Observability view](/docs/dashboards/explore-view/#aws-observability) of the AWS Observability solution.
@@ -447,4 +455,19 @@ import AppUpdate from '../../reuse/apps/app-update.md';
 
 import AppUninstall from '../../reuse/apps/app-uninstall.md';
 
-<AppUninstall/>
+<AppUninstall/>
+
+## Create monitors for Amazon Bedrock app
+
+import CreateMonitors from '../../reuse/apps/create-monitors.md';
+
+<CreateMonitors/>
+
+### Amazon Bedrock Alerts
+
+| Name | Description | Alert Condition | Recover Condition |
+|:--|:--|:--|:--|
+| `Amazon Bedrock - Delete Action Detected` | This alert triggers when a Delete API call to the Amazon Bedrock environment is detected. | Count > 0 | Count < = 0 |
+| `Amazon Bedrock - High Model Invocation Latency` | This alert triggers when the average time to receive a response from a Bedrock model exceeds a configurable threshold in milliseconds. High latency can directly impact the user experience of your applications. | Count > 5000 | Count < = 5000 |
+| `Amazon Bedrock - High Number of Access Denied Errors` | This alert fires when there is a spike in AccessDeniedException errors in CloudTrail for the Bedrock service. This could indicate misconfigured IAM policies or a potential security threat. | Count > 5 | Count < = 5 |
+| `Amazon Bedrock - Model Invocation Server Error Detection` | This alert triggers if the number of server-side errors from model invocations increases more than configurable value (Default 5). This can indicate issues with the service, your input data, or permissions. | Count > 5 | Count < = 5 |

docs/integrations/amazon-aws/amazon-ec2-auto-scaling.md

@@ -159,6 +159,14 @@ import AppInstallNoDataSourceV2 from '../../reuse/apps/app-install-index-apps-v2
 
 <AppInstallNoDataSourceV2/>
 
+As part of the app installation process, the following fields will be created by default:
+
+* `account`: The friendly name or alias assigned to the AWS account.
+* `region`: The geographical region where the AWS resource is located (for example, us-east-1 or eu-west-2).
+* `accountid`: The unique 12-digit identifier for the AWS account where the resource is present.
+* `namespace`: The AWS service namespace that the resource or metric belongs to (for example, AWS/EC2 or AWS/AutoScaling).
+* `autoscalinggroup`: A specific identifier for the Auto Scaling Group within AWS EC2 Auto Scaling.
+
 ## Viewing Amazon EC2 Auto Scaling dashboards
 
 ### Amazon EC2 Autoscaling - Overview
@@ -228,4 +236,19 @@ import AppUpdate from '../../reuse/apps/app-update.md';
 
 import AppUninstall from '../../reuse/apps/app-uninstall.md';
 
-<AppUninstall/>
+<AppUninstall/>
+
+## Create monitors for Amazon EC2 Auto Scaling app
+
+import CreateMonitors from '../../reuse/apps/create-monitors.md';
+
+<CreateMonitors/>
+
+### Amazon EC2 Auto Scaling Alerts
+
+| Name | Description | Alert Condition | Recover Condition |
+|:--|:--|:--|:--|
+| `Amazon EC2 Auto Scaling - In-Service Capacity Below Desired` | This alert triggers when the number of healthy, active instances falls below the desired capacity. This indicates that your application may lack the capacity to handle its current load. | Count > 0 | Count < = 0 |
+| `Amazon EC2 Auto Scaling - Instance To Max Capacity Ratio` | Proactive alert that triggers when the total number of instances approaches the configured maximum size, warning of an inability to scale out further. | Count > 0.9 | Count < = 0.9 |
+| `Amazon EC2 Auto Scaling - Instances in Pending State` | This alert triggers when instances remain in a 'Pending' state for a prolonged period, indicating potential issues with instance launch or configuration. | Count > 0 | Count < = 0 |
+| `Amazon EC2 Auto Scaling - Instances in Terminating State` | This alert triggers when instances remain in a 'Terminating' state for a prolonged period, often indicating issues with lifecycle hooks. | Count > 0 | Count < = 0 |

docs/integrations/amazon-aws/amazon-opensearch.md

@@ -311,6 +311,14 @@ import AppInstall from '../../reuse/apps/app-install-v2.md';
 
 <AppInstall/>
 
+As part of the app installation process, the following fields will be created by default:
+
+* `account`: The friendly name or alias assigned to the AWS account.
+* `region`: The geographical region where the AWS resource is located (for example, us-east-1 or eu-west-2).
+* `accountid`: The unique 12-digit identifier for the AWS account where the resource is present.
+* `namespace`: The AWS service namespace that the resource or metric belongs to (for example, AWS/ES or AWS/OpenSearch).
+* `domainname`: A specific identifier for the OpenSearch domain within AWS OpenSearch Service.
+
 ## Viewing Amazon OpenSearch dashboards
 
 ### Overview
@@ -449,4 +457,21 @@ import AppUpdate from '../../reuse/apps/app-update.md';
 
 import AppUninstall from '../../reuse/apps/app-uninstall.md';
 
-<AppUninstall/>
+<AppUninstall/>
+
+## Create monitors for Amazon OpenSearch app
+
+import CreateMonitors from '../../reuse/apps/create-monitors.md';
+
+<CreateMonitors/>
+
+### Amazon OpenSearch Alerts
+
+| Name | Description | Alert Condition | Recover Condition |
+|:--|:--|:--|:--|
+| `Amazon OpenSearch - Cluster Write Operations Blocked` | This alert fires when the cluster is actively blocking write requests. This is a severe state that means applications cannot write new data to the cluster. | Count > = 1 | Count < 1 |
+| `Amazon OpenSearch - High Indexing Latency` | This alert triggers when the average indexing latency exceeds 1000ms, indicating a potential bottleneck in data ingestion pipelines. | Count > 1000 | Count < = 1000 |
+| `Amazon OpenSearch - High JVM Memory Pressure` | This alert fires when JVM Memory Pressure is consistently high, which can lead to long garbage collection pauses, slow performance, and potential out-of-memory errors. | Count > = 95 | Count < 95 |
+| `Amazon OpenSearch - Sustained High CPU Utilization` | This alert fires when CPU utilization is consistently high (>= 80%) for 15 minutes, indicating an overloaded cluster that may lead to performance degradation. | Count > = 80 | Count < 80 |
+| `Amazon OpenSearch - Unassigned Primary Shards Detected` | This alert fires when the cluster status is critical, indicating at least one primary shard and its replicas are not allocated. This signifies a non-functional cluster and potential data loss. | Count > = 1 | Count < 1 |
+| `Amazon OpenSearch - Unassigned Replica Shards Detected` | This alert fires when all primary shards are active but one or more replica shards are not allocated to a node. This compromises high availability. | Count > = 1 | Count < 1 |