Merge branch 'main' into chore/tag-citrix_waf

Author: taylor-swanson

.github/CODEOWNERS

@@ -87,6 +87,7 @@
 /packages/aws_billing @elastic/obs-infraobs-integrations 
 /packages/aws_logs @elastic/obs-ds-hosted-services
 /packages/aws_mq @elastic/obs-infraobs-integrations
+/packages/aws_vpcflow_otel @elastic/obs-infraobs-integrations
 /packages/awsfargate @elastic/obs-infraobs-integrations
 /packages/awsfirehose @elastic/obs-ds-hosted-services
 /packages/azure @elastic/obs-infraobs-integrations @elastic/obs-ds-hosted-services @elastic/security-service-integrations
@@ -204,6 +205,7 @@
 /packages/elastic_package_registry @elastic/ecosystem
 /packages/elastic_security @elastic/security-service-integrations
 /packages/elasticsearch @elastic/stack-monitoring
+/packages/aws_elb_otel @elastic/obs-infraobs-integrations
 /packages/endace @elastic/integration-experience @elastic/sec-linux-platform
 /packages/endace/data_stream/flow @elastic/sec-linux-platform
 /packages/endace/data_stream/log @elastic/integration-experience
@@ -429,6 +431,7 @@
 /packages/system/data_stream/load @elastic/obs-infraobs-integrations
 /packages/system/data_stream/memory @elastic/obs-infraobs-integrations
 /packages/system/data_stream/network @elastic/obs-infraobs-integrations
+/packages/system/data_stream/ntp @elastic/obs-infraobs-integrations
 /packages/system/data_stream/process @elastic/obs-infraobs-integrations
 /packages/system/data_stream/process_summary @elastic/obs-infraobs-integrations
 /packages/system/data_stream/security @elastic/sec-windows-platform

.github/ISSUE_TEMPLATE/integration_bug.yml

@@ -43,7 +43,9 @@ body:
         - Auth0 [auth0]
         - authentik [authentik]
         - AWS Cost and Usage Report (CUR 2.0) [aws_billing]
+        - AWS ELB OpenTelemetry Assets [aws_elb_otel]
         - AWS Fargate (for ECS clusters) [awsfargate]
+        - AWS VPC Flow Logs OpenTelemetry Assets [aws_vpcflow_otel]
         - AWS [aws]
         - Azure AI Foundry [azure_ai_foundry]
         - Azure App Service [azure_app_service]

.github/ISSUE_TEMPLATE/integration_feature_request.yml

@@ -43,7 +43,9 @@ body:
         - Auth0 [auth0]
         - authentik [authentik]
         - AWS Cost and Usage Report (CUR 2.0) [aws_billing]
+        - AWS ELB OpenTelemetry Assets [aws_elb_otel]
         - AWS Fargate (for ECS clusters) [awsfargate]
+        - AWS VPC Flow Logs OpenTelemetry Assets [aws_vpcflow_otel]
         - AWS [aws]
         - Azure AI Foundry [azure_ai_foundry]
         - Azure App Service [azure_app_service]

.github/workflows/bump-elastic-stack-version.yml

@@ -25,7 +25,7 @@ jobs:
       - uses: actions/checkout@v5
 
       - name: Install Updatecli in the runner
-        uses: updatecli/updatecli-action@57aa8966d4d775cb1420b90c270ba97a4b5abe47 #v2.93.0
+        uses: updatecli/updatecli-action@719e3592d124cbf826da704cbe557e1221dd4bba #v2.94.0
 
       - name: Select diff action
         if: ${{ github.event_name == 'pull_request' }}

docs/extend/auto-install-content-packages.md

@@ -0,0 +1,37 @@
+---
+description: Enable automatic installation for your content package if data with a matching dataset is ingested in Elasticsearch.
+---
+
+# Enable automatic installation for content packages [auto-install-content-packages]
+
+As of version 9.2.0, {{kib}} can automatically install content packages when it detects matching data in {{es}}. This feature uses the `data_stream.dataset` attribute to identify relevant content and install assets such as dashboards and alerts without requiring user intervention.
+
+When data is ingested with a specific `data_stream.dataset` value, {{kib}} checks the {{package-registry}} for content packages that have at least one matching dataset defined in their `discovery.datasets` field. If there is a matching content package, {{kib}} automatically installs it.
+
+## Requirements [auto-install-content-packages-requirements]
+
+- {{kib}} version 9.2.0 or later
+- The `format_version` in the content package's `manifest.yml` must specify `3.4.1` or later.
+
+## Configuration [auto-install-content-packages-configuration]
+
+To enable automatic installation for your content package, add the `discovery.datasets` property to your package's `manifest.yml` file. This property should be defined as an array of objects, each with a `name` field specifying a dataset. For example:
+
+```yml
+# my_content_package/manifest.yml
+
+format_version: 3.4.1
+name: my_content_package
+version: 1.0.0
+type: content
+
+# ...
+
+discovery:
+  fields: []
+  datasets:
+    - name: my.dataset
+    - name: other.dataset
+```
+
+If you publish a content package with this configuration, {{kib}} will automatically install the package when data with `data_stream.dataset: "my.dataset"` or `data_stream.dataset: "other.dataset"` is ingested in {{es}}.

docs/extend/build-new-integration.md

@@ -15,6 +15,7 @@ Ready to monitor, ingest, and visualize something? Let’s get started. You’ll
 * [Edit ingest pipelines](/extend/edit-ingest-pipeline.md): Customize ingest pipelines to parse, enrich, and transform incoming data before it’s indexed.
 * [Edit field mappings](/extend/add-mapping.md): Specify and adjust field mappings to define the structure and types of your indexed data.
 * [Create and export dashboards](/extend/create-dashboards.md): Build {{kib}} dashboards and visualizations to explore and analyze the ingested data.
+* [Enable automatic installation for content packages](/extend/auto-install-content-packages.md): Enable automatic installation for your content package if data with a matching dataset is ingested in {{es}}.
 * [Testing and validation](/extend/testing-validation.md): Run tests and validate your integration to ensure it works as expected and meets quality standards.
 * [Finishing touches](/extend/finishing-touches.md): Finalize documentation, metadata, and package details to prepare your integration for release.
 * [Tips for building integrations](/extend/tips-for-building.md): Explore best practices and helpful advice to streamline your integration development process.

docs/extend/toc.yml

@@ -14,6 +14,7 @@ toc:
       - file: edit-ingest-pipeline.md
       - file: add-mapping.md
       - file: create-dashboards.md
+      - file: auto-install-content-packages.md
       - file: build-it.md
       - file: testing-validation.md
       - file: finishing-touches.md

packages/apache_otel/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.2.0"
+  changes:
+    - description: Add `discovery` field to support auto-install
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/15664
 - version: "0.1.1"
   changes:
     - description: Add `opentelemetry` category

packages/apache_otel/manifest.yml

@@ -1,7 +1,7 @@
 format_version: 3.5.0
 name: apache_otel
 title: "Apache OpenTelemetry Assets"
-version: 0.1.1
+version: 0.2.0
 source:
   license: "Elastic-2.0"
 description: "Apache status metrics from OpenTelemtry Collector"
@@ -12,9 +12,12 @@ categories:
   - opentelemetry
 conditions:
   kibana:
-    version: "^9.1.0"
+    version: "^9.2.0"
   elastic:
     subscription: "basic"
+discovery:
+  datasets:
+    - name: apachereceiver.otel
 screenshots:
   - src: /img/apache_otel_metrics.png
     title: Sample screenshot

packages/atlassian_bitbucket/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "2.6.0"
+  changes:
+    - description: Prevent updating fleet health status to degraded.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/15584
 - version: "2.5.0"
   changes:
     - description: Improve error reporting.