Merge branch 'main' into chart_expression-xy_addTimeMarker

.buildkite/ftr_configs.yml

@@ -32,6 +32,7 @@ disabled:
   - x-pack/test/security_solution_cypress/upgrade_config.ts
   - x-pack/test/security_solution_cypress/visual_config.ts
   - x-pack/test/functional_enterprise_search/with_host_configured.config.ts
+  - x-pack/plugins/apm/ftr_e2e/ftr_config_open.ts
   - x-pack/plugins/apm/ftr_e2e/ftr_config_run.ts
   - x-pack/plugins/apm/ftr_e2e/ftr_config.ts
 

.buildkite/pipelines/artifacts.yml

@@ -56,6 +56,7 @@ steps:
     agents:
       queue: n2-2
     timeout_in_minutes: 30
+    if: "build.env('RELEASE_BUILD') == null || build.env('RELEASE_BUILD') == '' || build.env('RELEASE_BUILD') == 'false'"
     retry:
       automatic:
         - exit_status: '*'

.buildkite/scripts/lifecycle/post_command.sh

@@ -26,6 +26,7 @@ if [[ "$IS_TEST_EXECUTION_STEP" == "true" ]]; then
   buildkite-agent artifact upload 'x-pack/test/functional/apps/reporting/reports/session/*.pdf'
   buildkite-agent artifact upload 'x-pack/test/functional/failure_debug/html/*.html'
   buildkite-agent artifact upload '.es/**/*.hprof'
+  buildkite-agent artifact upload 'data/es_debug_*.tar.gz'
 
   echo "--- Run Failed Test Reporter"
   node scripts/report_failed_tests --build-url="${BUILDKITE_BUILD_URL}#${BUILDKITE_JOB_ID}" 'target/junit/**/*.xml'

dev_docs/operations/ci_stats.mdx

@@ -0,0 +1,15 @@
+---
+id: kibDevDocsOpsCiStats
+slug: /kibana-dev-docs/ops/ci-stats
+title: "Kibana CI Stats"
+description: A service that we run to track little bits of data about CI runs.
+tags: ['kibana', 'dev', 'contributor', 'operations', 'ci']
+---
+
+Kibana CI Stats (sometimes written "ci-stats") is a service run at https://ci-stats.kibana.dev. This service runs a series of APIs in front of an Elasticsearch Cluster which allows us to record data about each run of CI. This data includes metrics, times, test results, and more. We are working on storing performance data in there too, and eventually will spend time to write good UIs on top of this data.
+
+The service implementation is available at https://github.com/elastic/kibana-ci-stats/ (private because there doesn't seem to be a good reason to make it public).
+
+The service is run on Google Cloud Run, which allows us to build a container, push it to GCR, define a memory limit, vCPU count, and concurrent request limit per container, and Google will automatically scale the container for us. It works pretty well and hides a lot of the complexity of running the service. The repo uses Buildkite CI to build and deploy the container when pushing to the main branch. All changes to the main branch must come from PRs, but at this time we don't require review for PRs.
+
+The website at https://ci-stats.kibana.dev uses EUI and Elastic Charts, and currently has users powered by Github OAuth. When someone authenticates with ci-stats they are first redirected to Github for authentication, then their membership in the Elastic org is checked. Users in the Elastic org will be able to do things that other users can't, like [trigger flaky test runner jobs](https://ci-stats.kibana.dev/trigger_flaky_test_runner).

dev_docs/operations/operations_landing.mdx

@@ -0,0 +1,47 @@
+---
+id: kibDevDocsOpsOverview
+slug: /kibana-dev-docs/ops
+title: Kibana Operations
+description: Links to all the documentation maintained by the Kibana Operations team
+tags: ['kibana', 'dev', 'contributor', 'operations']
+layout: landing
+---
+
+<DocLandingHero
+  title='Welcome to the ops docs!'
+  description="👋 Here you will find documentation about all the things the Kibana Operations team manages. Feel free to look around and ask questions!"
+/>
+
+<DocRelatedArticles
+  sectionTitle='CI'
+  items={[
+    { pageId: "kibDevDocsOpsCiStats" },
+  ]}
+/>
+
+<DocRelatedArticles
+  sectionTitle='Build tooling'
+  items={[
+    { pageId: "kibDevDocsOpsOptimizer" },
+    { pageId: "kibDevDocsOpsBabelPreset" },
+    { pageId: "kibDevDocsOpsTypeSummarizer" },
+  ]}
+/>
+
+<DocRelatedArticles
+  sectionTitle='Linting & Validation'
+  items={[
+    { pageId: "kibDevDocsOpsEslintConfig" },
+    { pageId: "kibDevDocsOpsEslintWithTypes" },
+    { pageId: "kibDevDocsOpsEslintPluginImports" },
+  ]}
+/>
+
+<DocRelatedArticles
+  sectionTitle='Utilities'
+  items={[
+    { pageId: "kibDevDocsToolingLog" },
+    { pageId: "kibDevDocsOpsJestSerializers"},
+    { pageId: "kibDevDocsOpsExpect" },
+  ]}
+/>

docs/apm/services.asciidoc

@@ -12,3 +12,41 @@ and requires anomaly detection to be enabled.
 
 [role="screenshot"]
 image::apm/images/apm-services-overview.png[Example view of services table the APM app in Kibana]
+
+[float]
+[[service-groups]]
+==== Service groups
+
+preview::[]
+
+Group services together to build meaningful views that remove noise and simplify investigations across services.
+Service groups are {kib} space-specific and available for any users with appropriate access.
+
+[role="screenshot"]
+image::apm/images/apm-service-group.png[Example view of service group in the APM app in Kibana]
+
+To enable Service groups, open {kib} and navigate to **Stack Management** > **Advanced Settings** > **Observability**,
+and enable the **Service groups feature**.
+
+To create a service group, navigate to **Observability** > **APM** > **Services** and select **Create group**.
+Specify a name, color, and description.
+Then, using the <<kuery-query, Kibana Query Language (KQL)>>, specify a query to select services for the group.
+Services that match the query within the last 24 hours will be assigned to the group.
+
+[NOTE]
+====
+Once a service group has been saved, this list of services within it is static.
+If a newly added service matches the KQL query, it will not be automatically added to the service group.
+Similarly, if a service stops matching the KQL query, it will not be removed from the group.
+
+To update the list of services within a group,
+edit the service group, click **Refresh** next to the KQL query, and click **Save group**.
+====
+
+**Examples**
+
+Not sure where to get started? Here are some sample queries you can build from:
+
+* Group services by environment--in this example, "production": `service.environment : "production"`
+* Group services by name--this example groups those that end in "beat": `service.name : *beat` (matches services named "Auditbeat", "Heartbeat", "Filebeat", etc.)
+* Group services with a high transaction duration in the last 24 hours: `transaction.duration.us >= 50000000`