[OOTB Alerts] Generate README for Alerting Rule Templates

packages/aws_bedrock_agentcore/_dev/build/docs/README.md

@@ -64,4 +64,7 @@ The metrics include the following dimensions for enhanced filtering and analysis
 - `SessionId`: The session identifier for agent invocations
 
 {{event "metrics"}}
-{{fields "metrics"}}
+{{fields "metrics"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/aws_bedrock_agentcore/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.3.0"
+  changes:
+    - description: Update README with alerting rule templates.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "0.2.0"
   changes:
     - description: Add browser tool, and code interpreter metrics with dashboards.
@@ -9,7 +14,7 @@
     - description: Add agent_name and endpoint_name fields extracted for InvokeAgentRuntime operations.
       type: enhancement
       link: https://github.com/elastic/integrations/pull/16143
-- version: "0.0.3" 
+- version: "0.0.3"
   changes:
     - description: Add alerting rule template for the agent runtime
       type: enhancement

packages/aws_bedrock_agentcore/docs/README.md

@@ -194,3 +194,26 @@ An example event for `metrics` looks as following:
 | data_stream.namespace | Data stream namespace. | constant_keyword |  |  |
 | data_stream.type | Data stream type. | constant_keyword |  |  |
 | event.module | Name of the module this data is coming from. If your monitoring agent supports the concept of modules or plugins to process events of a given source (e.g. Apache logs), `event.module` should contain the name of this module. | constant_keyword |  |  |
+
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[AWS Bedrock AgentCore] Agent runtime high latency**
+
+
+
+**[AWS Bedrock AgentCore] Agent runtime system errors**
+
+
+
+**[AWS Bedrock AgentCore] Agent runtime user errors**
+
+
+

packages/aws_bedrock_agentcore/manifest.yml

@@ -1,7 +1,7 @@
 format_version: 3.4.0
 name: aws_bedrock_agentcore
 title: "Amazon Bedrock AgentCore"
-version: 0.2.0
+version: 0.3.0
 source:
   license: "Elastic-2.0"
 description: "Collect Amazon Bedrock AgentCore's Agent runtime, Gateway, Identity, Memory, Browser Tools and Code Interpreter metrics using Elastic Agent"

packages/azure_ai_foundry/_dev/build/docs/README.md

@@ -95,3 +95,6 @@ The Azure AI Foundry metrics provide insights into the performance and usage of
 For more details on ECS fields, check the [ECS Field Reference](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) documentation.
 
 {{fields "metrics"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/azure_ai_foundry/changelog.yml

@@ -1,3 +1,8 @@
+- version: "0.7.1"
+  changes:
+    - description: Update README with Alerting Rule Templates.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "0.7.0"
   changes:
     - description: Add Alerting Rule Templates.

packages/azure_ai_foundry/docs/README.md

@@ -464,3 +464,25 @@ For more details on ECS fields, check the [ECS Field Reference](https://www.elas
 | dataset.namespace | Dataset namespace. | constant_keyword |  |  |
 | dataset.type | Dataset type. | constant_keyword |  |  |
 
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[Azure AI Foundry] Latency high**
+
+
+
+**[Azure AI Foundry] Model Availability above threshold**
+
+
+
+**[Azure AI Foundry] Provisioned Utilization above threshold**
+
+
+

packages/azure_ai_foundry/manifest.yml

@@ -1,7 +1,7 @@
 format_version: 3.4.0
 name: azure_ai_foundry
 title: "Azure AI Foundry"
-version: "0.7.0"
+version: "0.7.1"
 source:
   license: "Elastic-2.0"
 description: "Collects Azure AI Foundry logs and metrics"

packages/azure_openai/_dev/build/docs/README.md

@@ -109,3 +109,6 @@ The primary aggregation value will be retrieved for all the metrics contained in
 For more details on ECS fields, check the [ECS Field Reference](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) documentation.
 
 {{fields "metrics"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/azure_openai/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "1.10.1"
+  changes:
+    - description: Update README with Alerting Rule Templates.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "1.10.0"
   changes:
     - description: Add Alerting Rule Templates.

packages/azure_openai/docs/README.md

@@ -379,3 +379,25 @@ For more details on ECS fields, check the [ECS Field Reference](https://www.elas
 | dataset.namespace | Dataset namespace. | constant_keyword |  |  |
 | dataset.type | Dataset type. | constant_keyword |  |  |
 
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[Azure OpenAI] Latency high**
+
+
+
+**[Azure OpenAI] Provisioned Utilization above threshold**
+
+
+
+**[Azure OpenAI] Quota Error Rates above threshold**
+
+
+

packages/azure_openai/manifest.yml

@@ -1,7 +1,7 @@
 format_version: 3.4.0
 name: azure_openai
 title: "Azure OpenAI"
-version: "1.10.0"
+version: "1.10.1"
 source:
   license: "Elastic-2.0"
 description: "Collects Azure OpenAI Logs and Metrics"

packages/microsoft_sqlserver/_dev/build/docs/README.md

@@ -186,3 +186,6 @@ The Microsoft SQL Server `transaction_log` dataset provides metrics from the log
 Please refer to the following [document](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) for detailed information on ECS fields.
 
 {{fields "transaction_log"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/microsoft_sqlserver/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "2.15.0"
+  changes:
+    - description: Update README with Alerting Rule Template.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "2.14.1"
   changes:
     - description: Change the default value for the username.

packages/microsoft_sqlserver/docs/README.md

@@ -624,3 +624,25 @@ Please refer to the following [document](https://www.elastic.co/guide/en/ecs/cur
 | mssql.query | The SQL queries executed. | keyword |  |  |
 | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword |  |  |
 
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[MicrosoftSQL Server] Lock Waits above threshold**
+
+
+
+**[MicrosoftSQL Server] Memory Grants Pending above threshold**
+
+
+
+**[MicrosoftSQL Server] Used Log Space above threshold**
+
+
+

packages/microsoft_sqlserver/manifest.yml

@@ -1,7 +1,7 @@
 format_version: "3.4.0"
 name: microsoft_sqlserver
 title: "Microsoft SQL Server"
-version: "2.14.1"
+version: "2.15.0"
 description: Collect events from Microsoft SQL Server with Elastic Agent
 type: integration
 categories:

packages/mongodb/_dev/build/docs/README.md

@@ -184,3 +184,6 @@ The fields reported are:
 Please refer to the following [document](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) for detailed information on ECS fields.
 
 {{fields "status"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/mongodb/changelog.yml

@@ -1,3 +1,8 @@
+- version: "1.24.0"
+  changes:
+    - description: Update README with Alerting Rule Template.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "1.23.0"
   changes:
     - description: Add alerting rule templates.

packages/mongodb/docs/README.md

@@ -1645,3 +1645,37 @@ Please refer to the following [document](https://www.elastic.co/guide/en/ecs/cur
 | mongodb.status.write_backs_queued | True when there are operations from a mongos instance queued for retrying. | boolean |  |
 | service.address | Address of the machine where the service is running. | keyword |  |
 
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[MongoDB] WiredTiger cache pressure**
+
+
+
+**[MongoDB Availability] High connection usage**
+
+
+
+**[MongoDB] Oplog headroom critically low**
+
+
+
+**[MongoDB] Replica member down**
+
+
+
+**[MongoDB] High replication lag**
+
+
+
+**[MongoDB] Unhealthy replica members**
+
+
+

packages/mongodb/manifest.yml

@@ -1,6 +1,6 @@
 name: mongodb
 title: MongoDB
-version: "1.23.0"
+version: "1.24.0"
 description: Collect logs and metrics from MongoDB instances with Elastic Agent.
 type: integration
 categories:

packages/mysql/_dev/build/docs/README.md

@@ -160,3 +160,6 @@ The MySQL `status` dataset collects data from MySQL by running a `SHOW GLOBAL ST
 Refer to the following [document](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) for detailed information on ECS fields.
 
 {{fields "status"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/mysql/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "1.29.1"
+  changes:
+    - description: Update README with alerting rule templates.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "1.29.0"
   changes:
     - description: Add alerting rule templates.

packages/mysql/docs/README.md

@@ -1083,3 +1083,25 @@ Refer to the following [document](https://www.elastic.co/guide/en/ecs/current/ec
 | mysql.status.threads.running | The number of running threads. | long | gauge |
 | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword |  |
 
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[MySQL Galera] Cluster State Abnormal**
+
+
+
+**[MySQL Replica] Replication Lag High**
+
+
+
+**[MySQL Performance] Slow Query Latency High**
+
+
+

packages/mysql/manifest.yml

@@ -1,7 +1,7 @@
 format_version: "3.4.0"
 name: mysql
 title: MySQL
-version: "1.29.0"
+version: "1.29.1"
 description: Collect logs and metrics from MySQL servers with Elastic Agent.
 type: integration
 categories:

packages/postgresql/_dev/build/docs/README.md

@@ -136,3 +136,6 @@ The `statement` dataset periodically fetches metrics from PostgreSQL servers.
 Please refer to the following [document](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) for detailed information on ECS fields.
 
 {{fields "statement"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}

packages/postgresql/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "1.32.1"
+  changes:
+    - description: Update README with Alerting Rule Templates.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/16139
 - version: "1.32.0"
   changes:
     - description: Add Alerting Rule Templates.

packages/postgresql/docs/README.md

@@ -746,3 +746,21 @@ Please refer to the following [document](https://www.elastic.co/guide/en/ecs/cur
 | postgresql.statement.user.id | OID of the user logged into the backend that ran the query. | long |  |
 | service.address | Address where data about this service was collected from. This should be a URI, network address (ipv4:port or [ipv6]:port) or a resource path (sockets). | keyword |  |
 
+
+## Alerting Rule Template
+Alert rule templates provide pre-defined configurations for creating alert rules in Kibana.
+
+For more information, refer to the [Elastic documentation](https://www.elastic.co/docs/reference/fleet/alerting-rule-templates).
+
+Alert rule templates require Elastic Stack version 9.2.0 or later.
+
+The following alert rule templates are available:
+
+**[PostgreSQL] Buffer Cache Hit Ratio above threshold**
+
+
+
+**[PostgreSQL] Latency high**
+
+
+

packages/postgresql/manifest.yml

@@ -1,7 +1,7 @@
 format_version: "3.4.0"
 name: postgresql
 title: PostgreSQL
-version: "1.32.0"
+version: "1.32.1"
 description: Collect logs and metrics from PostgreSQL servers with Elastic Agent.
 type: integration
 categories:

packages/system/_dev/build/docs/README.md

@@ -484,3 +484,6 @@ This data should be available without elevated permissions.
 Please refer to the following [document](https://www.elastic.co/guide/en/ecs/current/ecs-field-reference.html) for detailed information on ECS fields.
 
 {{fields "uptime"}}
+
+## Alerting Rule Template
+{{alertRuleTemplates}}