Merge branch 'main' into 1640-update-tutorial-ingest-logs-from-python-app

Author: vishaangelova

.github/workflows/label-community-issues.yml

@@ -12,11 +12,17 @@ jobs:
       contents: read
 
     steps:
+        # Adding this step for debug purposes
+        # If this works as expected, we can simplify this workflow
+        # and replace it with the `check-membership` step
+      - name: Check organization membership (test)
+        run: echo "${{ github.event.issue.author_association == 'MEMBER' }}"
       - name: Check organization membership
         id: check-membership
         uses: actions/github-script@v7
         with:
           github-token: ${{ secrets.ORG_MEMBER_READ_TOKEN }}
+          result-encoding: string
           script: |
             const issueAuthor = '${{ github.event.issue.user.login }}';
             const orgName = 'elastic';
@@ -55,4 +61,4 @@ jobs:
               labels: ['community']
             });
             
-            console.log(`Added "community" label to issue by ${issueAuthor}`);
+            console.log(`Added "community" label to issue by ${issueAuthor}`);

deploy-manage/cloud-organization/billing/security-billing-dimensions.md

@@ -70,8 +70,7 @@ Logs, events, alerts, and configuration data ingested into your security project
 
 For more details about {{elastic-sec}} serverless project rates and billable assets, refer to Cloud Protection in the [{{ecloud}} pricing table](https://cloud.elastic.co/cloud-pricing-table?productType=serverless&project=security).
 
-% Note: Commenting out this section until this is ready to be published. 
 
-% ## Elastic-managed LLM
+## Elastic Managed LLM
 
-% The default LLM enables you to leverage AI-powered search as a service without deploying a model in your serverless project. It's configured by default to use with the Security AI Assistant, Attack Discovery, and other applicable AI features as a part of your "Complete" tier subscription. Using the default LLM will use tokens and incur related token-based add-on billing for your serverless project.
+The default [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) enables you to leverage AI-powered search as a service without deploying a model in your serverless project. It's configured by default to use with the Security AI Assistant, Attack Discovery, and other applicable AI features as a part of your "Complete" tier subscription. Using the default LLM will use tokens and incur related token-based add-on billing for your serverless project.

deploy-manage/security/kibana-session-management.md

@@ -24,7 +24,7 @@ To manage user sessions programmatically, {{kib}} exposes [session management AP
 You can use `xpack.security.session.idleTimeout` to expire sessions after a period of inactivity. This and `xpack.security.session.lifespan` are both highly recommended. By default, sessions expire after 3 days of inactivity. To define another value for a sliding session expiration, set the  property in the [`kibana.yml`](/deploy-manage/stack-settings.md) configuration file. The idle timeout is formatted as a duration of `<count>[ms|s|m|h|d|w|M|Y]` (e.g. *20m*, *24h*, *7d*, *1w*). For example, set the idle timeout to expire sessions after 30 minutes of inactivity:
 
 ```yaml
-xpack.security.session.idleTimeout: "3d"
+xpack.security.session.idleTimeout: "30m"
 ```
 
 

explore-analyze/alerts-cases/watcher/action-foreach.md

@@ -45,3 +45,7 @@ PUT _watcher/watch/log_event_watch
 ```
 
 1. The logging statement will be executed for each of the returned search hits.
+
+::::{note}
+If you are running a [`script`](transform-script.md) {{watcher-transform}}, the transform needs to be included prior to the `actions` section to ensure the output is available to the `foreach` loop.
+::::

reference/fleet/install-elastic-agents.md

@@ -142,7 +142,7 @@ The disk requirements for {{agent}} vary by operating system and {{stack}} versi
 | Operating system | 8.13 | 8.14 | 8.15 | 8.18 | 9.0 |
 | --- | --- | --- | --- |
 | **Linux** | 1800 MB | 1018 MB | 1060 MB | 1.5 GB | 1.5 GB |
-| **macOS** | 1100 MB | 619 MB | 680 MB | 775 MB | 7755 MB |
+| **macOS** | 1100 MB | 619 MB | 680 MB | 775 MB | 775 MB |
 | **Windows** | 891 MB | 504 MB | 500 MB | 678 MB | 705 MB |
 
 During upgrades, double the disk space is required to store the new {{agent}} binary. After the upgrade completes, the original {{agent}} is removed from disk to free up the space.