Merge branch 'main' into kofi-high-cpu-troubleshooting

Author: shainaraskas

.github/CODEOWNERS

@@ -1,5 +1,65 @@
-/.github/ @elastic/doc-leads
-/.github/workflows/ @elastic/docs-engineering
+# Unless a later match takes precedence, someone on the docs team must review all PRs to this repo
+*                                           @elastic/docs
 
-/serverless/ @elastic/platform-docs
-/serverless/serverless-changelog.asciidoc @elastic/docs
+# Templates, workflows, and config
+/.github/                                   @elastic/doc-leads
+/.github/workflows/                         @elastic/docs-engineering
+/acrolinx/                                  @elastic/doc-leads
+
+# The docs
+/cloud-account/                             @elastic/admin-docs
+/deploy-manage/                             @elastic/admin-docs
+/explore-analyze/                           @elastic/core-docs @elastic/experience-docs 
+/extend/                                    @elastic/core-docs
+/get-started/                               @elastic/core-docs
+
+/manage-data/                               @elastic/admin-docs
+/manage-data/data-store/                    @elastic/admin-docs @elastic/developer-docs 
+/manage-data/ingest/                        @elastic/ingest-docs
+
+/reference/                                 @elastic/docs
+/reference/apm-agents/                      @elastic/ingest-docs
+/reference/data-analysis/                   @elastic/docs
+/reference/data-analysis/observability/     @elastic/experience-docs
+/reference/data-analysis/kibana/            @elastic/experience-docs 
+/reference/data-analysis/machine-learning/  @elastic/developer-docs
+/reference/data-analysis/observability/     @elastic/experience-docs
+/reference/elasticsearch/clients/           @elastic/developer-docs
+/reference/fleet/                           @elastic/ingest-docs
+/reference/glossary/                        @elastic/docs
+/reference/ingestion-tools/                 @elastic/ingest-docs
+/reference/observability/                   @elastic/experience-docs
+/reference/search/                          @elastic/developer-docs
+/reference/security/                        @elastic/experience-docs
+
+/release-notes/                             @elastic/docs
+
+/release-notes/apm-agents/                  @elastic/ingest-docs
+/release-notes/elastic-cloud-serverless/    @elastic/admin-docs
+/release-notes/elastic-observability/       @elastic/ski-docs
+/release-notes/elastic-security/            @elastic/ski-docs
+/release-notes/elasticsearch-clients/       @elastic/developer-docs
+/release-notes/fleet-elastic-agent/         @elastic/ingest-docs
+/release-notes/intro/                       @elastic/docs
+
+/solutions/                                 @elastic/experience-docs @elastic/developer-docs 
+/solutions/observability/                   @elastic/experience-docs
+/solutions/observability/get-started/       @elastic/ski-docs
+/solutions/search/                          @elastic/developer-docs
+/solutions/security/                        @elastic/experience-docs
+
+/troubleshoot/                              @elastic/docs
+/troubleshoot/deployments/                  @elastic/admin-docs
+/troubleshoot/elasticsearch/                @elastic/admin-docs
+/troubleshoot/ingest/                       @elastic/ingest-docs
+/troubleshoot/kibana/                       @elastic/admin-docs @elastic/experience-docs 
+/troubleshoot/monitoring/                   @elastic/admin-docs @elastic/experience-docs
+/troubleshoot/observability/                @elastic/ski-docs
+/troubleshoot/security/                     @elastic/ski-docs
+
+# Raw migrated files
+/raw-migrated-files/                        @elastic/docs
+
+# Legacy serverless docs
+/serverless/                                @elastic/admin-docs
+/serverless/serverless-changelog.asciidoc   @elastic/docs

.github/ISSUE_TEMPLATE/community-request.yaml renamed to .github/ISSUE_TEMPLATE/a-community-request.yaml

@@ -1,14 +1,14 @@
 name: "Community documentation request"
-description: Request a documentation change or enhancement.
-title: "[Request]: "
-labels: ["Request", "community"]
+description: An issue template for non-Elastic employees to request changes to the documentation.
+title: "[Community]: "
+labels: ["community"]
 body:
   - type: markdown
     attributes:
       value: |
-        Hi 👋. Thanks for taking the time to fill out this request!
-        This form will create an issue that Elastic's docs team will triage and prioritize.
-        You can also open a PR instead.
+        This issue template is for non-Elastic employees to request changes to the documentation. **If you are an Elastic employee, please use the internal issue template instead.**
+        
+        This form will create an issue that Elastic's docs team will triage and prioritize. You can also open a PR instead. Thanks for taking the time to fill out this request!
   - type: textarea
     id: link
     attributes:

.github/ISSUE_TEMPLATE/internal-request.yaml renamed to .github/ISSUE_TEMPLATE/b-internal-request.yaml

@@ -1,7 +1,6 @@
 name: "Internal documentation request (Elastic employees)"
-description: Request a documentation change or enhancement for any supported release.
-title: "[REQUEST]: "
-labels: ["request", "Team:Docs"]
+description: An issue template for Elastic employees to request improvements, additions, or changes to the documentation.
+title: "[Internal]: "
 body:
   - type: markdown
     attributes:
@@ -63,10 +62,21 @@ body:
         - 'N/A'
         - '8.17'
         - '8.18'
+        - '8.19'
         - '9.0'
+        - '9.1'
+        - '9.2'
       default: 0
     validations:
       required: true
+  - type: input
+    id: release-serverless
+    attributes:
+      label: Serverless release
+      description: When do you expect the feature to be promoted and available in the _**serverless production environment**_?
+      placeholder: The week of April 1, 2024
+    validations:
+      required: true    
   - type: dropdown
     id: collaboration
     attributes:

.github/ISSUE_TEMPLATE/api-feedback.yaml renamed to .github/ISSUE_TEMPLATE/c-api-feedback.yaml

@@ -1,7 +1,7 @@
 name: "API docs feedback"
 description: Tell us about your experience with Elastic API documentation.
-title: "[Feedback]: "
-labels: ["feedback", "community"]
+title: "[API]: "
+labels: ["api-feedback"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/d-ui-copy-request.yaml

@@ -0,0 +1,81 @@
+name: "UI copy request"
+description: Submit a UI copy-related request to the documentation team.
+title: "[UI copy]: "
+labels: "ui-copy"
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Hello! Use this form to submit a UI copy related request to Elastic's documentation team. You should also directly contact the specific writer or docs team that's responsibile for the applicable part of the product, especially for time-sensitive requests. 
+        > [!WARNING]  
+        > THIS IS A PUBLIC REPO. DO NOT INCLUDE SENSITIVE INFORMATION HERE.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Summarize your request here. What is the work and how can we help? Do we need to write new copy, or edit existing copy? Feel free to include screenshots.
+      placeholder: |
+        What: We're introducing new feature A. We need a writer to review the UI copy.
+        When: This feature will launch at the completion of project B.
+        Why: This feature will make X, Y, and Z easier for the user.
+    validations:
+      required: true
+  - type: textarea
+    id: related
+    attributes:
+      label: Related links / assets
+      description: Where can the documentation team learn more about this feature?
+      value: |
+        Please include each of the following, if applicable:
+        Figma link(s):
+        Github epic link(s):
+        Github issue link(s):
+        How to find the text in a production environment:
+        Testing environment information:
+        NOTE: To keep sensitive information such as credentials secure, do not include it in this form.
+    validations:
+      required: true
+  - type: dropdown
+    id: product-area
+    attributes:
+      label: Which product area does this mainly concern?
+      options:
+        - Cloud UI
+        - Search solution
+        - Observability solution
+        - Security solution
+        - Kibana Analytics (Discover, Dashboards...)
+        - Kibana Management
+        - Something else
+      default: 0
+    validations:
+      required: true
+  - type: textarea
+    id: collaborators
+    attributes:
+      label: Collaborators
+      description: Please include contact information for the responsible product manager, designer, and developer.
+      value: |
+        PM:
+        Designer: 
+        Developer:
+        Others (if applicable):
+    validations:
+      required: true
+  - type: textarea
+    id: timeline
+    attributes:
+      label: Timeline / deliverables
+      description: When would it be ideal for for us to complete the request? What deliverables do you need, and when? If applicable, how do the release timelines for this feature differ between serverless / stateful? 
+      placeholder: |
+        For example:
+
+        We need a final draft of the new UI copy no later than December 5, ideally by December 1. No differences between serverless/ESS. 
+
+        This is an urgent request, it would be great to have updated copy for A and B ASAP, since the original copy is already in production. No differences between serverless/ESS. 
+    validations:
+      required: true
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for submitting this issue! We'll be in contact shortly. 

.github/ISSUE_TEMPLATE/issue-report.yaml

@@ -1,14 +1,12 @@
-name: "Docs issue"
-description: Report documentation issues such as inaccuracies, broken links, typos, or missing information.
-title: "[Issue]: "
-labels: ["triage"]
+name: "Website issue"
+description: This issue template should only be used when navigating directly from elastic.co.
+title: "[Website]: "
+labels: ["source:web"]
 body:
   - type: markdown
     attributes:
       value: |
-        Hi 👋. Thanks for taking the time to fill out this issue report!
-        This form will create an issue that Elastic's docs team will triage and prioritize.
-        You can also open a PR instead.
+        Hi 👋. Thanks for taking the time to fill out this issue report! This form will create an issue that Elastic's docs team will triage and prioritize. You can also open a PR instead.
   - type: dropdown
     attributes:
       label: Type of issue

.github/workflows/add-new-team-label.yml

@@ -0,0 +1,18 @@
+name: "Label new issues with needs-team"
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  add-needs-triage-label:
+    name: Add `needs-team` label
+    runs-on: ubuntu-latest
+    steps:
+      - name: Add the needs-team label
+        uses: actions-ecosystem/action-add-labels@v1
+        with:
+          labels: |
+            needs-team
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/add-to-board.yml

@@ -0,0 +1,51 @@
+name: Triage & route issues
+
+on:
+  issues:
+    types: [labeled]
+
+permissions:
+  issues: write
+  contents: read
+
+jobs:
+  route:
+    runs-on: ubuntu-latest
+    if: |
+      github.event.label.name == 'team:Ingest' ||
+      github.event.label.name == 'team:Experience' ||
+      github.event.label.name == 'team:Admin' ||
+      github.event.label.name == 'team:Developer' ||
+      github.event.label.name == 'team:DocsEng' ||
+      github.event.label.name == 'team:Obs' ||
+      github.event.label.name == 'team:Platform' ||
+      github.event.label.name == 'team:Projects' ||
+      github.event.label.name == 'team:Search' ||
+      github.event.label.name == 'team:Security'
+    env:
+      PROJECT_ID_MAP: |
+        {
+          "team:Ingest":      "649",
+          "team:Experience":  "1034",
+          "team:Admin":       "1927",
+          "team:Developer":   "726",
+          "team:DocsEng":     "1625",
+          "team:Obs":         "649",
+          "team:Platform":    "1232",
+          "team:Projects":    "1415",
+          "team:Search":      "726",
+          "team:Security":    "1034"
+        }
+    steps:
+      - name: Remove needs-team label
+        uses: actions-ecosystem/action-remove-labels@v1
+        with:
+          labels: needs-team
+
+      - name: Add issue to the right project
+        uses: actions/add-to-project@244f685bbc3b7adfa8466e08b698b5577571133e
+        with:
+          project-url: https://github.com/orgs/elastic/projects/${{ fromJson(env.PROJECT_ID_MAP)[github.event.label.name] }}
+          github-token: ${{ secrets.ADD_TO_BOARD_TOKEN }}
+          labeled: ${{ github.event.label.name }}
+          label-operator: OR

.github/workflows/docs-build.yml

@@ -16,4 +16,4 @@ jobs:
       deployments: write
       id-token: write
       contents: read
-      pull-requests: read
+      pull-requests: write

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

@@ -0,0 +1,64 @@
+name: Label Community Issues
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  label-community-issues:
+    runs-on: ubuntu-latest
+    permissions:
+      issues: write
+      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';
+            
+            try {
+              await github.rest.orgs.getMembershipForUser({
+                org: orgName,
+                username: issueAuthor
+              });
+              
+              console.log(`${issueAuthor} is a member of ${orgName} organization`);
+              return 'member';
+              
+            } catch (error) {
+              if (error.status === 404) {
+                console.log(`${issueAuthor} is not a member of ${orgName} organization`);
+                return 'non-member';
+              } else {
+                console.log('Error checking organization membership:', error);
+                return 'error';
+              }
+            }
+
+      - name: Add community label
+        if: steps.check-membership.outputs.result == 'non-member'
+        uses: actions/github-script@v7
+        with:
+          github-token: ${{ secrets.GITHUB_TOKEN }}
+          script: |
+            const issueAuthor = '${{ github.event.issue.user.login }}';
+            
+            await github.rest.issues.addLabels({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              issue_number: context.issue.number,
+              labels: ['community']
+            });
+            
+            console.log(`Added "community" label to issue by ${issueAuthor}`);