From 8413074f0fdcc3a441c2c2406e5543f171d52af5 Mon Sep 17 00:00:00 2001 From: dedemorton Date: Tue, 12 Nov 2024 18:29:06 -0800 Subject: [PATCH 1/2] Remove technical preview from serverless docs --- docs/en/serverless/ai-assistant/ai-assistant.asciidoc | 2 -- docs/en/serverless/aiops/aiops-analyze-spikes.asciidoc | 2 -- docs/en/serverless/aiops/aiops-detect-anomalies.asciidoc | 2 -- docs/en/serverless/aiops/aiops-detect-change-points.asciidoc | 2 -- docs/en/serverless/aiops/aiops-forecast-anomaly.asciidoc | 2 -- .../serverless/aiops/aiops-tune-anomaly-detection-job.asciidoc | 2 -- docs/en/serverless/aiops/aiops.asciidoc | 2 -- docs/en/serverless/alerting/aggregation-options.asciidoc | 2 -- .../serverless/alerting/aiops-generate-anomaly-alerts.asciidoc | 2 -- docs/en/serverless/alerting/alerting.asciidoc | 2 -- docs/en/serverless/alerting/create-anomaly-alert-rule.asciidoc | 2 -- .../alerting/create-custom-threshold-alert-rule.asciidoc | 2 -- .../alerting/create-elasticsearch-query-alert-rule.asciidoc | 2 -- .../alerting/create-error-count-threshold-alert-rule.asciidoc | 2 -- ...create-failed-transaction-rate-threshold-alert-rule.asciidoc | 2 -- .../alerting/create-inventory-threshold-alert-rule.asciidoc | 2 -- .../alerting/create-latency-threshold-alert-rule.asciidoc | 2 -- docs/en/serverless/alerting/create-manage-rules.asciidoc | 2 -- .../alerting/create-slo-burn-rate-alert-rule.asciidoc | 2 -- docs/en/serverless/alerting/rate-aggregation.asciidoc | 2 -- .../serverless/alerting/triage-slo-burn-rate-breaches.asciidoc | 2 -- docs/en/serverless/alerting/view-alerts.asciidoc | 2 -- .../apm-agents/apm-agents-aws-lambda-functions.asciidoc | 2 -- .../apm-agents/apm-agents-elastic-apm-agents.asciidoc | 2 -- .../apm-agents-opentelemetry-collect-metrics.asciidoc | 2 -- .../apm-agents/apm-agents-opentelemetry-limitations.asciidoc | 2 -- ...m-agents-opentelemetry-opentelemetry-native-support.asciidoc | 2 -- .../apm-agents-opentelemetry-resource-attributes.asciidoc | 2 -- docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc | 2 -- docs/en/serverless/apm/apm-compress-spans.asciidoc | 2 -- docs/en/serverless/apm/apm-create-custom-links.asciidoc | 2 -- docs/en/serverless/apm/apm-data-types.asciidoc | 2 -- docs/en/serverless/apm/apm-distributed-tracing.asciidoc | 2 -- docs/en/serverless/apm/apm-filter-your-data.asciidoc | 2 -- ...m-find-transaction-latency-and-failure-correlations.asciidoc | 2 -- docs/en/serverless/apm/apm-get-started.asciidoc | 2 -- .../serverless/apm/apm-integrate-with-machine-learning.asciidoc | 2 -- docs/en/serverless/apm/apm-keep-data-secure.asciidoc | 2 -- docs/en/serverless/apm/apm-kibana-settings.asciidoc | 2 -- docs/en/serverless/apm/apm-observe-lambda-functions.asciidoc | 2 -- docs/en/serverless/apm/apm-query-your-data.asciidoc | 2 -- docs/en/serverless/apm/apm-reduce-your-data-usage.asciidoc | 2 -- docs/en/serverless/apm/apm-reference.asciidoc | 2 -- docs/en/serverless/apm/apm-send-traces-to-elastic.asciidoc | 2 -- docs/en/serverless/apm/apm-server-api.asciidoc | 2 -- docs/en/serverless/apm/apm-stacktrace-collection.asciidoc | 2 -- .../apm/apm-track-deployments-with-annotations.asciidoc | 2 -- docs/en/serverless/apm/apm-transaction-sampling.asciidoc | 2 -- docs/en/serverless/apm/apm-troubleshooting.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-dependencies.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-errors.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-infrastructure.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-logs.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-metrics.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-overview.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-service-map.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-service-overview.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-services.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-traces.asciidoc | 2 -- docs/en/serverless/apm/apm-ui-transactions.asciidoc | 2 -- docs/en/serverless/apm/apm-view-and-analyze-traces.asciidoc | 2 -- docs/en/serverless/apm/apm.asciidoc | 2 -- docs/en/serverless/cases/cases.asciidoc | 2 -- docs/en/serverless/cases/create-manage-cases.asciidoc | 2 -- docs/en/serverless/cases/manage-cases-settings.asciidoc | 2 -- .../dashboards/dashboards-and-visualizations.asciidoc | 2 -- docs/en/serverless/elastic-entity-model.asciidoc | 2 -- docs/en/serverless/infra-monitoring/analyze-hosts.asciidoc | 2 -- docs/en/serverless/infra-monitoring/aws-metrics.asciidoc | 2 -- .../infra-monitoring/configure-infra-settings.asciidoc | 2 -- docs/en/serverless/infra-monitoring/container-metrics.asciidoc | 2 -- .../infra-monitoring/detect-metric-anomalies.asciidoc | 2 -- .../infra-monitoring/get-started-with-metrics.asciidoc | 2 -- .../infra-monitoring/handle-no-results-found-message.asciidoc | 2 -- docs/en/serverless/infra-monitoring/host-metrics.asciidoc | 2 -- docs/en/serverless/infra-monitoring/infra-monitoring.asciidoc | 2 -- .../serverless/infra-monitoring/kubernetes-pod-metrics.asciidoc | 2 -- docs/en/serverless/infra-monitoring/metrics-app-fields.asciidoc | 2 -- docs/en/serverless/infra-monitoring/metrics-reference.asciidoc | 2 -- .../serverless/infra-monitoring/troubleshooting-infra.asciidoc | 2 -- .../infra-monitoring/view-infrastructure-metrics.asciidoc | 2 -- docs/en/serverless/inventory.asciidoc | 2 -- docs/en/serverless/logging/correlate-application-logs.asciidoc | 2 -- docs/en/serverless/logging/ecs-application-logs.asciidoc | 2 -- docs/en/serverless/logging/filter-and-aggregate-logs.asciidoc | 2 -- docs/en/serverless/logging/get-started-with-logs.asciidoc | 2 -- docs/en/serverless/logging/log-monitoring.asciidoc | 2 -- docs/en/serverless/logging/parse-log-data.asciidoc | 2 -- docs/en/serverless/logging/plaintext-application-logs.asciidoc | 2 -- docs/en/serverless/logging/run-log-pattern-analysis.asciidoc | 2 -- docs/en/serverless/logging/send-application-logs.asciidoc | 2 -- docs/en/serverless/logging/stream-log-files.asciidoc | 2 -- docs/en/serverless/logging/troubleshoot-logs.asciidoc | 2 -- docs/en/serverless/logging/view-and-monitor-logs.asciidoc | 2 -- docs/en/serverless/observability-overview.asciidoc | 2 -- docs/en/serverless/projects/billing.asciidoc | 2 -- .../projects/create-an-observability-project.asciidoc | 2 -- docs/en/serverless/quickstarts/k8s-logs-metrics.asciidoc | 2 -- .../quickstarts/monitor-hosts-with-elastic-agent.asciidoc | 2 -- docs/en/serverless/slos/create-an-slo.asciidoc | 2 -- docs/en/serverless/slos/slos.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-analyze.asciidoc | 2 -- .../serverless/synthetics/synthetics-command-reference.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-configuration.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-create-test.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-feature-roles.asciidoc | 2 -- .../synthetics/synthetics-get-started-project.asciidoc | 2 -- .../en/serverless/synthetics/synthetics-get-started-ui.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-get-started.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-intro.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-journeys.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-lightweight.asciidoc | 2 -- .../serverless/synthetics/synthetics-manage-monitors.asciidoc | 2 -- .../serverless/synthetics/synthetics-manage-retention.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-mfa.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-monitor-use.asciidoc | 2 -- .../en/serverless/synthetics/synthetics-params-secrets.asciidoc | 2 -- .../serverless/synthetics/synthetics-private-location.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-recorder.asciidoc | 2 -- .../synthetics/synthetics-scale-and-architect.asciidoc | 2 -- .../synthetics/synthetics-security-encryption.asciidoc | 2 -- docs/en/serverless/synthetics/synthetics-settings.asciidoc | 2 -- .../serverless/synthetics/synthetics-troubleshooting.asciidoc | 2 -- docs/en/serverless/technical-preview-limitations.asciidoc | 2 -- docs/en/serverless/what-is-observability-serverless.asciidoc | 2 -- 126 files changed, 252 deletions(-) diff --git a/docs/en/serverless/ai-assistant/ai-assistant.asciidoc b/docs/en/serverless/ai-assistant/ai-assistant.asciidoc index 06142a50e7..09c44f1762 100644 --- a/docs/en/serverless/ai-assistant/ai-assistant.asciidoc +++ b/docs/en/serverless/ai-assistant/ai-assistant.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - The AI Assistant uses generative AI to provide: * **Chat**: Have conversations with the AI Assistant. Chat uses function calling to request, analyze, and visualize your data. diff --git a/docs/en/serverless/aiops/aiops-analyze-spikes.asciidoc b/docs/en/serverless/aiops/aiops-analyze-spikes.asciidoc index 3673f62b34..7496a75bee 100644 --- a/docs/en/serverless/aiops/aiops-analyze-spikes.asciidoc +++ b/docs/en/serverless/aiops/aiops-analyze-spikes.asciidoc @@ -4,8 +4,6 @@ // :description: Find and investigate the causes of unusual spikes or drops in log rates. // :keywords: serverless, observability, how-to -preview:[] - // {obs-serverless} provides built-in log rate analysis capabilities, diff --git a/docs/en/serverless/aiops/aiops-detect-anomalies.asciidoc b/docs/en/serverless/aiops/aiops-detect-anomalies.asciidoc index 37211e6686..c87a36cf8c 100644 --- a/docs/en/serverless/aiops/aiops-detect-anomalies.asciidoc +++ b/docs/en/serverless/aiops/aiops-detect-anomalies.asciidoc @@ -4,8 +4,6 @@ // :description: Detect anomalies by comparing real-time and historical data from different sources to look for unusual, problematic patterns. // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create, run, and view {anomaly-job}s include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/aiops/aiops-detect-change-points.asciidoc b/docs/en/serverless/aiops/aiops-detect-change-points.asciidoc index 67d1547931..fbdce3cc33 100644 --- a/docs/en/serverless/aiops/aiops-detect-change-points.asciidoc +++ b/docs/en/serverless/aiops/aiops-detect-change-points.asciidoc @@ -4,8 +4,6 @@ // :description: Detect distribution changes, trend changes, and other statistically significant change points in a metric of your time series data. // :keywords: serverless, observability, how-to -preview:[] - // The change point detection feature in {obs-serverless} detects distribution changes, diff --git a/docs/en/serverless/aiops/aiops-forecast-anomaly.asciidoc b/docs/en/serverless/aiops/aiops-forecast-anomaly.asciidoc index 274d1979b0..e7f0f2dad6 100644 --- a/docs/en/serverless/aiops/aiops-forecast-anomaly.asciidoc +++ b/docs/en/serverless/aiops/aiops-forecast-anomaly.asciidoc @@ -4,8 +4,6 @@ // :description: Predict future behavior of your data by creating a forecast for an anomaly detection job. // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create a forecast for an {anomaly-job} include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/aiops/aiops-tune-anomaly-detection-job.asciidoc b/docs/en/serverless/aiops/aiops-tune-anomaly-detection-job.asciidoc index d21bf82521..a1d2048d33 100644 --- a/docs/en/serverless/aiops/aiops-tune-anomaly-detection-job.asciidoc +++ b/docs/en/serverless/aiops/aiops-tune-anomaly-detection-job.asciidoc @@ -4,8 +4,6 @@ // :description: Tune your job by creating calendars, adding job rules, and defining custom URLs. // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create calendars, add job rules, and define custom URLs include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/aiops/aiops.asciidoc b/docs/en/serverless/aiops/aiops.asciidoc index a211dd1a4e..1a3f86c0c2 100644 --- a/docs/en/serverless/aiops/aiops.asciidoc +++ b/docs/en/serverless/aiops/aiops.asciidoc @@ -4,8 +4,6 @@ // :description: Automate anomaly detection and accelerate root cause analysis with AIOps. // :keywords: serverless, observability, overview -preview:[] - The AIOps capabilities available in {obs-serverless} enable you to consume and process large observability data sets at scale, reducing the time and effort required to detect, understand, investigate, and resolve incidents. Built on predictive analytics and {ml}, our AIOps capabilities require no prior experience with {ml}. DevOps engineers, SREs, and security analysts can get started right away using these AIOps features with little or no advanced configuration: diff --git a/docs/en/serverless/alerting/aggregation-options.asciidoc b/docs/en/serverless/alerting/aggregation-options.asciidoc index 74f8952e2b..27e133dab5 100644 --- a/docs/en/serverless/alerting/aggregation-options.asciidoc +++ b/docs/en/serverless/alerting/aggregation-options.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about aggregations available in alerting rules. // :keywords: serverless, observability, reference -preview:[] - Aggregations summarize your data to make it easier to analyze. In some alerting rules, you can specify aggregations to gather data for the rule. diff --git a/docs/en/serverless/alerting/aiops-generate-anomaly-alerts.asciidoc b/docs/en/serverless/alerting/aiops-generate-anomaly-alerts.asciidoc index 82b755e2ef..046506f87b 100644 --- a/docs/en/serverless/alerting/aiops-generate-anomaly-alerts.asciidoc +++ b/docs/en/serverless/alerting/aiops-generate-anomaly-alerts.asciidoc @@ -8,8 +8,6 @@ Anomaly detection ++++ -preview:[] - :role: Editor :goal: create anomaly detection rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/alerting.asciidoc b/docs/en/serverless/alerting/alerting.asciidoc index 3aec064467..58c6a87224 100644 --- a/docs/en/serverless/alerting/alerting.asciidoc +++ b/docs/en/serverless/alerting/alerting.asciidoc @@ -4,8 +4,6 @@ // :description: Get alerts based on rules you define for detecting complex conditions in your applications and services. // :keywords: serverless, observability, overview, alerting -preview:[] - Alerting enables you to define _rules_, which detect complex conditions within different apps and trigger actions when those conditions are met. Alerting provides a set of built-in connectors and rules for you to use. This page describes all of these elements and how they operate together. [discrete] diff --git a/docs/en/serverless/alerting/create-anomaly-alert-rule.asciidoc b/docs/en/serverless/alerting/create-anomaly-alert-rule.asciidoc index 2008ae5cf2..0109646081 100644 --- a/docs/en/serverless/alerting/create-anomaly-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-anomaly-alert-rule.asciidoc @@ -8,8 +8,6 @@ APM anomaly ++++ -preview:[] - :role: Editor :goal: create anomaly rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-custom-threshold-alert-rule.asciidoc b/docs/en/serverless/alerting/create-custom-threshold-alert-rule.asciidoc index 94ca37d995..536a2d3b9a 100644 --- a/docs/en/serverless/alerting/create-custom-threshold-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-custom-threshold-alert-rule.asciidoc @@ -8,8 +8,6 @@ Custom threshold ++++ -preview:[] - :role: Editor :goal: create a custom threshold rule include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc b/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc index fe4011b2c8..7f6316a13a 100644 --- a/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc @@ -8,8 +8,6 @@ Elasticsearch query ++++ -preview:[] - :role: Editor :goal: create Elasticsearch query rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-error-count-threshold-alert-rule.asciidoc b/docs/en/serverless/alerting/create-error-count-threshold-alert-rule.asciidoc index 5ca3da2198..f223061923 100644 --- a/docs/en/serverless/alerting/create-error-count-threshold-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-error-count-threshold-alert-rule.asciidoc @@ -8,8 +8,6 @@ Error count threshold ++++ -preview:[] - :role: Editor :goal: create error count threshold rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-failed-transaction-rate-threshold-alert-rule.asciidoc b/docs/en/serverless/alerting/create-failed-transaction-rate-threshold-alert-rule.asciidoc index 187f6fbb12..d0fa0c6fbd 100644 --- a/docs/en/serverless/alerting/create-failed-transaction-rate-threshold-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-failed-transaction-rate-threshold-alert-rule.asciidoc @@ -8,8 +8,6 @@ Failed transaction rate threshold ++++ -preview:[] - :role: Editor :goal: create failed transaction rate threshold rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-inventory-threshold-alert-rule.asciidoc b/docs/en/serverless/alerting/create-inventory-threshold-alert-rule.asciidoc index 9db7772283..409e3d7c7d 100644 --- a/docs/en/serverless/alerting/create-inventory-threshold-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-inventory-threshold-alert-rule.asciidoc @@ -8,8 +8,6 @@ Inventory ++++ -preview:[] - :role: Editor :goal: create inventory threshold rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-latency-threshold-alert-rule.asciidoc b/docs/en/serverless/alerting/create-latency-threshold-alert-rule.asciidoc index 49eb9292cf..f4a7b433fc 100644 --- a/docs/en/serverless/alerting/create-latency-threshold-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-latency-threshold-alert-rule.asciidoc @@ -8,8 +8,6 @@ Latency threshold ++++ -preview:[] - :role: Editor :goal: create latency threshold rules include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-manage-rules.asciidoc b/docs/en/serverless/alerting/create-manage-rules.asciidoc index 2c9bfbefde..2b07333ad0 100644 --- a/docs/en/serverless/alerting/create-manage-rules.asciidoc +++ b/docs/en/serverless/alerting/create-manage-rules.asciidoc @@ -4,8 +4,6 @@ // :description: Create and manage rules for alerting when conditions are met. // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create and manage rules for alerting include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/create-slo-burn-rate-alert-rule.asciidoc b/docs/en/serverless/alerting/create-slo-burn-rate-alert-rule.asciidoc index 648c77e743..db88467bd6 100644 --- a/docs/en/serverless/alerting/create-slo-burn-rate-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-slo-burn-rate-alert-rule.asciidoc @@ -8,8 +8,6 @@ SLO burn rate ++++ -preview:[] - :role: Editor :goal: create rules for alerting include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/alerting/rate-aggregation.asciidoc b/docs/en/serverless/alerting/rate-aggregation.asciidoc index 701e592826..d2e8c6329d 100644 --- a/docs/en/serverless/alerting/rate-aggregation.asciidoc +++ b/docs/en/serverless/alerting/rate-aggregation.asciidoc @@ -4,8 +4,6 @@ // :description: Analyze the rate at which a specific field changes over time. // :keywords: serverless, observability, reference -preview:[] - You can use a rate aggregation to analyze the rate at which a specific field changes over time. This type of aggregation is useful when you want to analyze fields like counters. diff --git a/docs/en/serverless/alerting/triage-slo-burn-rate-breaches.asciidoc b/docs/en/serverless/alerting/triage-slo-burn-rate-breaches.asciidoc index 1ae5f51f82..a800be4581 100644 --- a/docs/en/serverless/alerting/triage-slo-burn-rate-breaches.asciidoc +++ b/docs/en/serverless/alerting/triage-slo-burn-rate-breaches.asciidoc @@ -8,8 +8,6 @@ SLO burn rate breaches ++++ -preview:[] - SLO burn rate breaches occur when the percentage of bad events over a specified time period exceeds the threshold set in your <>. When this happens, you are at risk of exhausting your error budget and violating your SLO. diff --git a/docs/en/serverless/alerting/view-alerts.asciidoc b/docs/en/serverless/alerting/view-alerts.asciidoc index abefb3d921..fa784abb71 100644 --- a/docs/en/serverless/alerting/view-alerts.asciidoc +++ b/docs/en/serverless/alerting/view-alerts.asciidoc @@ -4,8 +4,6 @@ // :description: Track and manage alerts for your services and applications. // :keywords: serverless, observability, how-to, alerting -preview:[] - :role: Editor :goal: perform this task include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm-agents/apm-agents-aws-lambda-functions.asciidoc b/docs/en/serverless/apm-agents/apm-agents-aws-lambda-functions.asciidoc index 8c90ea2ff9..2d8e5cf8dd 100644 --- a/docs/en/serverless/apm-agents/apm-agents-aws-lambda-functions.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-aws-lambda-functions.asciidoc @@ -4,8 +4,6 @@ // :description: Use Elastic APM to monitor your AWS Lambda functions. // :keywords: serverless, observability, overview -preview:[] - Elastic APM lets you monitor your AWS Lambda functions. The natural integration of <> into your AWS Lambda functions provides insights into each function's execution and runtime behavior as well as its relationships and dependencies to other services. diff --git a/docs/en/serverless/apm-agents/apm-agents-elastic-apm-agents.asciidoc b/docs/en/serverless/apm-agents/apm-agents-elastic-apm-agents.asciidoc index 353f0ecf51..b146b2f798 100644 --- a/docs/en/serverless/apm-agents/apm-agents-elastic-apm-agents.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-elastic-apm-agents.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - :role: Admin :goal: use APM agents include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-collect-metrics.asciidoc b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-collect-metrics.asciidoc index fac986b2fb..542725c43d 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-collect-metrics.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-collect-metrics.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - [IMPORTANT] ==== When collecting metrics, please note that the https://www.javadoc.io/doc/io.opentelemetry/opentelemetry-api/latest/io/opentelemetry/api/metrics/DoubleValueRecorder.html[`DoubleValueRecorder`] diff --git a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-limitations.asciidoc b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-limitations.asciidoc index eefeea5138..6d0003e4b0 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-limitations.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-limitations.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - [discrete] [[observability-apm-agents-opentelemetry-limitations-opentelemetry-traces]] == OpenTelemetry traces diff --git a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-opentelemetry-native-support.asciidoc b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-opentelemetry-native-support.asciidoc index eb00ee1e3e..064c426d10 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-opentelemetry-native-support.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-opentelemetry-native-support.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - [NOTE] ==== This is one of several approaches you can use to integrate Elastic with OpenTelemetry. diff --git a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-resource-attributes.asciidoc b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-resource-attributes.asciidoc index 5b4d3fe918..2f19b0fef9 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-resource-attributes.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-resource-attributes.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - A resource attribute is a key/value pair containing information about the entity producing telemetry. Resource attributes are mapped to Elastic Common Schema (ECS) fields like `service.*`, `cloud.*`, `process.*`, etc. These fields describe the service and the environment that the service runs in. diff --git a/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc b/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc index 2a297d6bfe..3bc596c183 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - [NOTE] ==== For a complete overview of using OpenTelemetry with Elastic, explore https://github.com/elastic/opentelemetry[Elastic Distributions of OpenTelemetry]. diff --git a/docs/en/serverless/apm/apm-compress-spans.asciidoc b/docs/en/serverless/apm/apm-compress-spans.asciidoc index 427cc99a99..331c08cb3e 100644 --- a/docs/en/serverless/apm/apm-compress-spans.asciidoc +++ b/docs/en/serverless/apm/apm-compress-spans.asciidoc @@ -4,8 +4,6 @@ // :description: Compress similar or identical spans to reduce storage overhead, processing power needed, and clutter in the Applications UI. // :keywords: serverless, observability, how-to -preview:[] - In some cases, APM agents may collect large amounts of very similar or identical spans in a transaction. For example, this can happen if spans are captured inside a loop or in unoptimized SQL queries that use multiple queries instead of joins to fetch related data. diff --git a/docs/en/serverless/apm/apm-create-custom-links.asciidoc b/docs/en/serverless/apm/apm-create-custom-links.asciidoc index ce5355e238..61398f59c0 100644 --- a/docs/en/serverless/apm/apm-create-custom-links.asciidoc +++ b/docs/en/serverless/apm/apm-create-custom-links.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create and manage custom links include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm/apm-data-types.asciidoc b/docs/en/serverless/apm/apm-data-types.asciidoc index 177fde831f..8dace1337b 100644 --- a/docs/en/serverless/apm/apm-data-types.asciidoc +++ b/docs/en/serverless/apm/apm-data-types.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about the various APM data types. // :keywords: serverless, observability, overview -preview:[] - Elastic APM agents capture different types of information from within their instrumented applications. These are known as events, and can be spans, transactions, errors, or metrics: diff --git a/docs/en/serverless/apm/apm-distributed-tracing.asciidoc b/docs/en/serverless/apm/apm-distributed-tracing.asciidoc index 1ee167e3ab..653a0acc05 100644 --- a/docs/en/serverless/apm/apm-distributed-tracing.asciidoc +++ b/docs/en/serverless/apm/apm-distributed-tracing.asciidoc @@ -4,8 +4,6 @@ // :description: Understand how a single request that travels through multiple services impacts your application. // :keywords: serverless, observability, how-to -preview:[] - A `trace` is a group of <> and <> with a common root. Each `trace` tracks the entirety of a single request. When a `trace` travels through multiple services, as is common in a microservice architecture, diff --git a/docs/en/serverless/apm/apm-filter-your-data.asciidoc b/docs/en/serverless/apm/apm-filter-your-data.asciidoc index fee20316d0..5ddfd1f200 100644 --- a/docs/en/serverless/apm/apm-filter-your-data.asciidoc +++ b/docs/en/serverless/apm/apm-filter-your-data.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - Global filters are ways you can filter your APM data based on a specific time range or environment. When viewing a specific service, the filter persists as you move between tabs. diff --git a/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc b/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc index 2c2591e96b..5519c03cf7 100644 --- a/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc +++ b/docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - Correlations surface attributes of your data that are potentially correlated with high-latency or erroneous transactions. For example, if you are a site reliability engineer who is responsible for keeping production systems up and diff --git a/docs/en/serverless/apm/apm-get-started.asciidoc b/docs/en/serverless/apm/apm-get-started.asciidoc index 2b3b9856d8..41e3f083ba 100644 --- a/docs/en/serverless/apm/apm-get-started.asciidoc +++ b/docs/en/serverless/apm/apm-get-started.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to collect Application Performance Monitoring (APM) data and visualize it in real time. // :keywords: serverless, observability, how-to -preview:[] - :role: Admin :goal: send APM data to Elastic include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm/apm-integrate-with-machine-learning.asciidoc b/docs/en/serverless/apm/apm-integrate-with-machine-learning.asciidoc index 9310f744e7..a9b96b2bd4 100644 --- a/docs/en/serverless/apm/apm-integrate-with-machine-learning.asciidoc +++ b/docs/en/serverless/apm/apm-integrate-with-machine-learning.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - The Machine learning integration initiates a new job predefined to calculate anomaly scores on APM transaction durations. With this integration, you can quickly pinpoint anomalous transactions and see the health of any upstream and downstream services. diff --git a/docs/en/serverless/apm/apm-keep-data-secure.asciidoc b/docs/en/serverless/apm/apm-keep-data-secure.asciidoc index 04df108010..75fbb84b15 100644 --- a/docs/en/serverless/apm/apm-keep-data-secure.asciidoc +++ b/docs/en/serverless/apm/apm-keep-data-secure.asciidoc @@ -4,8 +4,6 @@ // :description: Make sure APM data is sent to Elastic securely and sensitive data is protected. // :keywords: serverless, observability, overview -preview:[] - :role: Editor :goal: create and manage API keys include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm/apm-kibana-settings.asciidoc b/docs/en/serverless/apm/apm-kibana-settings.asciidoc index 0998ef2c51..61b13c0e0b 100644 --- a/docs/en/serverless/apm/apm-kibana-settings.asciidoc +++ b/docs/en/serverless/apm/apm-kibana-settings.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - :role: Editor :goal: modify settings include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm/apm-observe-lambda-functions.asciidoc b/docs/en/serverless/apm/apm-observe-lambda-functions.asciidoc index f730d80e8f..c26812c0a6 100644 --- a/docs/en/serverless/apm/apm-observe-lambda-functions.asciidoc +++ b/docs/en/serverless/apm/apm-observe-lambda-functions.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - Elastic APM provides performance and error monitoring for AWS Lambda functions. See how your Lambda functions relate to and depend on other services, and get insight into function execution and runtime behavior, like lambda duration, cold start rate, cold start duration, compute usage, memory usage, and more. diff --git a/docs/en/serverless/apm/apm-query-your-data.asciidoc b/docs/en/serverless/apm/apm-query-your-data.asciidoc index 7d0e1e62cf..9d6081f3c7 100644 --- a/docs/en/serverless/apm/apm-query-your-data.asciidoc +++ b/docs/en/serverless/apm/apm-query-your-data.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - Querying your APM data is an essential tool that can make finding bottlenecks in your code even more straightforward. Using the query bar, a powerful data query feature, you can pass advanced queries on your data diff --git a/docs/en/serverless/apm/apm-reduce-your-data-usage.asciidoc b/docs/en/serverless/apm/apm-reduce-your-data-usage.asciidoc index f6c5268611..98fa1d9041 100644 --- a/docs/en/serverless/apm/apm-reduce-your-data-usage.asciidoc +++ b/docs/en/serverless/apm/apm-reduce-your-data-usage.asciidoc @@ -4,8 +4,6 @@ // :description: Implement strategies for reducing your data usage without compromising the ability to analyze APM data. // :keywords: serverless, observability, overview -preview:[] - The richness and volume of APM data provides unique insights into your applications, but it can also mean higher costs and more noise when analyzing data. There are a couple strategies you can use to reduce your data usage while continuing to get the full value of APM data. Read more about diff --git a/docs/en/serverless/apm/apm-reference.asciidoc b/docs/en/serverless/apm/apm-reference.asciidoc index f9b1aef9e9..7068da8e0a 100644 --- a/docs/en/serverless/apm/apm-reference.asciidoc +++ b/docs/en/serverless/apm/apm-reference.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - The following reference documentation is available: * <> diff --git a/docs/en/serverless/apm/apm-send-traces-to-elastic.asciidoc b/docs/en/serverless/apm/apm-send-traces-to-elastic.asciidoc index ac33f576db..a12f475f78 100644 --- a/docs/en/serverless/apm/apm-send-traces-to-elastic.asciidoc +++ b/docs/en/serverless/apm/apm-send-traces-to-elastic.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - :role: Admin :goal: send APM data to Elastic include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm/apm-server-api.asciidoc b/docs/en/serverless/apm/apm-server-api.asciidoc index ddd8a4e07d..aca9eb6042 100644 --- a/docs/en/serverless/apm/apm-server-api.asciidoc +++ b/docs/en/serverless/apm/apm-server-api.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - [WARNING] ==== This API is exclusively for APM agent developers. The vast majority of users should have no reason to interact with this API. diff --git a/docs/en/serverless/apm/apm-stacktrace-collection.asciidoc b/docs/en/serverless/apm/apm-stacktrace-collection.asciidoc index 5a6ae825d9..ee8133a161 100644 --- a/docs/en/serverless/apm/apm-stacktrace-collection.asciidoc +++ b/docs/en/serverless/apm/apm-stacktrace-collection.asciidoc @@ -4,8 +4,6 @@ // :description: Reduce data storage and costs by reducing stacktrace collection // :keywords: serverless, observability, how-to -preview:[] - Elastic APM agents collect `stacktrace` information under certain circumstances. This can be very helpful in identifying issues in your code, but it also comes with an overhead at collection time and increases your storage usage. Stack trace collection settings are managed in each APM agent. You can enable and disable this feature, or set specific configuration limits, like the maximum number of stacktrace frames to collect, or the minimum duration of a stacktrace to collect. diff --git a/docs/en/serverless/apm/apm-track-deployments-with-annotations.asciidoc b/docs/en/serverless/apm/apm-track-deployments-with-annotations.asciidoc index 1c4bd9d2c4..907abb245d 100644 --- a/docs/en/serverless/apm/apm-track-deployments-with-annotations.asciidoc +++ b/docs/en/serverless/apm/apm-track-deployments-with-annotations.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - :role: Admin :goal: create and manage annotations include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/apm/apm-transaction-sampling.asciidoc b/docs/en/serverless/apm/apm-transaction-sampling.asciidoc index a3d0116347..ef29464cfe 100644 --- a/docs/en/serverless/apm/apm-transaction-sampling.asciidoc +++ b/docs/en/serverless/apm/apm-transaction-sampling.asciidoc @@ -4,8 +4,6 @@ // :description: Reduce data storage, costs, and noise by ingesting only a percentage of all traces that you can extrapolate from in your analysis. // :keywords: serverless, observability, how-to -preview:[] - <> can generate a substantial amount of data. More data can mean higher costs and more noise. Sampling aims to lower the amount of data ingested and the effort required to analyze that data — diff --git a/docs/en/serverless/apm/apm-troubleshooting.asciidoc b/docs/en/serverless/apm/apm-troubleshooting.asciidoc index e07ea26ad0..12b62462cf 100644 --- a/docs/en/serverless/apm/apm-troubleshooting.asciidoc +++ b/docs/en/serverless/apm/apm-troubleshooting.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - This section provides solutions to common questions and problems, and processing and performance guidance. diff --git a/docs/en/serverless/apm/apm-ui-dependencies.asciidoc b/docs/en/serverless/apm/apm-ui-dependencies.asciidoc index d866655c71..df5ed22044 100644 --- a/docs/en/serverless/apm/apm-ui-dependencies.asciidoc +++ b/docs/en/serverless/apm/apm-ui-dependencies.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - APM agents collect details about external calls made from instrumented services. Sometimes, these external calls resolve into a downstream service that's instrumented — in these cases, you can utilize <> to drill down into problematic downstream services. diff --git a/docs/en/serverless/apm/apm-ui-errors.asciidoc b/docs/en/serverless/apm/apm-ui-errors.asciidoc index f5077f8b70..5bb237a802 100644 --- a/docs/en/serverless/apm/apm-ui-errors.asciidoc +++ b/docs/en/serverless/apm/apm-ui-errors.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - _Errors_ are groups of exceptions with a similar exception or log message. The **Errors** overview provides a high-level view of the exceptions that APM agents catch, or that users manually report with APM agent APIs. diff --git a/docs/en/serverless/apm/apm-ui-infrastructure.asciidoc b/docs/en/serverless/apm/apm-ui-infrastructure.asciidoc index 3b8928c1a0..0111662b16 100644 --- a/docs/en/serverless/apm/apm-ui-infrastructure.asciidoc +++ b/docs/en/serverless/apm/apm-ui-infrastructure.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - :feature: Applications UI Infrastructure include::../partials/feature-beta.asciidoc[] :feature!: diff --git a/docs/en/serverless/apm/apm-ui-logs.asciidoc b/docs/en/serverless/apm/apm-ui-logs.asciidoc index be01d1c0e5..be8bb597f1 100644 --- a/docs/en/serverless/apm/apm-ui-logs.asciidoc +++ b/docs/en/serverless/apm/apm-ui-logs.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - The **Logs** tab shows contextual logs for the selected service. include::../transclusion/kibana/logs/log-overview.asciidoc[] diff --git a/docs/en/serverless/apm/apm-ui-metrics.asciidoc b/docs/en/serverless/apm/apm-ui-metrics.asciidoc index cd9fbb90b5..c86e672a57 100644 --- a/docs/en/serverless/apm/apm-ui-metrics.asciidoc +++ b/docs/en/serverless/apm/apm-ui-metrics.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - The **Metrics** overview provides APM agent-specific metrics, which lets you perform more in-depth root cause analysis investigations within the Applications UI. diff --git a/docs/en/serverless/apm/apm-ui-overview.asciidoc b/docs/en/serverless/apm/apm-ui-overview.asciidoc index 1698cfce9b..4fba1337dd 100644 --- a/docs/en/serverless/apm/apm-ui-overview.asciidoc +++ b/docs/en/serverless/apm/apm-ui-overview.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to navigate the Applications UI. // :keywords: serverless, observability, reference -preview:[] - For a quick, high-level overview of the health and performance of your application, start with: diff --git a/docs/en/serverless/apm/apm-ui-service-map.asciidoc b/docs/en/serverless/apm/apm-ui-service-map.asciidoc index 8bf6d636c8..ea81e9b76c 100644 --- a/docs/en/serverless/apm/apm-ui-service-map.asciidoc +++ b/docs/en/serverless/apm/apm-ui-service-map.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - A service map is a real-time visual representation of the instrumented services in your application's architecture. It shows you how these services are connected, along with high-level metrics like average transaction duration, requests per minute, and errors per minute. diff --git a/docs/en/serverless/apm/apm-ui-service-overview.asciidoc b/docs/en/serverless/apm/apm-ui-service-overview.asciidoc index 8cabccdeef..d729346df1 100644 --- a/docs/en/serverless/apm/apm-ui-service-overview.asciidoc +++ b/docs/en/serverless/apm/apm-ui-service-overview.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - Selecting a <> brings you to the **Service overview**. The **Service overview** contains a wide variety of charts and tables that provide high-level visibility into how a service is performing across your infrastructure: diff --git a/docs/en/serverless/apm/apm-ui-services.asciidoc b/docs/en/serverless/apm/apm-ui-services.asciidoc index 1fa4cd07d7..9644d526ee 100644 --- a/docs/en/serverless/apm/apm-ui-services.asciidoc +++ b/docs/en/serverless/apm/apm-ui-services.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - The **Services** inventory provides a quick, high-level overview of the health and general performance of all instrumented services. diff --git a/docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc b/docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc index 8af33c6f32..c9ad55962b 100644 --- a/docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc +++ b/docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - The trace sample timeline visualization is a high-level view of what your application was doing while it was trying to respond to a request. This makes it useful for visualizing where a selected transaction spent most of its time. diff --git a/docs/en/serverless/apm/apm-ui-traces.asciidoc b/docs/en/serverless/apm/apm-ui-traces.asciidoc index 6f20a861fd..958acc05db 100644 --- a/docs/en/serverless/apm/apm-ui-traces.asciidoc +++ b/docs/en/serverless/apm/apm-ui-traces.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - [TIP] ==== Traces link together related transactions to show an end-to-end performance of how a request was served diff --git a/docs/en/serverless/apm/apm-ui-transactions.asciidoc b/docs/en/serverless/apm/apm-ui-transactions.asciidoc index 46cf846b62..690eca5aeb 100644 --- a/docs/en/serverless/apm/apm-ui-transactions.asciidoc +++ b/docs/en/serverless/apm/apm-ui-transactions.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, reference -preview:[] - A _transaction_ describes an event captured by an Elastic APM agent instrumenting a service. APM agents automatically collect performance metrics on HTTP requests, database queries, and much more. The **Transactions** tab shows an overview of all transactions. diff --git a/docs/en/serverless/apm/apm-view-and-analyze-traces.asciidoc b/docs/en/serverless/apm/apm-view-and-analyze-traces.asciidoc index 256c9d31cd..28603d4b81 100644 --- a/docs/en/serverless/apm/apm-view-and-analyze-traces.asciidoc +++ b/docs/en/serverless/apm/apm-view-and-analyze-traces.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - APM allows you to monitor your software services and applications in real time; visualize detailed performance information on your services, identify and analyze errors, diff --git a/docs/en/serverless/apm/apm.asciidoc b/docs/en/serverless/apm/apm.asciidoc index a07e8994bd..97b5c6a732 100644 --- a/docs/en/serverless/apm/apm.asciidoc +++ b/docs/en/serverless/apm/apm.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, overview -preview:[] - Elastic APM is an application performance monitoring system. It allows you to monitor software services and applications in real time, by collecting detailed performance information on response time for incoming requests, diff --git a/docs/en/serverless/cases/cases.asciidoc b/docs/en/serverless/cases/cases.asciidoc index fe5ea7c005..ce86e964a6 100644 --- a/docs/en/serverless/cases/cases.asciidoc +++ b/docs/en/serverless/cases/cases.asciidoc @@ -4,8 +4,6 @@ // :description: Use cases to track progress toward solving problems detected in Elastic Observability. // :keywords: serverless, observability, overview -preview:[] - Collect and share information about observability issues by creating a case. Cases allow you to track key investigation details, add assignees and tags to your cases, set their severity and status, and add alerts, diff --git a/docs/en/serverless/cases/create-manage-cases.asciidoc b/docs/en/serverless/cases/create-manage-cases.asciidoc index f0084fb7d5..79748fe9ee 100644 --- a/docs/en/serverless/cases/create-manage-cases.asciidoc +++ b/docs/en/serverless/cases/create-manage-cases.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to create a case, add files, and manage the case over time. // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create and manage cases include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/cases/manage-cases-settings.asciidoc b/docs/en/serverless/cases/manage-cases-settings.asciidoc index d169be842c..a42148c93f 100644 --- a/docs/en/serverless/cases/manage-cases-settings.asciidoc +++ b/docs/en/serverless/cases/manage-cases-settings.asciidoc @@ -4,8 +4,6 @@ // :description: Change the default behavior of {obs-serverless} cases by adding connectors, custom fields, templates, and closure options. // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create and edit connectors include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/dashboards/dashboards-and-visualizations.asciidoc b/docs/en/serverless/dashboards/dashboards-and-visualizations.asciidoc index dd450416c7..047f64916c 100644 --- a/docs/en/serverless/dashboards/dashboards-and-visualizations.asciidoc +++ b/docs/en/serverless/dashboards/dashboards-and-visualizations.asciidoc @@ -4,8 +4,6 @@ // :description: Visualize your observability data using pre-built dashboards or create your own. // :keywords: serverless, observability, overview -preview:[] - Elastic provides a wide range of pre-built dashboards for visualizing observability data from a variety of sources. These dashboards are loaded automatically when you install https://docs.elastic.co/integrations[Elastic integrations]. diff --git a/docs/en/serverless/elastic-entity-model.asciidoc b/docs/en/serverless/elastic-entity-model.asciidoc index 11d8e87941..3e3dfecbc0 100644 --- a/docs/en/serverless/elastic-entity-model.asciidoc +++ b/docs/en/serverless/elastic-entity-model.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about the model that empowers entity-centric Elastic solution features and workflows. // :keywords: serverless, observability, overview -preview:[] - The Elastic Entity Model consists of: * a data model and related entity indices diff --git a/docs/en/serverless/infra-monitoring/analyze-hosts.asciidoc b/docs/en/serverless/infra-monitoring/analyze-hosts.asciidoc index e763e1a2d4..13d087415c 100644 --- a/docs/en/serverless/infra-monitoring/analyze-hosts.asciidoc +++ b/docs/en/serverless/infra-monitoring/analyze-hosts.asciidoc @@ -4,8 +4,6 @@ // :description: Get a metrics-driven view of your hosts backed by an easy-to-use interface called Lens. // :keywords: serverless, observability, how to -preview:[] - We'd love to get your feedback! https://docs.google.com/forms/d/e/1FAIpQLScRHG8TIVb1Oq8ZhD4aks3P1TmgiM58TY123QpDCcBz83YC6w/viewform[Tell us what you think!] diff --git a/docs/en/serverless/infra-monitoring/aws-metrics.asciidoc b/docs/en/serverless/infra-monitoring/aws-metrics.asciidoc index 2554415b28..a6fdd62f7c 100644 --- a/docs/en/serverless/infra-monitoring/aws-metrics.asciidoc +++ b/docs/en/serverless/infra-monitoring/aws-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about key metrics used for AWS monitoring. // :keywords: serverless, observability, reference -preview:[] - [IMPORTANT] ==== Additional AWS charges for GetMetricData API requests are generated using this module. diff --git a/docs/en/serverless/infra-monitoring/configure-infra-settings.asciidoc b/docs/en/serverless/infra-monitoring/configure-infra-settings.asciidoc index 61ffe49456..bce8b59d39 100644 --- a/docs/en/serverless/infra-monitoring/configure-infra-settings.asciidoc +++ b/docs/en/serverless/infra-monitoring/configure-infra-settings.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to configure infrastructure UI settings. // :keywords: serverless, observability, how to -preview:[] - :role: Editor :goal: configure settings include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/infra-monitoring/container-metrics.asciidoc b/docs/en/serverless/infra-monitoring/container-metrics.asciidoc index 43c2bc1dc0..3f8179f65f 100644 --- a/docs/en/serverless/infra-monitoring/container-metrics.asciidoc +++ b/docs/en/serverless/infra-monitoring/container-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about key container metrics used for container monitoring. // :keywords: serverless, observability, reference -preview:[] - Learn about key container metrics displayed in the Infrastructure UI: * <> diff --git a/docs/en/serverless/infra-monitoring/detect-metric-anomalies.asciidoc b/docs/en/serverless/infra-monitoring/detect-metric-anomalies.asciidoc index a07bef833f..2346282380 100644 --- a/docs/en/serverless/infra-monitoring/detect-metric-anomalies.asciidoc +++ b/docs/en/serverless/infra-monitoring/detect-metric-anomalies.asciidoc @@ -4,8 +4,6 @@ // :description: Detect and inspect memory usage and network traffic anomalies for hosts and Kubernetes pods. // :keywords: serverless, observability, how to -preview:[] - :role: Editor :goal: create {ml} jobs include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/infra-monitoring/get-started-with-metrics.asciidoc b/docs/en/serverless/infra-monitoring/get-started-with-metrics.asciidoc index fa383711bd..8050d10351 100644 --- a/docs/en/serverless/infra-monitoring/get-started-with-metrics.asciidoc +++ b/docs/en/serverless/infra-monitoring/get-started-with-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to onboard your system metrics data quickly. // :keywords: serverless, observability, how-to -preview:[] - :role: Admin :goal: onboard system metrics data include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/infra-monitoring/handle-no-results-found-message.asciidoc b/docs/en/serverless/infra-monitoring/handle-no-results-found-message.asciidoc index baf985e001..1dd97c303f 100644 --- a/docs/en/serverless/infra-monitoring/handle-no-results-found-message.asciidoc +++ b/docs/en/serverless/infra-monitoring/handle-no-results-found-message.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about the reasons for "no results found" messages and how to fix them. // :keywords: serverless, observability, how to -preview:[] - To correctly render visualizations in the {obs-serverless} UI, all metrics used by the UI must be present in the collected data. For a description of these metrics, diff --git a/docs/en/serverless/infra-monitoring/host-metrics.asciidoc b/docs/en/serverless/infra-monitoring/host-metrics.asciidoc index 27e3e16e16..a631e08431 100644 --- a/docs/en/serverless/infra-monitoring/host-metrics.asciidoc +++ b/docs/en/serverless/infra-monitoring/host-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about key host metrics used for host monitoring. // :keywords: serverless, observability, reference -preview:[] - Learn about key host metrics displayed in the Infrastructure UI: * <> diff --git a/docs/en/serverless/infra-monitoring/infra-monitoring.asciidoc b/docs/en/serverless/infra-monitoring/infra-monitoring.asciidoc index 225ba7c176..83afbfd638 100644 --- a/docs/en/serverless/infra-monitoring/infra-monitoring.asciidoc +++ b/docs/en/serverless/infra-monitoring/infra-monitoring.asciidoc @@ -4,8 +4,6 @@ // :description: Monitor metrics from your servers, Docker, Kubernetes, Prometheus, and other services and applications. // :keywords: serverless, observability, overview -preview:[] - {obs-serverless} allows you to visualize infrastructure metrics to help diagnose problematic spikes, identify high resource utilization, automatically discover and track pods, and unify your metrics with logs and APM data. diff --git a/docs/en/serverless/infra-monitoring/kubernetes-pod-metrics.asciidoc b/docs/en/serverless/infra-monitoring/kubernetes-pod-metrics.asciidoc index ae946c6102..7c9800182a 100644 --- a/docs/en/serverless/infra-monitoring/kubernetes-pod-metrics.asciidoc +++ b/docs/en/serverless/infra-monitoring/kubernetes-pod-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about key metrics used for Kubernetes monitoring. // :keywords: serverless, observability, reference -preview:[] - To analyze Kubernetes pod metrics, you can select view filters based on the following predefined metrics, or you can add <>. diff --git a/docs/en/serverless/infra-monitoring/metrics-app-fields.asciidoc b/docs/en/serverless/infra-monitoring/metrics-app-fields.asciidoc index 758b4e7367..8b089fbae5 100644 --- a/docs/en/serverless/infra-monitoring/metrics-app-fields.asciidoc +++ b/docs/en/serverless/infra-monitoring/metrics-app-fields.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about the fields required to display data in the Infrastructure UI. // :keywords: serverless, observability, reference -preview:[] - This section lists the fields the Infrastructure UI uses to display data. Please note that some of the fields listed here are not {ecs-ref}/ecs-reference.html#_what_is_ecs[ECS fields]. diff --git a/docs/en/serverless/infra-monitoring/metrics-reference.asciidoc b/docs/en/serverless/infra-monitoring/metrics-reference.asciidoc index 0b3ce231f9..4998143707 100644 --- a/docs/en/serverless/infra-monitoring/metrics-reference.asciidoc +++ b/docs/en/serverless/infra-monitoring/metrics-reference.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about key metrics used for infrastructure monitoring. // :keywords: serverless, observability, reference -preview:[] - Learn about the key metrics displayed in the Infrastructure UI and how they are calculated. diff --git a/docs/en/serverless/infra-monitoring/troubleshooting-infra.asciidoc b/docs/en/serverless/infra-monitoring/troubleshooting-infra.asciidoc index 8b66523c31..e91af5210c 100644 --- a/docs/en/serverless/infra-monitoring/troubleshooting-infra.asciidoc +++ b/docs/en/serverless/infra-monitoring/troubleshooting-infra.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to troubleshoot issues with infrastructure monitoring. // :keywords: serverless, observability, how to -preview:[] - Learn how to troubleshoot common issues on your own or ask for help. * <> diff --git a/docs/en/serverless/infra-monitoring/view-infrastructure-metrics.asciidoc b/docs/en/serverless/infra-monitoring/view-infrastructure-metrics.asciidoc index 9f71943c6f..444ebd64aa 100644 --- a/docs/en/serverless/infra-monitoring/view-infrastructure-metrics.asciidoc +++ b/docs/en/serverless/infra-monitoring/view-infrastructure-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Get a metrics-driven view of your infrastructure grouped by resource type. // :keywords: serverless, observability, how to -preview:[] - The **Infrastructure Inventory** page provides a metrics-driven view of your entire infrastructure grouped by the resources you are monitoring. All monitored resources emitting a core set of infrastructure metrics are displayed to give you a quick view of the overall health diff --git a/docs/en/serverless/inventory.asciidoc b/docs/en/serverless/inventory.asciidoc index a18ff6a5d2..f73246252e 100644 --- a/docs/en/serverless/inventory.asciidoc +++ b/docs/en/serverless/inventory.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about the new Inventory experience that enables you to monitor all your entities from one single place. // :keywords: serverless, observability, inventory -preview:[] - Inventory provides a single place to observe the status of your entire ecosystem of hosts, containers, and services at a glance, even just from logs. From there, you can monitor and understand the health of your entities, check what needs attention, and start your investigations. [NOTE] diff --git a/docs/en/serverless/logging/correlate-application-logs.asciidoc b/docs/en/serverless/logging/correlate-application-logs.asciidoc index a4b515df7b..c262af4852 100644 --- a/docs/en/serverless/logging/correlate-application-logs.asciidoc +++ b/docs/en/serverless/logging/correlate-application-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about application logs and options for ingesting them. // :keywords: serverless, observability, overview -preview:[] - Application logs provide valuable insight into events that have occurred within your services and applications. The format of your logs (structured or plaintext) influences your log ingestion strategy. diff --git a/docs/en/serverless/logging/ecs-application-logs.asciidoc b/docs/en/serverless/logging/ecs-application-logs.asciidoc index 4f68847b87..05d851ca2a 100644 --- a/docs/en/serverless/logging/ecs-application-logs.asciidoc +++ b/docs/en/serverless/logging/ecs-application-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Use an ECS logger or an {apm-agent} to format your logs in ECS format. // :keywords: serverless, observability, how-to -preview:[] - Logs formatted in Elastic Common Schema (ECS) don't require manual parsing, and the configuration can be reused across applications. ECS-formatted logs, when paired with an {apm-agent}, allow you to correlate logs to easily view logs that belong to a particular trace. You can format your logs in ECS format the following ways: diff --git a/docs/en/serverless/logging/filter-and-aggregate-logs.asciidoc b/docs/en/serverless/logging/filter-and-aggregate-logs.asciidoc index 11f28086b5..74d719efb0 100644 --- a/docs/en/serverless/logging/filter-and-aggregate-logs.asciidoc +++ b/docs/en/serverless/logging/filter-and-aggregate-logs.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - Filter and aggregate your log data to find specific information, gain insight, and monitor your systems more efficiently. You can filter and aggregate based on structured fields like timestamps, log levels, and IP addresses that you've extracted from your log data. This guide shows you how to: diff --git a/docs/en/serverless/logging/get-started-with-logs.asciidoc b/docs/en/serverless/logging/get-started-with-logs.asciidoc index bca0c8d608..c80be97012 100644 --- a/docs/en/serverless/logging/get-started-with-logs.asciidoc +++ b/docs/en/serverless/logging/get-started-with-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to onboard your system log data quickly. // :keywords: serverless, observability, how-to -preview:[] - :role: Admin :goal: onboard log data include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/logging/log-monitoring.asciidoc b/docs/en/serverless/logging/log-monitoring.asciidoc index dbbeba23ec..860d1cd2bb 100644 --- a/docs/en/serverless/logging/log-monitoring.asciidoc +++ b/docs/en/serverless/logging/log-monitoring.asciidoc @@ -4,8 +4,6 @@ // :description: Use Elastic to deploy and manage logs at a petabyte scale, and get insights from your logs in minutes. // :keywords: serverless, observability, overview -preview:[] - Elastic Observability allows you to deploy and manage logs at a petabyte scale, giving you insights into your logs in minutes. You can also search across your logs in one place, troubleshoot in real time, and detect patterns and outliers with categorization and anomaly detection. For more information, refer to the following links: * <>: Onboard system log data from a machine or server. diff --git a/docs/en/serverless/logging/parse-log-data.asciidoc b/docs/en/serverless/logging/parse-log-data.asciidoc index 330c45d370..0f4c4407b0 100644 --- a/docs/en/serverless/logging/parse-log-data.asciidoc +++ b/docs/en/serverless/logging/parse-log-data.asciidoc @@ -3,8 +3,6 @@ // :keywords: serverless, observability, how-to -preview:[] - :role: Admin :goal: create ingest pipelines that parse and route logs include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/logging/plaintext-application-logs.asciidoc b/docs/en/serverless/logging/plaintext-application-logs.asciidoc index 8d1d444f6d..1082f6eb2f 100644 --- a/docs/en/serverless/logging/plaintext-application-logs.asciidoc +++ b/docs/en/serverless/logging/plaintext-application-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Parse and ingest raw, plain-text application logs using a log shipper like Filebeat. // :keywords: serverless, observability, how-to -preview:[] - Ingest and parse plaintext logs, including existing logs, from any programming language or framework without modifying your application or its configuration. Plaintext logs require some additional setup that structured logs do not require: diff --git a/docs/en/serverless/logging/run-log-pattern-analysis.asciidoc b/docs/en/serverless/logging/run-log-pattern-analysis.asciidoc index d930553cb8..da0d13096f 100644 --- a/docs/en/serverless/logging/run-log-pattern-analysis.asciidoc +++ b/docs/en/serverless/logging/run-log-pattern-analysis.asciidoc @@ -4,8 +4,6 @@ // :description: Find patterns in unstructured log messages. // :keywords: serverless, observability, how-to -preview:[] - preview::[] Log pattern analysis helps you find patterns in unstructured log messages and makes it easier to examine your data. diff --git a/docs/en/serverless/logging/send-application-logs.asciidoc b/docs/en/serverless/logging/send-application-logs.asciidoc index 445c645620..185825d796 100644 --- a/docs/en/serverless/logging/send-application-logs.asciidoc +++ b/docs/en/serverless/logging/send-application-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Use the Java {apm-agent} to capture and send logs. // :keywords: serverless, observability, how-to -preview:[] - include::../transclusion/observability/application-logs/apm-agent-log-sending.asciidoc[] [discrete] diff --git a/docs/en/serverless/logging/stream-log-files.asciidoc b/docs/en/serverless/logging/stream-log-files.asciidoc index b83d62e71f..96656047a7 100644 --- a/docs/en/serverless/logging/stream-log-files.asciidoc +++ b/docs/en/serverless/logging/stream-log-files.asciidoc @@ -4,8 +4,6 @@ // :description: Send a log file to your Observability project using the standalone {agent}. // :keywords: serverless, observability, how-to -preview:[] - :role: Admin :goal: onboard log data include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/logging/troubleshoot-logs.asciidoc b/docs/en/serverless/logging/troubleshoot-logs.asciidoc index 2d025616f1..a84fa22533 100644 --- a/docs/en/serverless/logging/troubleshoot-logs.asciidoc +++ b/docs/en/serverless/logging/troubleshoot-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Find solutions to errors you might encounter while onboarding your logs. // :keywords: serverless, observability, troubleshooting -preview:[] - This section provides possible solutions for errors you might encounter while onboarding your logs. [discrete] diff --git a/docs/en/serverless/logging/view-and-monitor-logs.asciidoc b/docs/en/serverless/logging/view-and-monitor-logs.asciidoc index 251f531370..dfad76d82d 100644 --- a/docs/en/serverless/logging/view-and-monitor-logs.asciidoc +++ b/docs/en/serverless/logging/view-and-monitor-logs.asciidoc @@ -4,8 +4,6 @@ // :description: Visualize and analyze logs. // :keywords: serverless, observability, how-to -preview:[] - With **Logs Explorer**, based on Discover, you can quickly search and filter your log data, get information about the structure of log fields, and display your findings in a visualization. You can also customize and save your searches and place them on a dashboard. Instead of having to log into different servers, change directories, and view individual files, all your logs are available in a single view. diff --git a/docs/en/serverless/observability-overview.asciidoc b/docs/en/serverless/observability-overview.asciidoc index f27d9b70c3..a526260f4e 100644 --- a/docs/en/serverless/observability-overview.asciidoc +++ b/docs/en/serverless/observability-overview.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to accelerate problem resolution with open, flexible, and unified observability powered by advanced machine learning and analytics. // :keywords: serverless, observability, overview -preview:[] - {obs-serverless} provides granular insights and context into the behavior of applications running in your environments. It's an important part of any system that you build and want to monitor. Being able to detect and fix root cause events quickly within an observable system is a minimum requirement for any analyst. diff --git a/docs/en/serverless/projects/billing.asciidoc b/docs/en/serverless/projects/billing.asciidoc index a117dcfda3..a8f1c0a360 100644 --- a/docs/en/serverless/projects/billing.asciidoc +++ b/docs/en/serverless/projects/billing.asciidoc @@ -4,8 +4,6 @@ // :description: Learn about how Observability usage affects pricing. // :keywords: serverless, observability, overview -preview:[] - Elastic Observability severless projects provide you with all the capabilities of Elastic Observability to monitor critical applications. Projects are provided using a Software as a Service (SaaS) model, and pricing is entirely consumption-based. diff --git a/docs/en/serverless/projects/create-an-observability-project.asciidoc b/docs/en/serverless/projects/create-an-observability-project.asciidoc index 8e77027168..7c2a945e01 100644 --- a/docs/en/serverless/projects/create-an-observability-project.asciidoc +++ b/docs/en/serverless/projects/create-an-observability-project.asciidoc @@ -15,8 +15,6 @@ include::../partials/roles.asciidoc[] :goal!: -preview:[] - An {obs-serverless} project allows you to run {obs-serverless} in an autoscaled and fully-managed environment, where you don't have to manage the underlying {es} cluster or {kib} instances. diff --git a/docs/en/serverless/quickstarts/k8s-logs-metrics.asciidoc b/docs/en/serverless/quickstarts/k8s-logs-metrics.asciidoc index 3e2a7a5a95..6a30cb6d7e 100644 --- a/docs/en/serverless/quickstarts/k8s-logs-metrics.asciidoc +++ b/docs/en/serverless/quickstarts/k8s-logs-metrics.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to monitor your cluster infrastructure running on Kubernetes. // :keywords: serverless, observability, how-to -preview:[] - In this quickstart guide, you'll learn how to create the Kubernetes resources that are required to monitor your cluster infrastructure. This new approach requires minimal configuration and provides you with an easy setup to monitor your infrastructure. You no longer need to download, install, or configure the Elastic Agent, everything happens automatically when you run the kubectl command. diff --git a/docs/en/serverless/quickstarts/monitor-hosts-with-elastic-agent.asciidoc b/docs/en/serverless/quickstarts/monitor-hosts-with-elastic-agent.asciidoc index 12a6f564fd..ad1c92e011 100644 --- a/docs/en/serverless/quickstarts/monitor-hosts-with-elastic-agent.asciidoc +++ b/docs/en/serverless/quickstarts/monitor-hosts-with-elastic-agent.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to scan your hosts to detect and collect logs and metrics. // :keywords: serverless, observability, how-to -preview:[] - In this quickstart guide, you'll learn how to scan your host to detect and collect logs and metrics, then navigate to dashboards to further analyze and explore your observability data. You'll also learn how to get value out of your observability data. diff --git a/docs/en/serverless/slos/create-an-slo.asciidoc b/docs/en/serverless/slos/create-an-slo.asciidoc index 2c62e5cc01..2973ae0bc2 100644 --- a/docs/en/serverless/slos/create-an-slo.asciidoc +++ b/docs/en/serverless/slos/create-an-slo.asciidoc @@ -4,8 +4,6 @@ // :description: Learn how to define a service-level indicator (SLI), set an objective, and create a service-level objective (SLO). // :keywords: serverless, observability, how-to -preview:[] - :role: Editor :goal: create SLOs include::../partials/roles.asciidoc[] diff --git a/docs/en/serverless/slos/slos.asciidoc b/docs/en/serverless/slos/slos.asciidoc index 98004edd0c..08ae5dd10e 100644 --- a/docs/en/serverless/slos/slos.asciidoc +++ b/docs/en/serverless/slos/slos.asciidoc @@ -4,8 +4,6 @@ // :description: Set clear, measurable targets for your service performance with service-level objectives (SLOs). // :keywords: serverless, observability, overview -preview:[] - Service-level objectives (SLOs) allow you to set clear, measurable targets for your service performance, based on factors like availability, response times, error rates, and other key metrics. You can define SLOs based on different types of data sources, such as custom KQL queries and APM latency or availability data. diff --git a/docs/en/serverless/synthetics/synthetics-analyze.asciidoc b/docs/en/serverless/synthetics/synthetics-analyze.asciidoc index 3e64b23f77..db7b809b7c 100644 --- a/docs/en/serverless/synthetics/synthetics-analyze.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-analyze.asciidoc @@ -5,8 +5,6 @@ Analyze monitor data ++++ -preview:[] - The Synthetics UI in Observability projects both provides a high-level overview of your service's availability and allows you to dig into details to diagnose what caused downtime. diff --git a/docs/en/serverless/synthetics/synthetics-command-reference.asciidoc b/docs/en/serverless/synthetics/synthetics-command-reference.asciidoc index fa0630e090..8665d1fe74 100644 --- a/docs/en/serverless/synthetics/synthetics-command-reference.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-command-reference.asciidoc @@ -5,8 +5,6 @@ Use the CLI ++++ -preview:[] - [discrete] [[elastic-synthetics-command]] == `@elastic/synthetics` diff --git a/docs/en/serverless/synthetics/synthetics-configuration.asciidoc b/docs/en/serverless/synthetics/synthetics-configuration.asciidoc index 3e13f1deff..cb65bcd633 100644 --- a/docs/en/serverless/synthetics/synthetics-configuration.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-configuration.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-configuration]] = Configure a Synthetics project -preview:[] - Synthetic tests support the configuration of dynamic parameters that can be used in Synthetics projects. In addition, the Synthetics agent, which is built on top of Playwright, supports configuring browser and context options that are available diff --git a/docs/en/serverless/synthetics/synthetics-create-test.asciidoc b/docs/en/serverless/synthetics/synthetics-create-test.asciidoc index bf099fdf6f..70575762d8 100644 --- a/docs/en/serverless/synthetics/synthetics-create-test.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-create-test.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-create-test]] = Write a synthetic test -preview:[] - After <>, you can start writing synthetic tests that check critical actions and requests that an end-user might make on your site. diff --git a/docs/en/serverless/synthetics/synthetics-feature-roles.asciidoc b/docs/en/serverless/synthetics/synthetics-feature-roles.asciidoc index 5b2428c155..823254bfae 100644 --- a/docs/en/serverless/synthetics/synthetics-feature-roles.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-feature-roles.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-feature-roles]] = Grant users access to secured resources -preview:[] - You can use role-based access control to grant users access to secured resources. The roles that you set up depend on your organization's security requirements and the minimum privileges required to use specific features. diff --git a/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc b/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc index aca2059a78..f3b16c7e5c 100644 --- a/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc @@ -5,8 +5,6 @@ Use a Synthetics project ++++ -preview:[] - A Synthetics project is the most powerful and sophisticated way to configure synthetic monitors. A Synthetics project lets you define your infrastructure as code, more commonly known as IaaC or Git-ops. With monitors created and managed in Synthetics projects, you organize your YAML configuration and diff --git a/docs/en/serverless/synthetics/synthetics-get-started-ui.asciidoc b/docs/en/serverless/synthetics/synthetics-get-started-ui.asciidoc index 428999ab99..f359f0eb70 100644 --- a/docs/en/serverless/synthetics/synthetics-get-started-ui.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-get-started-ui.asciidoc @@ -5,8 +5,6 @@ Use the Synthetics UI ++++ -preview:[] - You can create synthetic monitors directly in the UI by opening an Observability project and navigating to **Synthetics**. image::images/synthetics-get-started-ui.png[Diagram showing which pieces of software are used to configure monitors, create monitors, and view results when using Synthetics projects.] diff --git a/docs/en/serverless/synthetics/synthetics-get-started.asciidoc b/docs/en/serverless/synthetics/synthetics-get-started.asciidoc index 749dd68bca..0c0ba5f04e 100644 --- a/docs/en/serverless/synthetics/synthetics-get-started.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-get-started.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-get-started]] = Get started -preview:[] - To set up a synthetic monitor, you need to configure the monitor, run it, and send data back to Elastic. After setup is complete, the data will be available in your Observability project to view, analyze, and alert on. diff --git a/docs/en/serverless/synthetics/synthetics-intro.asciidoc b/docs/en/serverless/synthetics/synthetics-intro.asciidoc index 6eea8a46ad..0a8da0da53 100644 --- a/docs/en/serverless/synthetics/synthetics-intro.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-intro.asciidoc @@ -1,8 +1,6 @@ [[observability-monitor-synthetics]] = Synthetic monitoring -preview:[] - [NOTE] ==== The Synthetics UI is for viewing result data from monitors created and managed diff --git a/docs/en/serverless/synthetics/synthetics-journeys.asciidoc b/docs/en/serverless/synthetics/synthetics-journeys.asciidoc index 05709d39dd..d9b9c38c6b 100644 --- a/docs/en/serverless/synthetics/synthetics-journeys.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-journeys.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-journeys]] = Scripting browser monitors -preview:[] - Browser monitors are a type of synthetic monitor. Synthetic monitoring extends traditional end-to-end testing techniques because it allows your tests to run continuously on the cloud. With synthetic monitoring, you can assert that your application continues to work after a deployment by reusing diff --git a/docs/en/serverless/synthetics/synthetics-lightweight.asciidoc b/docs/en/serverless/synthetics/synthetics-lightweight.asciidoc index 637f414d50..4cb22d14e0 100644 --- a/docs/en/serverless/synthetics/synthetics-lightweight.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-lightweight.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-lightweight]] = Configure lightweight monitors -preview:[] - Monitor the status of network endpoints using the following lightweight checks: * **HTTP**: Monitor your website. The HTTP monitor checks to make sure specific endpoints return the correct diff --git a/docs/en/serverless/synthetics/synthetics-manage-monitors.asciidoc b/docs/en/serverless/synthetics/synthetics-manage-monitors.asciidoc index cf4445c0bc..c24b373574 100644 --- a/docs/en/serverless/synthetics/synthetics-manage-monitors.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-manage-monitors.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-manage-monitors]] = Manage monitors -preview:[] - After you've <>, you'll need to manage that monitor over time. This might include updating or permanently deleting an existing monitor. diff --git a/docs/en/serverless/synthetics/synthetics-manage-retention.asciidoc b/docs/en/serverless/synthetics/synthetics-manage-retention.asciidoc index 66bfb3fc37..f7d6c0fe5d 100644 --- a/docs/en/serverless/synthetics/synthetics-manage-retention.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-manage-retention.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-manage-retention]] = Manage data retention -preview:[] - When you set up a synthetic monitor, data from the monitor is saved in {ref}/data-streams.html[{es} data streams], an append-only structure in {es}. diff --git a/docs/en/serverless/synthetics/synthetics-mfa.asciidoc b/docs/en/serverless/synthetics/synthetics-mfa.asciidoc index 8afc1d38a5..eee8de6720 100644 --- a/docs/en/serverless/synthetics/synthetics-mfa.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-mfa.asciidoc @@ -5,8 +5,6 @@ Multifactor Authentication for browser monitors ++++ -preview:[] - Multi-factor Authentication (MFA) adds an essential layer of security to applications login processes, protecting against unauthorized access. A very common use case in Synthetics is testing user journeys involving websites diff --git a/docs/en/serverless/synthetics/synthetics-monitor-use.asciidoc b/docs/en/serverless/synthetics/synthetics-monitor-use.asciidoc index af2bf4c7cf..436a48ac23 100644 --- a/docs/en/serverless/synthetics/synthetics-monitor-use.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-monitor-use.asciidoc @@ -5,8 +5,6 @@ Configure individual monitors ++++ -preview:[] - [NOTE] ==== This is only relevant for monitors that are created and managed using a <>. diff --git a/docs/en/serverless/synthetics/synthetics-params-secrets.asciidoc b/docs/en/serverless/synthetics/synthetics-params-secrets.asciidoc index 7c31afc78a..17810b1ea1 100644 --- a/docs/en/serverless/synthetics/synthetics-params-secrets.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-params-secrets.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-params-secrets]] = Work with params and secrets -preview:[] - // lint disable params Params allow you to use dynamically defined values in your synthetic monitors. diff --git a/docs/en/serverless/synthetics/synthetics-private-location.asciidoc b/docs/en/serverless/synthetics/synthetics-private-location.asciidoc index 38004ee4b3..4ca28b0693 100644 --- a/docs/en/serverless/synthetics/synthetics-private-location.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-private-location.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-private-location]] = Monitor resources on private networks -preview:[] - To monitor resources on private networks you can either: * Allow Elastic's global managed infrastructure to access your private endpoints. diff --git a/docs/en/serverless/synthetics/synthetics-recorder.asciidoc b/docs/en/serverless/synthetics/synthetics-recorder.asciidoc index 9cb1c57c90..df9ca1f7ca 100644 --- a/docs/en/serverless/synthetics/synthetics-recorder.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-recorder.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-recorder]] = Use the Synthetics Recorder -preview:[] - [IMPORTANT] ==== As with any script recording technology, the Elastic Synthetics Recorder should be used as a tool to help create the main structure of the script. For simpler sites, you may be able to use the Synthetics Recorder's output directly to create a synthetic monitor, but for more complex and dynamic sites, or to limit flakiness, you'll likely need to edit its output before using it to create a monitor. diff --git a/docs/en/serverless/synthetics/synthetics-scale-and-architect.asciidoc b/docs/en/serverless/synthetics/synthetics-scale-and-architect.asciidoc index 1deaba9b60..fa73c1c382 100644 --- a/docs/en/serverless/synthetics/synthetics-scale-and-architect.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-scale-and-architect.asciidoc @@ -5,8 +5,6 @@ Scale and architect a deployment ++++ -preview:[] - Use these advanced considerations when using Elastic Synthetics for large and complex use cases. diff --git a/docs/en/serverless/synthetics/synthetics-security-encryption.asciidoc b/docs/en/serverless/synthetics/synthetics-security-encryption.asciidoc index dc3110d6da..2559679e36 100644 --- a/docs/en/serverless/synthetics/synthetics-security-encryption.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-security-encryption.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-security-encryption]] = Synthetics Encryption and Security -preview:[] - Elastic Synthetics was designed with security in mind encrypting both persisted and transmitted data. This page catalogs the points within Elastic Synthetics where data is either stored or transmitted in an encrypted fashion. diff --git a/docs/en/serverless/synthetics/synthetics-settings.asciidoc b/docs/en/serverless/synthetics/synthetics-settings.asciidoc index 1e3fb6af4e..10cd52a559 100644 --- a/docs/en/serverless/synthetics/synthetics-settings.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-settings.asciidoc @@ -1,8 +1,6 @@ [[observability-synthetics-settings]] = Configure Synthetics settings -preview:[] - There are several Synthetics settings you can adjust in your Observability project. [discrete] diff --git a/docs/en/serverless/synthetics/synthetics-troubleshooting.asciidoc b/docs/en/serverless/synthetics/synthetics-troubleshooting.asciidoc index 312a3952cf..7d19e23997 100644 --- a/docs/en/serverless/synthetics/synthetics-troubleshooting.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-troubleshooting.asciidoc @@ -5,8 +5,6 @@ Troubleshooting ++++ -preview:[] - [discrete] [[synthetics-troubleshooting-local-debugging]] == Local debugging diff --git a/docs/en/serverless/technical-preview-limitations.asciidoc b/docs/en/serverless/technical-preview-limitations.asciidoc index 6a93564ae2..10d685f8fc 100644 --- a/docs/en/serverless/technical-preview-limitations.asciidoc +++ b/docs/en/serverless/technical-preview-limitations.asciidoc @@ -4,6 +4,4 @@ // :description: Review the limitations that apply to Elastic Observability projects in technical preview. // :keywords: serverless, observability -preview:[] - Currently, the maximum ingestion rate for the Managed Intake Service (APM and OpenTelemetry ingest) is 11.5 MB/s of uncompressed data (roughly 1TB/d uncompressed equivalent). Ingestion at a higher rate may experience rate limiting or ingest failures. diff --git a/docs/en/serverless/what-is-observability-serverless.asciidoc b/docs/en/serverless/what-is-observability-serverless.asciidoc index 940948ae71..64ed8cd0e4 100644 --- a/docs/en/serverless/what-is-observability-serverless.asciidoc +++ b/docs/en/serverless/what-is-observability-serverless.asciidoc @@ -1,7 +1,5 @@ // :keywords: serverless, observability, overview -preview:[] - Elastic Observability accelerates problem resolution with open, flexible, and unified observability powered by advanced machine learning and analytics. Elastic ingests all operational and business telemetry and correlates for faster root cause detection. .Production workloads From 1ae7794dc5bd272d691e92a0eaec02563a0cf7c1 Mon Sep 17 00:00:00 2001 From: dedemorton Date: Wed, 13 Nov 2024 15:49:21 -0800 Subject: [PATCH 2/2] Update inline tech preview tags --- .../alerting/create-elasticsearch-query-alert-rule.asciidoc | 4 ++-- docs/en/serverless/alerting/create-manage-rules.asciidoc | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc b/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc index 7f6316a13a..33f73fe8d9 100644 --- a/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc +++ b/docs/en/serverless/alerting/create-elasticsearch-query-alert-rule.asciidoc @@ -55,7 +55,7 @@ For example: If you use {kibana-ref}/kuery-query.html[KQL] or {kibana-ref}/lucene-query.html[Lucene], you must specify a data view then define a text-based query. For example, `http.request.referrer: "https://example.com"`. + -preview:[] If you use {ref}/esql.html[ES|QL], you must provide a source command followed by an optional series of processing commands, separated by pipe characters (|). +If you use {ref}/esql.html[ES|QL], you must provide a source command followed by an optional series of processing commands, separated by pipe characters (|). For example: + [source,sh] @@ -104,7 +104,7 @@ image::images/alerting-rule-types-es-query-valid.png[Test {es} query returns num // NOTE: This is an autogenerated screenshot. Do not edit it directly. -preview:[] If you use an ES|QL query, a table is displayed. For example: +If you use an ES|QL query, a table is displayed. For example: [role="screenshot"] image::images/alerting-rule-types-esql-query-valid.png[Test ES|QL query returns a table when valid] diff --git a/docs/en/serverless/alerting/create-manage-rules.asciidoc b/docs/en/serverless/alerting/create-manage-rules.asciidoc index 2b07333ad0..29bb69d3af 100644 --- a/docs/en/serverless/alerting/create-manage-rules.asciidoc +++ b/docs/en/serverless/alerting/create-manage-rules.asciidoc @@ -124,7 +124,7 @@ time, indefinitely, or schedule single or recurring downtimes. When a rule is in a snoozed state, you can cancel or change the duration of this state. -preview:[] To temporarily suppress notifications for _all_ rules, create a <>. +To temporarily suppress notifications for _all_ rules, create a <>. // Remove tech preview?