elastic · colleenmcginnis · Dec 3, 2024 · Nov 27, 2024
@@ -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 <<observability-apm-agents-opentelemetry-opentelemetry-native-support,Elastic's native OTLP support>> instead.
+(which is different from the legacy exporter mentioned above) is not intended to be used with Elastic APM and {obs-serverless}. Use <<observability-apm-agents-opentelemetry-opentelemetry-native-support,Elastic's native OTLP support>> instead.
@@ -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?
 

@@ -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

@@ -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.

@@ -22,15 +22,15 @@ 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**.
 
 [discrete]
 [[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}

@@ -2,15 +2,15 @@ include::{asciidoc-dir}/../../shared/versions/stack/current.asciidoc[]
 include::{asciidoc-dir}/../../shared/attributes.asciidoc[]
 
 [[what-is-observability-serverless]]
-== Elastic Observability serverless
+== {obs-serverless}
 
 ++++
 <titleabbrev>Elastic Observability</titleabbrev>
 ++++
 
 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?

@@ -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:
 
 * <<observability-get-started-with-logs,Get started with system logs>>: Onboard system log data from a machine or server.
 * <<observability-stream-log-files,Stream any log file>>: Send log files to your Observability project using a standalone {agent}.

@@ -1,5 +1,5 @@
 [[observability-get-started]]
-= Get started with Elastic Observability
+= Get started with {obs-serverless}
 
 ++++
 <titleabbrev>Get started</titleabbrev>
@@ -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:
 
 * <<observability-alerting>>
 * <<observability-slos>>
@@ -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 <<general-serverless-billing>>.
 
-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].
@@ -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.

@@ -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]

@@ -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.

@@ -8,7 +8,7 @@
 
 // <rect x="506" y="182.744" width="577" height="344.513" rx="7" fill="white" fill-opacity="0.5" stroke="#69707D" stroke-width="2" stroke-linejoin="round" stroke-dasharray="4 4"/>
 
-// <text fill="#343741" xml:space="preserve" style="white-space: pre" font-family="Inter" font-size="24" font-weight="bold" letter-spacing="0em"><tspan x="710.083" y="166.505">Elastic Observability</tspan></text>
+// <text fill="#343741" xml:space="preserve" style="white-space: pre" font-family="Inter" font-size="24" font-weight="bold" letter-spacing="0em"><tspan x="710.083" y="166.505">{obs-serverless}</tspan></text>
 
 // <rect x="900" y="198.722" width="166.474" height="310.56" rx="7" fill="#0077CC" fill-opacity="0.24" stroke="#69707D" stroke-width="2" stroke-linejoin="round"/>
 

@@ -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].
@@ -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
 * <<observability-get-started,*Get started*>>: Discover more about our observability features and how to get started.
 * <<observability-quickstarts-monitor-hosts-with-elastic-agent,*Quickstart: Monitor hosts with Elastic Agent*>>: Scan your host to detect and collect logs and metrics.
 * <<observability-quickstarts-k8s-logs-metrics,*Quickstart: Monitor your Kubernetes cluster with Elastic Agent*>>: Create the Kubernetes resources that are required to monitor your cluster infrastructure.
-* <<observability-get-started-with-logs,*Get started with Logs*>>: Add your log data to Elastic Observability and start exploring your logs.
+* <<observability-get-started-with-logs,*Get started with Logs*>>: Add your log data to {obs-serverless} and start exploring your logs.
 * <<observability-apm-get-started,*Get started with traces and APM*>>: Collect Application Performance Monitoring (APM) data and visualize it in real time.
-* <<observability-get-started-with-metrics,*Get started with metrics*>>: Add your metrics data to Elastic Observability and visualize it in real time.
+* <<observability-get-started-with-metrics,*Get started with metrics*>>: Add your metrics data to {obs-serverless} and visualize it in real time.
 
 [discrete]
 == How to