From ae2be7d0e5889b95a356625875919a6c16d80b91 Mon Sep 17 00:00:00 2001 From: Colleen McGinnis Date: Wed, 27 Nov 2024 15:38:49 -0600 Subject: [PATCH] use shared attribute --- docs/en/observability/landing-page/page.asciidoc | 2 +- .../apm-agents-opentelemetry-limitations.asciidoc | 2 +- .../apm-agents/apm-agents-opentelemetry.asciidoc | 2 +- .../serverless/apm/apm-ui-trace-sample-timeline.asciidoc | 2 +- docs/en/serverless/cases/cases.asciidoc | 2 +- docs/en/serverless/cases/manage-cases-settings.asciidoc | 4 ++-- docs/en/serverless/index.asciidoc | 4 ++-- docs/en/serverless/logging/log-monitoring.asciidoc | 2 +- docs/en/serverless/observability-get-started.asciidoc | 4 ++-- docs/en/serverless/projects/billing.asciidoc | 8 ++++---- .../en/serverless/reference/elastic-entity-model.asciidoc | 2 +- .../synthetics/synthetics-get-started-project.asciidoc | 2 +- .../en/serverless/synthetics/synthetics-settings.asciidoc | 2 +- .../apm/guide/diagrams/apm-otel-architecture.asciidoc | 2 +- .../synthetics/global-managed-paid-for.asciidoc | 2 +- .../serverless/what-is-observability-serverless.asciidoc | 6 +++--- 16 files changed, 24 insertions(+), 24 deletions(-) diff --git a/docs/en/observability/landing-page/page.asciidoc b/docs/en/observability/landing-page/page.asciidoc index 6b92ef6b0d..65da406a01 100644 --- a/docs/en/observability/landing-page/page.asciidoc +++ b/docs/en/observability/landing-page/page.asciidoc @@ -2,7 +2,7 @@ include::temp/style.asciidoc[] [subs=attributes+] ++++ -

Rely on the most widely deployed observability solution, powered by machine learning and analytics, to converge metrics, logs, and traces that deliver unified visibility and actionable insights.

  • Eliminate tool silos and efficiently store data
  • Get visibility across hybrid and multi-cloud environments
  • Monitor your digital experience — 24/7

Using serverless? Go to the Elastic Observability serverless docs.

What do you want to observe?

Use cases

Cloud monitoring

Cross-platform and multi-cloud visibility and analytics.

DevOps

Observe your entire software lifecycle — from development to production.

  • CI/CD
    Get better visibility into your CI/CD pipelines.
  • ECS logging
    Leverage the Elastic Common Schema logging libraries to automatically link application traces to their corresponding logs.

AIOps

Automate anomaly detection and accelerate root cause analysis.

  • Root cause analysis with logs
    Learn about Elastic’s artificial intelligence for IT operations and machine learning capabilities for root cause analysis.
  • APM Correlations
    Automatically identify the probable causes of slow or failed transactions.

User experience

Measure, gauge, and improve your end users’ experience.

  • Scripting browser monitors
    Simulate critical user workflows on a regular interval to catch bugs before your users report them.
  • User experience
    Learn how to track Core Web Vitals and how to use them to quantify the real-world user experience.

Related documentation

+

Rely on the most widely deployed observability solution, powered by machine learning and analytics, to converge metrics, logs, and traces that deliver unified visibility and actionable insights.

  • Eliminate tool silos and efficiently store data
  • Get visibility across hybrid and multi-cloud environments
  • Monitor your digital experience — 24/7

Using serverless? Go to the {obs-serverless} docs.

What do you want to observe?

Use cases

Cloud monitoring

Cross-platform and multi-cloud visibility and analytics.

DevOps

Observe your entire software lifecycle — from development to production.

  • CI/CD
    Get better visibility into your CI/CD pipelines.
  • ECS logging
    Leverage the Elastic Common Schema logging libraries to automatically link application traces to their corresponding logs.

AIOps

Automate anomaly detection and accelerate root cause analysis.

  • Root cause analysis with logs
    Learn about Elastic’s artificial intelligence for IT operations and machine learning capabilities for root cause analysis.
  • APM Correlations
    Automatically identify the probable causes of slow or failed transactions.

User experience

Measure, gauge, and improve your end users’ experience.

  • Scripting browser monitors
    Simulate critical user workflows on a regular interval to catch bugs before your users report them.
  • User experience
    Learn how to track Core Web Vitals and how to use them to quantify the real-world user experience.

Related documentation

++++ ++++ 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 6d0003e4b0..87009e9157 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry-limitations.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry-limitations.asciidoc @@ -35,4 +35,4 @@ The https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/ has been deprecated and replaced by the native support of the OpenTelemetry Line Protocol in Elastic Observability (OTLP). To learn more, see https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/elasticsearchexporter#migration[migration]. The https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/elasticsearchexporter[OpenTelemetry Collector exporter for Elastic] -(which is different from the legacy exporter mentioned above) is not intended to be used with Elastic APM and Elastic Observability. Use <> instead. +(which is different from the legacy exporter mentioned above) is not intended to be used with Elastic APM and {obs-serverless}. Use <> instead. diff --git a/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc b/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc index 3bc596c183..2f6f544eb7 100644 --- a/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc +++ b/docs/en/serverless/apm-agents/apm-agents-opentelemetry.asciidoc @@ -118,7 +118,7 @@ For more on the limitations associated with using upstream OpenTelemetry tools, [[observability-apm-agents-opentelemetry-aws-lambda-collector-exporter]] == AWS Lambda collector exporter -AWS Lambda functions can be instrumented with OpenTelemetry and monitored with Elastic Observability. +AWS Lambda functions can be instrumented with OpenTelemetry and monitored with {obs-serverless}. // Do we want to say anything about why you would/wouldn't choose this method to send data to Elastic? 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 c9ad55962b..c09c5dac59 100644 --- a/docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc +++ b/docs/en/serverless/apm/apm-ui-trace-sample-timeline.asciidoc @@ -32,7 +32,7 @@ image::images/spans/apm-span-detail.png[Example view of a span detail in the App == Investigate The trace sample timeline features an **Investigate** button which provides a quick way to jump -to other areas of the Elastic Observability UI while maintaining the context of the currently selected trace sample. +to other areas of the {obs-serverless} UI while maintaining the context of the currently selected trace sample. For example, quickly view: * logs and metrics for the selected pod diff --git a/docs/en/serverless/cases/cases.asciidoc b/docs/en/serverless/cases/cases.asciidoc index ce86e964a6..2b05f96079 100644 --- a/docs/en/serverless/cases/cases.asciidoc +++ b/docs/en/serverless/cases/cases.asciidoc @@ -1,7 +1,7 @@ [[observability-cases]] = Cases -// :description: Use cases to track progress toward solving problems detected in Elastic Observability. +// :description: Use cases to track progress toward solving problems detected in {obs-serverless}. // :keywords: serverless, observability, overview Collect and share information about observability issues by creating a case. diff --git a/docs/en/serverless/cases/manage-cases-settings.asciidoc b/docs/en/serverless/cases/manage-cases-settings.asciidoc index a42148c93f..82cb7026dd 100644 --- a/docs/en/serverless/cases/manage-cases-settings.asciidoc +++ b/docs/en/serverless/cases/manage-cases-settings.asciidoc @@ -22,7 +22,7 @@ image::images/observability-cases-settings.png[View case settings] [[observability-case-settings-case-closures]] == Case closures -If you close cases in your external incident management system, the cases will remain open in Elastic Observability until you close them manually (the information is only sent in one direction). +If you close cases in your external incident management system, the cases will remain open in {obs-serverless} until you close them manually (the information is only sent in one direction). To close cases when they are sent to an external system, select **Automatically close cases when pushing new incident to external system**. @@ -30,7 +30,7 @@ To close cases when they are sent to an external system, select **Automatically [[observability-case-settings-external-incident-management-systems]] == External incident management systems -If you are using an external incident management system, you can integrate Elastic Observability +If you are using an external incident management system, you can integrate {obs-serverless} cases with this system using connectors. These third-party systems are supported: * {ibm-r} diff --git a/docs/en/serverless/index.asciidoc b/docs/en/serverless/index.asciidoc index 908c8a6b84..a84368fee2 100644 --- a/docs/en/serverless/index.asciidoc +++ b/docs/en/serverless/index.asciidoc @@ -2,7 +2,7 @@ include::{asciidoc-dir}/../../shared/versions/stack/current.asciidoc[] include::{asciidoc-dir}/../../shared/attributes.asciidoc[] [[what-is-observability-serverless]] -== Elastic Observability serverless +== {obs-serverless} ++++ Elastic Observability @@ -10,7 +10,7 @@ include::{asciidoc-dir}/../../shared/attributes.asciidoc[] include::./what-is-observability-serverless.asciidoc[leveloffset=+2] -// Group: Get started with Elastic Observability +// Group: Get started with Elastic Observability Serverless include::observability-get-started.asciidoc[leveloffset=+2] // What is Observability? diff --git a/docs/en/serverless/logging/log-monitoring.asciidoc b/docs/en/serverless/logging/log-monitoring.asciidoc index ccc9ce684e..122c3d8641 100644 --- a/docs/en/serverless/logging/log-monitoring.asciidoc +++ b/docs/en/serverless/logging/log-monitoring.asciidoc @@ -8,7 +8,7 @@ // :description: Use Elastic to deploy and manage logs at a petabyte scale, and get insights from your logs in minutes. // :keywords: serverless, observability, overview -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: +{obs-serverless} 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. * <>: Send log files to your Observability project using a standalone {agent}. diff --git a/docs/en/serverless/observability-get-started.asciidoc b/docs/en/serverless/observability-get-started.asciidoc index 30defd72be..0396d59b1a 100644 --- a/docs/en/serverless/observability-get-started.asciidoc +++ b/docs/en/serverless/observability-get-started.asciidoc @@ -1,5 +1,5 @@ [[observability-get-started]] -= Get started with Elastic Observability += Get started with {obs-serverless} ++++ Get started @@ -72,7 +72,7 @@ Follow the steps in these guides to get started: [discrete] == Additional guides -Ready to dig into more features of Elastic Observability? See these guides: +Ready to dig into more features of {obs-serverless}? See these guides: * <> * <> diff --git a/docs/en/serverless/projects/billing.asciidoc b/docs/en/serverless/projects/billing.asciidoc index a8f1c0a360..f1e2c8ac63 100644 --- a/docs/en/serverless/projects/billing.asciidoc +++ b/docs/en/serverless/projects/billing.asciidoc @@ -1,14 +1,14 @@ [[observability-billing]] -= Observability billing dimensions += {obs-serverless} billing dimensions // :description: Learn about how Observability usage affects pricing. // :keywords: serverless, observability, overview -Elastic Observability severless projects provide you with all the capabilities of Elastic Observability to monitor critical applications. +{obs-serverless} 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. Your monthly bill is based on the capabilities you use. -When you use Elastic Observability, your bill is calculated based on data volume, which has these components: +When you use {obs-serverless}, your bill is calculated based on data volume, which has these components: * **Ingest** — Measured by the number of GB of log/event/info data that you send to your Observability project over the course of a month. * **Storage/Retention** — This is known as Search AI Lake. @@ -18,4 +18,4 @@ and Ping (lightweight) tests have an all-you-can-use model per location used. For more information, refer to <>. -For detailed Observability serverless project rates, check the https://www.elastic.co/pricing/serverless-observability[Observability Serverless pricing page]. +For detailed {obs-serverless} project rates, check the https://www.elastic.co/pricing/serverless-observability[{obs-serverless} pricing page]. diff --git a/docs/en/serverless/reference/elastic-entity-model.asciidoc b/docs/en/serverless/reference/elastic-entity-model.asciidoc index ecd42912c7..fdc54c861d 100644 --- a/docs/en/serverless/reference/elastic-entity-model.asciidoc +++ b/docs/en/serverless/reference/elastic-entity-model.asciidoc @@ -10,7 +10,7 @@ The Elastic Entity Model consists of: * an Entity Discovery Framework, which consists of {ref}/transforms.html[transforms] and {ref}/ingest.html[Ingest pipelines] that read from signal indices and write data to entity indices * a set of management APIs that empower entity-centric Elastic solution features and workflows -In Elastic Observability, +In {obs-serverless}, an _entity_ is an object of interest that can be associated with produced telemetry and identified as unique. Note that this definition is intentionally closely aligned to the work of the https://github.com/open-telemetry/oteps/blob/main/text/entities/0256-entities-data-model.md#data-model[OpenTelemetry Entities SIG]. Examples of entities include (but are not limited to) services, hosts, and containers. diff --git a/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc b/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc index f3b16c7e5c..e7c23f2dee 100644 --- a/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-get-started-project.asciidoc @@ -176,7 +176,7 @@ While inside the Synthetics project directory you can do two things with the `np ---- npx @elastic/synthetics journeys ---- -* Push all monitor configurations to an Elastic Observability project. +* Push all monitor configurations to an Observability project. Run the following command from inside your Synthetics project directory: + [source,sh] diff --git a/docs/en/serverless/synthetics/synthetics-settings.asciidoc b/docs/en/serverless/synthetics/synthetics-settings.asciidoc index 10cd52a559..77fd90b961 100644 --- a/docs/en/serverless/synthetics/synthetics-settings.asciidoc +++ b/docs/en/serverless/synthetics/synthetics-settings.asciidoc @@ -7,7 +7,7 @@ There are several Synthetics settings you can adjust in your Observability proje [[synthetics-settings-alerting]] == Alerting -Alerting enables you to detect complex conditions using **rules** across Observability apps +Alerting enables you to detect complex conditions using **rules** across {obs-serverless} and send a notification using **connectors**. When you create a new synthetic monitor, new default synthetics rules will be applied. diff --git a/docs/en/serverless/transclusion/apm/guide/diagrams/apm-otel-architecture.asciidoc b/docs/en/serverless/transclusion/apm/guide/diagrams/apm-otel-architecture.asciidoc index 808f874435..a3ce1a8c5f 100644 --- a/docs/en/serverless/transclusion/apm/guide/diagrams/apm-otel-architecture.asciidoc +++ b/docs/en/serverless/transclusion/apm/guide/diagrams/apm-otel-architecture.asciidoc @@ -8,7 +8,7 @@ // -// Elastic Observability +// {obs-serverless} // diff --git a/docs/en/serverless/transclusion/synthetics/global-managed-paid-for.asciidoc b/docs/en/serverless/transclusion/synthetics/global-managed-paid-for.asciidoc index f37cc26007..58a3530130 100644 --- a/docs/en/serverless/transclusion/synthetics/global-managed-paid-for.asciidoc +++ b/docs/en/serverless/transclusion/synthetics/global-managed-paid-for.asciidoc @@ -1,2 +1,2 @@ Executing synthetic tests on Elastic's global managed testing infrastructure incurs an additional charge. Tests are charged under one of two new billing dimensions depending on the monitor type. For _browser monitor_ usage, there is a fee per test run. For _lightweight monitor_ usage, there is a fee per region in which you run any monitors regardless of the number of test runs. -For more details, refer to the https://www.elastic.co/pricing/serverless-observability[Observability Serverless pricing page]. +For more details, refer to the https://www.elastic.co/pricing/serverless-observability[{obs-serverless} pricing page]. diff --git a/docs/en/serverless/what-is-observability-serverless.asciidoc b/docs/en/serverless/what-is-observability-serverless.asciidoc index d75b81b35a..42474c247a 100644 --- a/docs/en/serverless/what-is-observability-serverless.asciidoc +++ b/docs/en/serverless/what-is-observability-serverless.asciidoc @@ -1,6 +1,6 @@ // :keywords: serverless, observability, overview -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. +{obs-serverless} 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. Not using serverless? Go to the {observability-guide}/index.html[Elastic Observability docs]. @@ -10,9 +10,9 @@ Not using serverless? Go to the {observability-guide}/index.html[Elastic Observa * <>: Discover more about our observability features and how to get started. * <>: Scan your host to detect and collect logs and metrics. * <>: Create the Kubernetes resources that are required to monitor your cluster infrastructure. -* <>: Add your log data to Elastic Observability and start exploring your logs. +* <>: Add your log data to {obs-serverless} and start exploring your logs. * <>: Collect Application Performance Monitoring (APM) data and visualize it in real time. -* <>: Add your metrics data to Elastic Observability and visualize it in real time. +* <>: Add your metrics data to {obs-serverless} and visualize it in real time. [discrete] == How to