diff --git a/deploy-manage/deploy/elastic-cloud/create-serverless-project.md b/deploy-manage/deploy/elastic-cloud/create-serverless-project.md index a0f69cf570..71ed9fab68 100644 --- a/deploy-manage/deploy/elastic-cloud/create-serverless-project.md +++ b/deploy-manage/deploy/elastic-cloud/create-serverless-project.md @@ -20,6 +20,6 @@ Choose the type of project that matches your needs and we’ll help you get star | --- | --- | | | | | ![elasticsearch](../../images/64x64_Color_elasticsearch-logo-color-64px.png "elasticsearch =50%") | **Elasticsearch**
Build custom search applications with {{es}}.

[**View guide →**](/solutions/search/serverless-elasticsearch-get-started.md)
| -| ![observability](../../images/64x64_Color_observability-logo-color-64px.png "observability =50%") | **Observability**
Monitor applications and systems with Elastic Observability.

[**View guide →**](/solutions/observability/get-started/create-an-observability-project.md)
| +| ![observability](../../images/64x64_Color_observability-logo-color-64px.png "observability =50%") | **Observability**
Monitor applications and systems with Elastic Observability.

[**View guide →**](/solutions/observability/get-started.md)
| | ![security](../../images/64x64_Color_security-logo-color-64px.png "security =50%") | **Security**
Detect, investigate, and respond to threats with Elastic Security.

[**View guide →**](/solutions/security/get-started/create-security-project.md)
| | | | \ No newline at end of file diff --git a/deploy-manage/deploy/elastic-cloud/serverless.md b/deploy-manage/deploy/elastic-cloud/serverless.md index 9f4304ab88..998400e18d 100644 --- a/deploy-manage/deploy/elastic-cloud/serverless.md +++ b/deploy-manage/deploy/elastic-cloud/serverless.md @@ -28,7 +28,7 @@ There are differences between {{es-serverless}} and {{ech}}, for a list of diffe Elastic provides three serverless solutions available on {{ecloud}}. Follow these guides to get started with your serverless project: * **[{{es-serverless}}](../../../solutions/search/serverless-elasticsearch-get-started.md)**: Build powerful applications and search experiences using a rich ecosystem of vector search capabilities, APIs, and libraries. -* **[{{obs-serverless}}](../../../solutions/observability/get-started/create-an-observability-project.md)**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data. +* **[{{obs-serverless}}](../../../solutions/observability/get-started.md)**: Monitor your own platforms and services using powerful machine learning and analytics tools with your logs, metrics, traces, and APM data. * **[{{sec-serverless}}](../../../solutions/security/get-started/create-security-project.md)**: Detect, investigate, and respond to threats with SIEM, endpoint protection, and AI-powered analytics capabilities. Afterwards, you can: diff --git a/manage-data/ingest/ingest-reference-architectures/agent-to-es.md b/manage-data/ingest/ingest-reference-architectures/agent-to-es.md index 2690ca8013..698a5162b7 100644 --- a/manage-data/ingest/ingest-reference-architectures/agent-to-es.md +++ b/manage-data/ingest/ingest-reference-architectures/agent-to-es.md @@ -35,7 +35,7 @@ Info on {{es}}: This basic architecture is a common approach for ingesting data for the [Elastic Observability](https://www.elastic.co/observability) and [Elastic Security](https://www.elastic.co/security) solutions: -* [Elastic Observability tutorials](/solutions/observability/get-started.md#_get_started_with_other_features) +* [Elastic Observability tutorials](/solutions/observability/get-started.md) * [Ingest data to Elastic Security](../../../solutions/security/get-started/ingest-data-to-elastic-security.md) diff --git a/redirects.yml b/redirects.yml index 02b5657cb6..f8aa702bfe 100644 --- a/redirects.yml +++ b/redirects.yml @@ -187,7 +187,7 @@ redirects: 'solutions/observability/apps/analyze-monitors.md': 'solutions/observability/uptime/analyze-monitors.md' 'solutions/observability/apps/inspect-uptime-duration-anomalies.md': 'solutions/observability/uptime/inspect-duration-anomalies.md' 'solutions/observability/apps/configure-settings.md': 'solutions/observability/uptime/configure-settings.md' - 'solutions/observability/apps/tutorial-monitor-java-application.md': 'solutions/observability/applications/tutorial-monitor-java-application.md' + 'solutions/observability/apps/tutorial-monitor-java-application.md': 'solutions/observability/get-started/other-tutorials/tutorial-monitor-java-application.md' # we can't redirect to the search-ui book so this is the next best option 'reference/search/index.md': 'reference/index.md' @@ -207,6 +207,8 @@ redirects: 'troubleshoot/elasticsearch/elasticsearch-client-net-api/logging.md': 'troubleshoot/elasticsearch/clients.md' 'troubleshoot/elasticsearch/elasticsearch-client-net-api/net.md': 'troubleshoot/elasticsearch/clients.md' 'troubleshoot/elasticsearch/elasticsearch-client-ruby-api/ruby.md': 'troubleshoot/elasticsearch/clients.md' - + 'solutions/observability/get-started/add-data-from-splunk.md': 'solutions/observability/get-started/other-tutorials/add-data-from-splunk.md' + 'solutions/observability/get-started/create-an-observability-project.md': 'solutions/observability/get-started.md' + 'solutions/observability/get-started/get-started-with-dashboards.md': 'solutions/observability/get-started.md' # Related to https://github.com/elastic/docs-content/pull/1329 'manage-data/ingest/transform-enrich/ingest-pipelines-serverless.md': 'manage-data/ingest/transform-enrich/ingest-pipelines.md' diff --git a/reference/observability/index.md b/reference/observability/index.md index 3f54ce3bd6..6b21074cd3 100644 --- a/reference/observability/index.md +++ b/reference/observability/index.md @@ -9,6 +9,7 @@ products: - id: cloud-serverless - id: observability --- + # Observability This section contains reference information for Elastic Observability features, including: @@ -20,3 +21,10 @@ To interface with Elastic Observability features, you can use the following APIs * [Observability Intake Serverless APIs](https://www.elastic.co/docs/api/doc/observability-serverless) * [Service level objectives](https://www.elastic.co/docs/api/doc/kibana/group/endpoint-slo) + +You can also browse reference documentation for the following components: + +- [Elastic Distributions of OpenTelemetry (EDOT)](opentelemetry://reference/index.md) +- [Fleet and Elastic Agent](/reference/fleet/index.md) +- [Elastic APM](/reference/apm/observability/apm.md) +- [Elastic APM agents](/reference/apm-agents/index.md) \ No newline at end of file diff --git a/solutions/images/Monitor_drill_down_1.png b/solutions/images/Monitor_drill_down_1.png new file mode 100644 index 0000000000..d0ecc82841 Binary files /dev/null and b/solutions/images/Monitor_drill_down_1.png differ diff --git a/solutions/images/Monitor_drill_down_2.png b/solutions/images/Monitor_drill_down_2.png new file mode 100644 index 0000000000..dc7139b7e6 Binary files /dev/null and b/solutions/images/Monitor_drill_down_2.png differ diff --git a/solutions/images/Synthetic-Error_details.png b/solutions/images/Synthetic-Error_details.png new file mode 100644 index 0000000000..16234f6390 Binary files /dev/null and b/solutions/images/Synthetic-Error_details.png differ diff --git a/solutions/images/observability-get-started.svg b/solutions/images/observability-get-started.svg deleted file mode 100644 index 487355b2f9..0000000000 --- a/solutions/images/observability-get-started.svg +++ /dev/null @@ -1,21 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - diff --git a/solutions/images/observability-quickstart-k8s-otel-entry-point.png b/solutions/images/observability-quickstart-k8s-otel-entry-point.png index 739832bac2..13e43af9e7 100644 Binary files a/solutions/images/observability-quickstart-k8s-otel-entry-point.png and b/solutions/images/observability-quickstart-k8s-otel-entry-point.png differ diff --git a/solutions/images/observability-quickstart-monitor-hosts-otel-entry-point.png b/solutions/images/observability-quickstart-monitor-hosts-otel-entry-point.png index fc5a000c9e..a7d652f757 100644 Binary files a/solutions/images/observability-quickstart-monitor-hosts-otel-entry-point.png and b/solutions/images/observability-quickstart-monitor-hosts-otel-entry-point.png differ diff --git a/solutions/images/screenshot-observability-monitoring-k8s-kubernetes-logs-can-be-searched.png b/solutions/images/screenshot-observability-monitoring-k8s-kubernetes-logs-can-be-searched.png new file mode 100644 index 0000000000..7d29ac561e Binary files /dev/null and b/solutions/images/screenshot-observability-monitoring-k8s-kubernetes-logs-can-be-searched.png differ diff --git a/solutions/images/screenshot-observability-monitoring-k8s-kubernetes-overview-cluster.png b/solutions/images/screenshot-observability-monitoring-k8s-kubernetes-overview-cluster.png new file mode 100644 index 0000000000..00ae55c958 Binary files /dev/null and b/solutions/images/screenshot-observability-monitoring-k8s-kubernetes-overview-cluster.png differ diff --git a/solutions/images/screenshot-observability-monitoring-k8s-leverage-machine-learning-to-uncover-insights.png b/solutions/images/screenshot-observability-monitoring-k8s-leverage-machine-learning-to-uncover-insights.png new file mode 100644 index 0000000000..aa7d3f7954 Binary files /dev/null and b/solutions/images/screenshot-observability-monitoring-k8s-leverage-machine-learning-to-uncover-insights.png differ diff --git a/solutions/images/synth-monitors.png b/solutions/images/synth-monitors.png new file mode 100644 index 0000000000..7fe5f9a1cb Binary files /dev/null and b/solutions/images/synth-monitors.png differ diff --git a/solutions/images/synthetics-create-browser-monitor.png b/solutions/images/synthetics-create-browser-monitor.png new file mode 100644 index 0000000000..0fe847934f Binary files /dev/null and b/solutions/images/synthetics-create-browser-monitor.png differ diff --git a/solutions/observability.md b/solutions/observability.md index d0a6829782..714298965a 100644 --- a/solutions/observability.md +++ b/solutions/observability.md @@ -15,39 +15,36 @@ products: # Observability -{{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. +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. -## Get started [_get_started] +For a complete overview, refer to [**What is Elastic {{observability}}**](/solutions/observability/get-started/what-is-elastic-observability.md). -Read the following quickstart guides to get started with {{observability}}: +## Get started [_get_started] -* [**Get started**](/solutions/observability/get-started.md): Discover more about our observability features and how to get started. +To start your {{observability}} journey, read the [**Get started**](/solutions/observability/get-started.md) guide, which presents all the essential steps, with links to valuable resources. You can also browse the {{observability}} [**Quickstart guides**](/solutions/observability/get-started/quickstarts.md). -Ingest observability data using OpenTelemetry: +## {{observability}} features [_observability_features] -* [**Quickstart: Monitor hosts with OpenTelemetry**](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md) -* [**Quickstart: Monitor Kubernetes with OpenTelemetry**](/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md) -* [**Quickstart: Send data to the Elastic Cloud Managed OTLP Endpoint**](/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md) +Read the documentation for each of the {{observability}} features to learn more about how to use them. -Use the Elastic Agent to ingest data: +- [Log monitoring](/solutions/observability/logs.md) +- [Infrastructure and hosts monitoring](/solutions/observability/infra-and-hosts.md) +- [Applications performance monitoring](/solutions/observability/apm/index.md) +- [Synthetics monitoring](/solutions/observability/synthetics/index.md) +- [Incident management](/solutions/observability/incident-management.md) +- [AI Assistant](/solutions/observability/observability-ai-assistant.md) -* [**Quickstart: Monitor hosts with Elastic Agent**](/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md): Scan your host to detect and collect logs and metrics. -* [**Quickstart: Monitor your Kubernetes cluster with Elastic Agent**](/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md): Create the Kubernetes resources that are required to monitor your cluster infrastructure. +## Reference documentation [_reference_documentation] -Explore your data: +The {{observability}} reference documentation is available in the [Elastic reference documentation](/reference/observability/index.md). -* [**Get started with Logs**](/solutions/observability/logs/get-started-with-system-logs.md): Add your log data to {{observability}} and start exploring your logs. -* [**Get started with traces and APM**](/solutions/observability/apm/get-started.md): Collect Application Performance Monitoring (APM) data and visualize it in real time. -* [**Get started with metrics**](/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md): Add your metrics data to {{observability}} and visualize it in real time. +You can also browse reference documentation for the following components: -## How to [_how_to] +- [Elastic Distributions of OpenTelemetry (EDOT)](opentelemetry://reference/index.md) +- [Fleet and Elastic Agent](/reference/fleet/index.md) +- [Elastic APM](/reference/apm/observability/apm.md) +- [Elastic APM agents](/reference/apm-agents/index.md) -After you've collected your data, you can: +## Release notes [_release_notes] -* [**Explore log data**](/solutions/observability/logs/discover-logs.md): Use Discover to explore your log data. -* [**Trigger alerts and triage problems**](/solutions/observability/incident-management/create-manage-rules.md): Create rules to detect complex conditions and trigger alerts. -* [**Track and deliver on your SLOs**](/solutions/observability/incident-management/service-level-objectives-slos.md): Measure key metrics important to the business. -* [**Detect anomalies and spikes**](/explore-analyze/machine-learning/anomaly-detection.md): Find unusual behavior in time series data. -* [**Monitor application performance**](/solutions/observability/apm/index.md): Monitor your software services and applications in real time. -* [**Integrate with OpenTelemetry**](/solutions/observability/apm/use-opentelemetry-with-apm.md): Reuse existing APM instrumentation to capture logs, traces, and metrics. -* [**Monitor your hosts and services**](/solutions/observability/infra-and-hosts/analyze-compare-hosts.md): Get a metrics-driven view of your hosts backed by an interface called Lens. \ No newline at end of file +Browse the latest [{{observability}} release notes](/release-notes/elastic-observability/index.md) for more information on new features, enhancements, and fixes. diff --git a/solutions/observability/apm/get-started-serverless.md b/solutions/observability/apm/get-started-serverless.md index c6a68697e0..4727e6fbb9 100644 --- a/solutions/observability/apm/get-started-serverless.md +++ b/solutions/observability/apm/get-started-serverless.md @@ -24,7 +24,7 @@ You’ll use APM agents to send APM data from your application to Elastic. Elast To send APM data to Elastic, you must install an APM agent and configure it to send data to your project: -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. To install and configure one or more APM agents, do one of following: * In your Observability project, go to **Add data** → **Application** → **Elastic APM** and follow the prompts. diff --git a/solutions/observability/applications/index.md b/solutions/observability/applications/index.md index 4c9c00386c..761c346491 100644 --- a/solutions/observability/applications/index.md +++ b/solutions/observability/applications/index.md @@ -25,4 +25,3 @@ Explore the topics in this section to learn how to observe and monitor software | [Synthetic monitoring](/solutions/observability/synthetics/index.md) | Monitor the availability of network endpoints and services. | | [Real user monitoring](/solutions/observability/applications/user-experience.md) | Quantify and analyze the perceived performance of your web application using real-world user experiences. | | [Uptime monitoring (deprecated)](/solutions/observability/uptime/index.md) | Periodically check the status of your services and applications. | -| [Tutorial: Monitor a Java application](/solutions/observability/applications/tutorial-monitor-java-application.md) | Monitor a Java application using Elastic Observability: Logs, Infrastructure metrics, APM, and Uptime. | diff --git a/solutions/observability/get-started.md b/solutions/observability/get-started.md index a4127c9933..3817fac1da 100644 --- a/solutions/observability/get-started.md +++ b/solutions/observability/get-started.md @@ -12,73 +12,202 @@ products: - id: observability --- -# Get started with Elastic Observability [observability-get-started] +# Get started with Elastic {{observability}} [observability-get-started] +New to Elastic {{observability}}? Discover more about our observability features and how to get started. The following instructions will guide you through setting up your first Elastic {{observability}} deployment, collecting data from infrastructure and applications, and exploring your data. -New to Elastic {{observability}}? Discover more about our observability features and how to get started. +## Get started with your use case [get-started-with-use-case] +Learn how to spin up a deployment on {{ech}} or create an {{obs-serverless}} project and use Elastic {{observability}} to gain deeper insight into the behavior of your applications and systems. -## Learn about Elastic {{observability}} [_learn_about_elastic_observability] +:::::::{stepper} -Learn about key features available to help you get value from your observability data: +::::::{step} Create an Observability project -* [What is Elastic {{observability}}?](/solutions/observability/get-started/what-is-elastic-observability.md) -* [What’s new in Elastic Stack](/release-notes/elastic-observability/index.md) -* [{{obs-serverless}} billing dimensions](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md) +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. +::::{dropdown} Steps for creating a project +:::{note} +The **Admin** role or higher is required to create projects. Refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/manage-users.md#general-assign-user-roles). +::: -## Get started with your use case [get-started-with-use-case] +1. Navigate to [cloud.elastic.co](https://cloud.elastic.co/) and log in to your account, or create one. +2. Select **Create serverless project**. +3. Under **Elastic for Observability**, select **Next**. +4. Enter a name for your project. +5. (Optional) Select **Edit settings** to change your project settings: + + * **Cloud provider**: The cloud platform where you’ll deploy your project. We currently support Amazon Web Services (AWS). + * **Region**: The [region](/deploy-manage/deploy/elastic-cloud/regions.md) where your project will live. + +6. Select **Create project**. It takes a few minutes to create your project. +7. When the project is ready, click **Continue**. + +For other types of deployments, refer to [Deploy](/deploy-manage/deploy.md). For a breakdown of the differences between deployment types and what they support, refer to [Detailed deployment comparison](/deploy-manage/deploy/deployment-comparison.md). +:::: +:::::: + +::::::{step} Collect infrastructure logs and metrics + +Bring logs and metrics from your hosts and services into Elastic {{observability}} to monitor the health and performance of your infrastructure. You can collect this data from hosts, containers, Kubernetes, and Cloud services. + +:::::{dropdown} Steps for collecting infrastructure logs and metrics + +::::{tab-set} +:::{tab-item} Hosts + +Elastic {{observability}} can collect telemetry data from hosts, containers, and Kubernetes through the EDOT Collector or the Elastic Agent. + +1. Select **Add data** from the main menu and then select **Host**. +2. Select one of these options: + * **OpenTelemetry: Full Observability**: Collect native OpenTelemetry metrics and logs. + * **Elastic Agent: Logs & Metrics**: Bring data from Elastic integrations. +3. Follow the instructions for your platform. + +For an overview of the Elastic Distribution of OpenTelemetry Collector, refer to [Elastic Distribution of OpenTelemetry (EDOT)](opentelemetry://reference/index.md). + +::: + +:::{tab-item} Kubernetes + +Elastic {{observability}} can collect telemetry data from Kubernetes through the Elastic Distribution of OpenTelemetry Collector or the Elastic Agent. + +1. Select **Add data** from the main menu and then select **Kubernetes**. +2. Select one of these options: + * **OpenTelemetry: Full Observability**: Collect native OpenTelemetry metrics and logs. + * **Elastic Agent: Logs & Metrics**: Bring data from Elastic integrations. +3. Follow the instructions for your platform. + +For an overview of EDOT, refer to [Elastic Distribution of OpenTelemetry (EDOT)](opentelemetry://reference/index.md). + +::: + +:::{tab-item} Integrations + +Elastic {{observability}} can collect telemetry data from services through Elastic integrations. + +1. Select **Add data** from the main menu. +2. In **Search through other ways of ingesting data**, type the name of an integration (for example, NGINX). +3. Select the integration you want to add. +4. Select **Add**. +::: + +:::{tab-item} Cloud + +Elastic {{observability}} can collect telemetry data from cloud services through Elastic integrations. + +1. Select **Add data** from the main menu and then select **Cloud**. +2. Select your Cloud provider to view the collection of integrations available for that provider. +3. Select the integration you want to add. +4. Select **Add**. +::: + +:::{tab-item} CI/CD + +Elastic {{observability}} can collect telemetry data from CI/CD pipelines using OpenTelemetry. + +Refer to [CI/CD](/solutions/observability/cicd.md) for more information. +::: + +:::{tab-item} LLMs -Learn how to spin up a deployment on {{ech}} or create an Observability Serverless project and use Elastic Observability to gain deeper insight into the behavior of your applications and systems. +Elastic provides a powerful LLM observability framework including key metrics, logs, and traces, along with pre-configured, out-of-the-box dashboards that deliver deep insights into model prompts and responses, performance, usage, and costs. -:::{image} /solutions/images/observability-get-started.svg -:alt: get started +Refer to [LLM observability](/solutions/observability/applications/llm-observability.md) for more information. ::: -1. **Choose your source.** Elastic integrates with hundreds of data sources for unified visibility across all your applications and systems. -2. **Ingest your data.** Turn-key integrations provide a repeatable workflow to ingest data from all your sources: you install an integration, configure it, and deploy an agent to collect your data. -3. **View your data.** Navigate seamlessly between Observabilty UIs and dashboards to identify and resolve problems quickly. -4. **Customize.** Expand your deployment and add features like alerting and anomaly detection. +::::: +:::::: + +::::::{step} Collect application traces, metrics, and logs + +Bring traces, logs, and metrics into [Elastic APM](/solutions/observability/apm/index.md) to help you troubleshoot and optimize your applications. You can collect this data using OpenTelemetry or APM Server. -To get started with on serverless, [create an Observability project](/solutions/observability/get-started/create-an-observability-project.md), then follow one of our [quickstarts](/solutions/observability/get-started.md#quickstarts-overview) to learn how to ingest and visualize your observability data. +:::::{dropdown} Steps for collecting application traces, metrics, and logs -### Quickstarts [quickstarts-overview] +::::{tab-set} +:::{tab-item} OpenTelemetry + +The [Elastic Distribution of OpenTelemetry (EDOT) SDKs](opentelemetry://reference/edot-sdks/index.md) facilitate the collection of traces, metrics, and logs in OpenTelemetry format into [Elastic APM](/solutions/observability/apm/index.md). + +1. Select **Add data** from the main menu and then select **Application**. +2. Select **OpenTelemetry**. +3. Follow the instructions for your platform. +::: + +:::{tab-item} APM agents + +Use the [APM agents](/solutions/observability/apm/elastic-apm-agents.md) to collect traces, metrics, and logs through [APM Server](/solutions/observability/apm/configure-apm-server.md). + +1. Select **Add data** from the main menu and then select **Application**. +2. Select **Elastic APM**. +3. Select the tab for your language or framework. +4. Follow the instructions in the tab. +::: +::::: +:::::: -Our quickstarts dramatically reduce your time-to-value by offering a fast path to ingest and visualize your Observability data. Each quickstart provides: +::::::{step} Add Synthetics monitoring -* A highly opinionated, fast path to data ingestion -* Sensible configuration defaults with minimal configuration required -* Auto-detection of logs and metrics for monitoring hosts -* Quick access to related dashboards and visualizations +[Synthetics monitoring](/solutions/observability/synthetics/index.md) lets you simulate, track, and visualize user journeys to catch performance, availability, and functionality issues in your services and applications. It periodically checks the status of your services and applications. -Follow the steps in these guides to get started quickly: +:::::{dropdown} Steps for adding Synthetics monitoring +1. Select **Add data** from the main menu and then select **Application**. +2. Select **Synthetic monitor**. +3. Select a [monitor type](/solutions/observability/synthetics/index.md). +4. Fill out the details. +5. (Optional) Add a [Playwright](https://playwright.dev/) script. +6. Test and create your monitor. +:::: +:::::: -* [**Quickstart: Monitor hosts with OpenTelemetry**](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md) -* [**Quickstart: Monitor Kubernetes with OpenTelemetry**](/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md) -* [**Quickstart: Send data to the Elastic Cloud Managed OTLP Endpoint**](/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md) -* [**Get started with Logs**](/solutions/observability/logs/get-started-with-system-logs.md): Add your log data to {{observability}} and start exploring your logs. -* [**Get started with traces and APM**](/solutions/observability/apm/get-started.md): Collect Application Performance Monitoring (APM) data and visualize it in real time. -* [**Get started with metrics**](/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md): Add your metrics data to {{observability}} and visualize it in real time. +::::::{step} Explore your logs, metrics, and traces -### Get started with other features [_get_started_with_other_features] +After you've onboarded your data, you can explore it in the following Elastic {{observability}} UIs, or query it using [query languages](elasticsearch://reference/query-languages/index.md). -Want to use {{fleet}} or some other feature not covered in the quickstarts? Follow the steps in these guides to get started: +- [Explore your logs](/solutions/observability/logs/explore-logs.md) in the Logs UI. +- [Analyze infrastructure and host metrics](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) in the Infrastructure UI. +- [View and analyze APM data](/solutions/observability/apm/view-analyze-data.md) in the Applications UI. +- Use the [Elastic Query Language ({{esql}})](/explore-analyze/discover/try-esql.md) to search and filter your data. -% Stateful only for Universal profiling +:::::: -* [Get started with system metrics](/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md) -* [Get started with application traces and APM](/solutions/observability/apm/get-started-fleet-managed-apm-server.md) -* [Get started with synthetic monitoring](/solutions/observability/synthetics/index.md) -* [Get started with Universal Profiling](/solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md) +::::::{step} Create your first dashboards -## Additional guides [_additional_guides] +Elastic provides a wide range of prebuilt dashboards for visualizing observability data from a variety of sources. These dashboards are loaded automatically when you install [Elastic integrations](https://docs.elastic.co/integrations). You can also create new dashboards and visualizations based on your data views. -Ready to dig into more features of Elastic Observability? See these guides: +To create a new dashboard, select **Create Dashboard** and begin adding visualizations. You can create charts, graphs, maps, tables, and other types of visualizations from your data, or you can add visualizations from the library. You can also add other types of panels, such as filters and controls. -* [Create an alert](/solutions/observability/incident-management/alerting.md) -* [Create a service-level objective (SLO)](/solutions/observability/incident-management/create-an-slo.md) +For more information about creating dashboards, refer to [Create your first dashboard](/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md). -## Related content for Elastic Stack [_related_content] +:::::: -* [Starting with the {{es}} Platform and its Solutions](/get-started/index.md) for new users -* [Adding data to {{es}}](/manage-data/ingest.md) for other ways to ingest data \ No newline at end of file +::::::{step} Set up alerts and SLOs + +Elastic {{observability}} lets you define rules of different types which detect complex conditions and trigger relevant actions. {{observability}} can send alerts to email, Slack, and other third-party systems. Refer to [Create and manage rules](/solutions/observability/incident-management/create-manage-rules.md) to get started. + +{{observability}} also lets you define Service Level Objectives (SLOs) to set clear, measurable targets for your service performance, based on factors like availability, response times, error rates, and other key metrics. Refer to [Create and manage SLOs](/solutions/observability/incident-management/service-level-objectives-slos.md) to get started. + +:::::: + +::::::: + +## Related resources + +Use these resources to learn more about {{observability}} or get started in a different way. + +### Quickstarts + +Quickstarts are compact hands-on guides that help you experiment with {{observability}} features. Each quickstart provides a highly opinionated, fast path to data ingestion, with minimal configuration required. + +[Browse the Elastic {{observability}} quickstarts](/solutions/observability/get-started/quickstarts.md) to get started with specific use cases. + +### Observability integrations + +Many [{{observability}} integrations](https://www.elastic.co/integrations/data-integrations?solution=observability) are available to collect and process your data. Refer to [Elastic integrations](https://www.elastic.co/docs/reference/integrations) for more information. + +### Other resources + +* [What's Elastic {{observability}}](/solutions/observability/get-started/what-is-elastic-observability.md) +* [What’s new in Elastic Stack](/release-notes/elastic-observability/index.md) +* [{{obs-serverless}} billing dimensions](/deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md) \ No newline at end of file diff --git a/solutions/observability/get-started/create-an-observability-project.md b/solutions/observability/get-started/create-an-observability-project.md deleted file mode 100644 index 25911d9f1c..0000000000 --- a/solutions/observability/get-started/create-an-observability-project.md +++ /dev/null @@ -1,52 +0,0 @@ ---- -navigation_title: Create an Observability project -mapped_pages: - - https://www.elastic.co/guide/en/serverless/current/observability-create-an-observability-project.html -applies_to: - serverless: -products: - - id: cloud-serverless ---- - -% Serverless only - -# Create an observability project [observability-create-an-observability-project] - - -::::{note} - -The **Admin** role or higher is required to create projects. To learn more, refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/manage-users.md#general-assign-user-roles). - -:::: - - -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. - -1. Navigate to [cloud.elastic.co](https://cloud.elastic.co/) and log in to your account. -2. Within **Serverless projects**, click **Create project**. -3. Under **Observability**, click **Next**. -4. Enter a name for your project. -5. (Optional) Click **Edit settings** to change your project settings: - - * **Cloud provider**: The cloud platform where you’ll deploy your project. We currently support Amazon Web Services (AWS). - * **Region**: The [region](/deploy-manage/deploy/elastic-cloud/regions.md) where your project will live. - -6. Click **Create project**. It takes a few minutes to create your project. -7. When the project is ready, click **Continue**. - -From here, you can start adding logs and other observability data. - -::::{tip} -To return to the onboarding page later, select **Add data** from the main menu. - -:::: - - - -## Next steps [observability-create-an-observability-project-next-steps] - -Learn how to add data to your project and start using {{obs-serverless}} features: - -* [Get started with system logs](../logs/get-started-with-system-logs.md) -* [Get started with traces and APM](/solutions/observability/apm/get-started.md) -* [Get started with system metrics](../infra-and-hosts/get-started-with-system-metrics.md) diff --git a/solutions/observability/get-started/get-started-with-dashboards.md b/solutions/observability/get-started/get-started-with-dashboards.md deleted file mode 100644 index 78558dd452..0000000000 --- a/solutions/observability/get-started/get-started-with-dashboards.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/serverless/current/observability-dashboards.html -applies_to: - serverless: -products: - - id: cloud-serverless ---- - -# Get started with dashboards [observability-dashboards] - -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 [Elastic integrations](https://docs.elastic.co/integrations). - -You can also create new dashboards and visualizations based on your data views to get a full picture of your data. - -In your Observability project, go to **Dashboards** to see installed dashboards or create your own. This example shows dashboards loaded by the System integration: - -:::{image} /solutions/images/serverless-dashboards.png -:alt: Screenshot showing list of System dashboards -:screenshot: -::: - -Notice you can filter the list of dashboards: - -* Use the text search field to filter by name or description. -* Use the **Tags** menu to filter by tag. To create a new tag or edit existing tags, click **Manage tags**. -* Click a dashboard’s tags to toggle filtering for each tag. - - -## Create new dashboards [observability-dashboards-create-new-dashboards] - -To create a new dashboard, click **Create Dashboard** and begin adding visualizations. You can create charts, graphs, maps, tables, and other types of visualizations from your data, or you can add visualizations from the library. - -You can also add other types of panels — such as filters, links, and text — and add controls like time sliders. - -For more information about creating dashboards, refer to [Create your first dashboard](/explore-analyze/dashboards/create-dashboard-of-panels-with-web-server-data.md). - -::::{note} -The tutorial about creating your first dashboard is written for {{kib}} users, but the steps for serverless are very similar. To load the sample data in serverless, go to **Project Settings** → **Integrations** in the navigation pane, then search for "sample data". - -:::: diff --git a/solutions/observability/get-started/add-data-from-splunk.md b/solutions/observability/get-started/other-tutorials/add-data-from-splunk.md similarity index 97% rename from solutions/observability/get-started/add-data-from-splunk.md rename to solutions/observability/get-started/other-tutorials/add-data-from-splunk.md index fd383dc79a..6d5ff04b8b 100644 --- a/solutions/observability/get-started/add-data-from-splunk.md +++ b/solutions/observability/get-started/other-tutorials/add-data-from-splunk.md @@ -40,7 +40,7 @@ To get started quickly, create an {{ech}} deployment and host it on AWS, GCP, or ## Step 1: Add integration [splunk-step-one] -Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for and add the nginx integration. Refer to [Get started with system metrics](../infra-and-hosts/get-started-with-system-metrics.md) for detailed steps about adding integrations. +Find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Search for and add the nginx integration. Refer to [Get started with system metrics](../../infra-and-hosts/get-started-with-system-metrics.md) for detailed steps about adding integrations. ## Step 2: Enable Collect logs from third-party REST API [splunk-step-two] diff --git a/solutions/observability/get-started/other-tutorials/index.md b/solutions/observability/get-started/other-tutorials/index.md new file mode 100644 index 0000000000..b770f7622b --- /dev/null +++ b/solutions/observability/get-started/other-tutorials/index.md @@ -0,0 +1,18 @@ +--- +navigation_title: Other Observability tutorials +applies_to: + stack: ga + serverless: ga +products: + - id: cloud-serverless + - id: observability +--- + +# {{observability}} tutorials + +The following tutorials explore various use cases and {{observability}} scenarios. + +- [Tutorial: Monitor a Java application](/solutions/observability/get-started/other-tutorials/tutorial-monitor-java-application.md) +- [Tutorial: Add data from Splunk](/solutions/observability/get-started/other-tutorials/add-data-from-splunk.md) + +To get started with {{observability}}, refer to [Get started with Elastic {{observability}}](/solutions/observability/get-started.md). \ No newline at end of file diff --git a/solutions/observability/applications/tutorial-monitor-java-application.md b/solutions/observability/get-started/other-tutorials/tutorial-monitor-java-application.md similarity index 99% rename from solutions/observability/applications/tutorial-monitor-java-application.md rename to solutions/observability/get-started/other-tutorials/tutorial-monitor-java-application.md index e3e099a99e..8bd55914bb 100644 --- a/solutions/observability/applications/tutorial-monitor-java-application.md +++ b/solutions/observability/get-started/other-tutorials/tutorial-monitor-java-application.md @@ -1912,5 +1912,5 @@ Do not underestimate the importance of this kind of monitoring. Also, consider t ## What’s next? [_whats_next] -For more information about using Elastic {{observability}}, see the [{{observability}} documentation](../get-started/what-is-elastic-observability.md). +For more information about using Elastic {{observability}}, see the [{{observability}} documentation](../what-is-elastic-observability.md). diff --git a/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md b/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md index 29779af1db..9ffb4f2924 100644 --- a/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md +++ b/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md @@ -1,4 +1,5 @@ --- +description: Learn how to use AWS Firehose to send logs and metrics to Elastic Observability for monitoring and analysis. mapped_pages: - https://www.elastic.co/guide/en/observability/current/collect-data-with-aws-firehose.html - https://www.elastic.co/guide/en/serverless/current/collect-data-with-aws-firehose.html @@ -97,7 +98,7 @@ The default CloudFormation stack is created in the AWS region selected for the u ::::{tab-item} Serverless :sync: serverless -* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started/create-an-observability-project.md). +* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started.md). * A user with the **Admin** role or higher—required to onboard system logs and metrics. To learn more, refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles). * An active AWS account and the necessary permissions to create delivery streams. @@ -170,7 +171,7 @@ The following table shows the type of data ingested by the supported AWS service :::{tab-item} Serverless :sync: serverless -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. In your {{obs-serverless}} project, go to **Add Data**. 3. Under **What do you want to monitor?** select **Cloud**, **AWS**, and then select **AWS Firehose**. diff --git a/solutions/observability/get-started/quickstart-create-synthetic-monitor.md b/solutions/observability/get-started/quickstart-create-synthetic-monitor.md new file mode 100644 index 0000000000..7a277919d4 --- /dev/null +++ b/solutions/observability/get-started/quickstart-create-synthetic-monitor.md @@ -0,0 +1,107 @@ +--- +description: Learn how to create a Synthetic Monitor to proactively test and monitor your applications by simulating user interactions. +applies_to: + serverless: +products: + - id: observability + - id: cloud-serverless +--- + +# Quickstart: Create a Synthetic Monitor [create-synthetic-monitor] + +Elastic [Synthetic monitoring](/solutions/observability/synthetics/index.md) is a comprehensive solution that allows organizations to proactively test and monitor applications by simulating user interactions, providing insights into performance metrics before real users encounter potential issues. This monitoring approach works by executing automated scripts that mimic typical user journeys and evaluating response times, error rates, and other critical performance indicators. + +In this quickstart guide, you'll get more familiar with Elastic Observability as well as an overview on how to ingest, view, and get started with Synthetic monitoring. + +## Create a monitor + +:::::{stepper} + +::::{step} Access your Elastic Cloud account + +Go to [cloud.elastic.co](https://cloud.elastic.co/) and access your account or create a new one. + +:::: + +::::{step} Create a new project + +Create a new {{observability}} project. Make sure to select your preferred cloud region when you create your first project. Refer to [Create an Observability project](/solutions/observability/get-started.md) for more details. + +:::: + +::::{step} Go to Synthetics + +Once your deployment is complete click **Applications** and select **Monitors** under **Synthetics**. + +There are two ways to run synthetic monitors which will depend on if the website or app being tested are accessible from: + +* Elastic's global managed testing infrastructure: With Elastic's global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you. This is perfect for testing websites or applications that are accessible from the public internet. +* Private networks support allows you to run monitors from your own premises. To run monitors from your own private network you must create a **Private Location** before continuing. For step-by-step instructions, refer to [Monitor resources on private networks](/solutions/observability/synthetics/monitor-resources-on-private-networks.md). + +This guide shows how to leverage Elastic's global managed testing infrastructure. + +:::{note} +Projects let you define your infrastructure as code. With project monitors you organize your YAML configuration and JavaScript- or TypeScript-defined monitors on the filesystem, use Git for version control, and deploy via a CLI tool, usually executed on a CI/CD platform. Refer to [Create monitors with project monitors](/solutions/observability/synthetics/create-monitors-with-projects.md). +::: + +::::{step} Create a browser monitor + +Create a single page browser monitor. Make sure to select a URL and the locations where monitors will be executed, then select **Create monitor**. + +:::{image} /solutions/images/synthetics-create-browser-monitor.png +:alt: Create browser monitor +:screenshot: +::: + +Synthetics will be executing the test across all of those locations, automatically refreshing the screen. + +:::{image} /solutions/images/synth-monitors.png +:alt: Browser monitor +:screenshot: +::: + +:::: + +::::{step} Turn on alerts + +If there are any issues, you might want to turn on alerts: + +1. Select **Configure now** from the Alerts warning, or go to **Settings** and then **Alerting**. +2. Select the default connector, which is already prepopulated when you deploy Elastic. After you select your default connector you can add your default email address to receive the alerts. +3. Go back to **Monitors**, select **Alerts and rules** then **Monitor status rule**. A dialog will appear where you can edit your alerts. You can also select alternate connector types, such as Slack, Microsoft Teams, and more. + +When you set up alerts and receive notifications, you’ll also receive a deep link directly into the Error details page. From here you can see: + +* What step failed +* Screenshot of the failed step +* Screenshot of the last time that step was successful +* The times of the failed step and last time step was successful to compare +* What code was executed +* What the browser is showing + +:::: + +::::{step} Analyze your monitor data + +Go to **Monitors** and select one of the monitors, you’ll see a dialog with a quick summary of the monitor. Select **Go to monitor** to see high level insights. Charts will start to render as more tests come through but you can quickly see the availability, the duration to execute tests, the timeline, and you can also drill down into the waterfall chart. + +:::{image} /solutions/images/Monitor_drill_down_1.png +:alt: Monitor drill down +:screenshot: +::: + +To drill down, select the icon under **View test run**. From here you can see the waterfall chart, object weight, object count, and more. + +:::{image} /solutions/images/Monitor_drill_down_2.png +:alt: Monitor drill down +:screenshot: +::: + +:::: +::::: + +## More resources + +* [Create monitors for project monitors](/solutions/observability/synthetics/create-monitors-with-projects.md). +* [Use the Synthetics UI](/solutions/observability/synthetics/create-monitors-ui.md). +* [Configure lightweight monitors](/solutions/observability/synthetics/configure-lightweight-monitors.md). diff --git a/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md b/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md index 397f67f5de..06a824b95c 100644 --- a/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md +++ b/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md @@ -1,4 +1,5 @@ --- +description: Learn how to use the Elastic Cloud Managed OTLP Endpoint to send logs, metrics, and traces to Elastic Observability. mapped_pages: - https://www.elastic.co/guide/en/serverless/current/collect-data-with-native-otlp.html applies_to: @@ -15,7 +16,7 @@ This functionality is in technical preview and may be changed or removed in a fu ## Prerequisites -* An {{obs-serverless}} project. To learn more, refer to [create an Observability project](/solutions/observability/get-started/create-an-observability-project.md). +* An {{obs-serverless}} project. To learn more, refer to [create an Observability project](/solutions/observability/get-started.md). * A system forwarding logs, metrics, or traces in OTLP (any EDOT Collector or SDK—EDOT or community). ### Limitations @@ -27,7 +28,7 @@ This functionality is in technical preview and may be changed or removed in a fu ### Get your native OTLP endpoint credentials -1. [Create a new Observability project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new Observability project](/solutions/observability/get-started.md), or open an existing one. 1. In your {{obs-serverless}} project, go to **Add Data**. diff --git a/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md b/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md index 067a293b9b..dad71564eb 100644 --- a/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md +++ b/solutions/observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md @@ -1,4 +1,5 @@ --- +description: Learn how to scan your host to detect and collect logs and metrics using Elastic Agent, and analyze your observability data with dashboards. mapped_pages: - https://www.elastic.co/guide/en/observability/current/quickstart-monitor-hosts-with-elastic-agent.html - https://www.elastic.co/guide/en/serverless/current/observability-quickstarts-monitor-hosts-with-elastic-agent.html @@ -47,7 +48,7 @@ The script also generates an {{agent}} configuration file that you can use with :::{tab-item} Serverless :sync: serverless -* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started/create-an-observability-project.md). +* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started.md). * An Elastic deployment. If you don’t have one yet, go to [cloud.elastic.co](https://cloud.elastic.co/). Within **Hosted deployments**, select **Create hosted deployment**. * A user with the **Admin** role or higher—required to onboard system logs and metrics. To learn more, refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles). * Root privileges on the host—required to run the auto-detection script used in this quickstart. @@ -75,11 +76,6 @@ The script also generates an {{agent}} configuration file that you can use with 1. In {{kib}}, go to the **Observability** UI and click **Add Data**. 2. Under **What do you want to monitor?** select **Host**, and then select **Elastic Agent: Logs & Metrics**. - :::{image} /solutions/images/observability-quickstart-monitor-hosts-entry-point.png - :alt: Host monitoring entry point - :screenshot: - ::: - 3. Copy the install command. You’ll run this command to download the auto-detection script, scan your system for observability data, and install {{agent}}. @@ -103,15 +99,9 @@ The script also generates an {{agent}} configuration file that you can use with :::{tab-item} Serverless :sync: serverless -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. In your {{obs-serverless}} project, go to **Add Data**. 3. Under **What do you want to monitor?** select **Host**, and then select **Elastic Agent: Logs & Metrics**. - - :::{image} /solutions/images/serverless-quickstart-monitor-hosts-entry-point.png - :alt: Host monitoring entry point - :screenshot: - ::: - 4. Copy the install command. You’ll run this command to download the auto-detection script, scan your system for observability data, and install {{agent}}. @@ -164,12 +154,6 @@ After installation is complete and all relevant data is flowing into Elastic, th For example, you can navigate the **Host overview** dashboard to explore detailed metrics about system usage and throughput. Metrics that indicate a possible problem are highlighted in red. -:::{image} /solutions/images/observability-quickstart-host-overview.png -:alt: Host overview dashboard -:screenshot: -::: - - ## Get value out of your data [_get_value_out_of_your_data] After using the dashboards to examine your data and confirm you’ve ingested all the host logs and metrics you want to monitor, you can use Elastic {{observability}} to gain deeper insight into your data. diff --git a/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md b/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md index 5b9fa8a6f7..b23b4c24ea 100644 --- a/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md +++ b/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md @@ -1,4 +1,5 @@ --- +description: Learn how to monitor hosts using the Elastic Distribution of OpenTelemetry (EDOT) Collector and gain deeper insights into your observability data. mapped_pages: - https://www.elastic.co/guide/en/observability/current/quickstart-monitor-hosts-with-otel.html - https://www.elastic.co/guide/en/serverless/current/quickstart-monitor-hosts-with-otel.html @@ -35,7 +36,7 @@ In this quickstart guide, you’ll learn how to monitor your hosts using the Ela :::{tab-item} Serverless :sync: serverless -* An {{observability}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started/create-an-observability-project.md). +* An {{observability}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started.md). * This quickstart is only available for Linux and MacOS systems. * A user with the **Admin** role or higher—required to onboard system logs and metrics. To learn more, refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles). * Root privileges on the host—required to run the OpenTelemetry collector because of these components: @@ -91,7 +92,7 @@ Logs are collected from setup onward, so you won’t see logs that occurred befo ::::{tab-item} Serverless :sync: serverless -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. To open the quickstart, go to **Add Data**. 3. Select **Collect and analyze logs**, and then select **OpenTelemetry**. 4. Under **What do you want to monitor?** select **Host**, and then select **Elastic Agent: Logs & Metrics**. @@ -114,13 +115,9 @@ Logs are collected from setup onward, so you won’t see logs that occurred befo ::::: - -Under **Visualize your data**, you’ll see links to **Discover** to view your logs and **Hosts** to view your host metrics. - - ## Gain deeper insight into your host data [_get_value_out_of_your_data] -After using the Hosts page and Discover to confirm you’ve ingested all the host logs and metrics you want to monitor, use Elastic {{observability}} to gain deeper insight into your host data with the following capabilities and features: +After using the **Hosts** page and **Discover** to confirm you’ve ingested all the host logs and metrics you want to monitor, use Elastic {{observability}} to gain deeper insight into your host data with the following capabilities and features: * In the [Infrastructure UI](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md), analyze and compare data collected from your hosts. You can also: @@ -141,3 +138,4 @@ After using the Hosts page and Discover to confirm you’ve ingested all the hos Refer to the [Elastic Observability](/solutions/observability.md) for a description of other useful features. + diff --git a/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md b/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md index 726ab92813..6d30626992 100644 --- a/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md +++ b/solutions/observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md @@ -1,4 +1,5 @@ --- +description: Learn how to monitor your Kubernetes cluster infrastructure with minimal configuration using Elastic Agent and kubectl commands. mapped_pages: - https://www.elastic.co/guide/en/serverless/current/observability-quickstarts-k8s-logs-metrics.html - https://www.elastic.co/guide/en/observability/current/monitor-k8s-logs-metrics-with-elastic-agent.html @@ -44,7 +45,7 @@ The kubectl command installs the standalone Elastic Agent in your Kubernetes clu :::{tab-item} Serverless :sync: serverless -* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started/create-an-observability-project.md). +* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started.md). * A user with the **Admin** role or higher—required to onboard system logs and metrics. To learn more, refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles). * A running Kubernetes cluster. * [Kubectl](https://kubernetes.io/docs/reference/kubectl/). @@ -65,11 +66,6 @@ The kubectl command installs the standalone Elastic Agent in your Kubernetes clu 1. In {{kib}}, go to the **Observability** UI and click **Add Data**. 2. Under **What do you want to monitor?** select **Kubernetes**, and then select **Elastic Agent: Logs & Metrics**. - :::{image} /solutions/images/observability-quickstart-k8s-entry-point.png - :alt: Kubernetes entry point - :screenshot: - ::: - 3. To install the Elastic Agent on your host, copy and run the install command. You will use the kubectl command to download a manifest file, inject user’s API key generated by {{kib}}, and create the Kubernetes resources. @@ -85,15 +81,9 @@ The kubectl command installs the standalone Elastic Agent in your Kubernetes clu :::{tab-item} Serverless :sync: serverless -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. In your {{obs-serverless}} project, go to **Add Data**. 3. Under **What do you want to monitor?** select **Kubernetes**, and then select **Elastic Agent: Logs & Metrics**. - - :::{image} /solutions/images/serverless-quickstart-k8s-entry-point.png - :alt: Kubernetes entry point - :screenshot: - ::: - 4. To install the Elastic Agent on your host, copy and run the install command. You will use the kubectl command to download a manifest file, inject user’s API key generated by Kibana, and create the Kubernetes resources. diff --git a/solutions/observability/get-started/quickstart-monitor-your-application-performance.md b/solutions/observability/get-started/quickstart-monitor-your-application-performance.md new file mode 100644 index 0000000000..58833942b5 --- /dev/null +++ b/solutions/observability/get-started/quickstart-monitor-your-application-performance.md @@ -0,0 +1,107 @@ +--- +description: Learn how to monitor your application performance using the Elastic Distribution of OpenTelemetry (EDOT) SDKs and Elastic APM. +applies_to: + stack: ga + serverless: ga +products: + - id: observability + - id: cloud-serverless +--- + +# Quickstart: Monitor your application performance [quickstart-monitor-your-application-performance] + +In this quickstart guide, you’ll learn how to instrument your application using the Elastic Distribution of OpenTelemetry (EDOT) SDKs. You’ll also learn how to use {{observability}} features to gain deeper insight into your application telemetry data after collecting it. + +## Prerequisites [_prerequisites] + +::::{tab-set} +:group: stack-serverless + +:::{tab-item} Elastic Stack +:sync: stack + +* An {{es}} cluster for storing and searching your data, and {{kib}} for visualizing and managing your data. This quickstart is available for all Elastic deployment models. The quickest way to get started with this quickstart is using a trial project on [Elastic serverless](https://docs.elastic.co/serverless/quickstart-monitor-hosts-with-otel.html). +* A user with the **Admin** role or higher—required to onboard system logs and metrics. To learn more, refer to [User roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md). +* An Elastic Distribution of OpenTelemetry (EDOT) Collector or the upstream OpenTelemetry Collector running on the host. + +::: + +:::{tab-item} Serverless +:sync: serverless + +* An {{observability}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started.md). +* A user with the **Admin** role or higher—required to onboard system logs and metrics. To learn more, refer to [Assign user roles and privileges](/deploy-manage/users-roles/cloud-organization/user-roles.md#general-assign-user-roles). +* An Elastic Distribution of OpenTelemetry (EDOT) Collector or the upstream OpenTelemetry Collector running on the host. + +::: +:::: + +## Install the EDOT Collector [_install_edot_collector] + +The EDOT Collector in [Agent mode](opentelemetry://reference/edot-collector/modes.md#edot-collector-as-agent) collects infrastructure and application telemetry data sent by the EDOT SDKs and forwards it to Elastic. + +Refer to the [EDOT Quickstarts](opentelemetry://reference/quickstart/index.md) to install the EDOT Collector for your deployment mode. + +## Collect application telemetry data [_collect_your_data] + +Follow these steps to collect application telemetry data using the EDOT SDKs: + +:::::{tab-set} +:group: stack-serverless + +::::{tab-item} Elastic Stack +:sync: stack + +1. In {{kib}}, go to the **Observability** UI and click **Add Data**. +2. Under **What do you want to monitor?** select **Application**, and then select **OpenTelemetry**. +3. Follow the instructions to install the EDOT SDK for your application: + + - [.NET](opentelemetry://reference/edot-sdks/dotnet/setup/index.md) + - [Java](opentelemetry://reference/edot-sdks/java/setup/index.md) + - [Node.js](opentelemetry://reference/edot-sdks/nodejs/setup/index.md) + - [PHP](opentelemetry://reference/edot-sdks/php/setup/index.md) + - [Python](opentelemetry://reference/edot-sdks/python/setup/index.md) +4. Configure your EDOT SDK to send data to the APM endpoint. The **OpenTelemetry** tab provides the required configuration values. + +:::{note} +If your application runs on Kubernetes, the OpenTelemetry operator automatically instruments your application, provided you've added language-specific annotations. Refer to [Auto-instrument applications](opentelemetry://reference/quickstart/self-managed/k8s.md). +::: + +:::: + +::::{tab-item} Serverless +:sync: serverless + +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. +2. Under **What do you want to monitor?** select **Application**, and then select **OpenTelemetry**. +3. Follow the instructions to install the EDOT SDK for your application: + + - [.NET](opentelemetry://reference/edot-sdks/dotnet/setup/index.md) + - [Java](opentelemetry://reference/edot-sdks/java/setup/index.md) + - [Node.js](opentelemetry://reference/edot-sdks/nodejs/setup/index.md) + - [PHP](opentelemetry://reference/edot-sdks/php/setup/index.md) + - [Python](opentelemetry://reference/edot-sdks/python/setup/index.md) +4. Configure your EDOT SDK to send data to the [Managed OTLP endpoint](opentelemetry://reference/motlp.md). The **OpenTelemetry** tab provides the required configuration values. + +:::{note} +If your application runs on Kubernetes, the OpenTelemetry operator automatically instruments your application, provided you've added language-specific annotations. Refer to [Auto-instrument applications](opentelemetry://reference/quickstart/serverless/k8s.md). +::: + +:::: +::::: + +## Gain deeper insight into your application data [_get_value_out_of_your_data] + +After using the **Applications** page and **Discover** to confirm you’ve ingested all the application traces, metrics, and logs you want to monitor, use Elastic {{observability}} to gain deeper insight into your application data with the following capabilities and features: + +* In the [Applications UI](/solutions/observability/apm/view-analyze-data.md), analyze and compare data collected from your application. You can also: + + * [Drill down into data](/solutions/observability/apm/drill-down-into-data.md) to view details about specific transactions and spans. + * [Find transaction latency and failure correlations](/solutions/observability/apm/find-transaction-latency-failure-correlations.md) to identify root causes. + * [Create alerts](/solutions/observability/apm/create-apm-rules-alerts.md) that notify you when an anomaly is detected or a metric exceeds a given value. + +* In [Service Map](/solutions/observability/apm/service-map.md), explore how your services are connected and check health indicators. You can also: + +* Use [machine learning](/solutions/observability/apm/machine-learning.md) to quickly pinpoint anomalous transactions and see the health of any upstream and downstream services. + +Refer to the [Elastic Observability](/solutions/observability.md) for a description of other useful features. \ No newline at end of file diff --git a/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md b/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md index b658fb40b5..912ffcd929 100644 --- a/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md +++ b/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md @@ -1,4 +1,5 @@ --- +description: Learn how to send Kubernetes logs, metrics, and application traces to Elasticsearch using the OpenTelemetry Operator and Elastic Distributions of OpenTelemetry (EDOT). mapped_pages: - https://www.elastic.co/guide/en/observability/current/monitor-k8s-otel-edot.html - https://www.elastic.co/guide/en/serverless/current/monitor-k8s-otel-edot.html @@ -46,7 +47,7 @@ The [{{ecloud}} Managed OTLP Endpoint](opentelemetry://reference/motlp.md) funct :::{tab-item} Serverless :sync: serverless -* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started/create-an-observability-project.md). +* An {{obs-serverless}} project. To learn more, refer to [Create an Observability project](/solutions/observability/get-started.md). * A running Kubernetes cluster (v1.23 or newer). * [Kubectl](https://kubernetes.io/docs/reference/kubectl/). * [Helm](https://helm.sh/docs/intro/install/). @@ -93,7 +94,7 @@ The [{{ecloud}} Managed OTLP Endpoint](opentelemetry://reference/motlp.md) funct :::{tab-item} Serverless :sync: serverless -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. In your {{obs-serverless}} project, go to **Add Data**. 3. Under **What do you want to monitor?** select **Kubernetes**, and then select **OpenTelemetry: Full Observability**. @@ -123,8 +124,6 @@ The [{{ecloud}} Managed OTLP Endpoint](opentelemetry://reference/motlp.md) funct :::: - - ## Visualize your data [_visualize_your_data] After installation is complete and all relevant data is flowing into Elastic, the **Visualize your data** section provides a link to the **[OTEL][Metrics Kubernetes]Cluster Overview** dashboard used to monitor the health of the cluster. @@ -134,6 +133,38 @@ After installation is complete and all relevant data is flowing into Elastic, th :screenshot: ::: +### Work with Kubernetes logs + +You can search and analyze Kubernetes logs using Elastic’s Discover capability. Find **Discover** in the main menu or use the global search field. + +:::{image} /solutions/images/screenshot-observability-monitoring-k8s-kubernetes-logs-can-be-searched.png +:alt: Kubernetes logs in Discover +:screenshot: +::: + +### Visualize Kubernetes metrics + +Kubernetes out-of-the-box dashboards allow you to analyze Kubernetes metrics within Kibana. Go to **Dashboards** → **Analytics** and search for **Kubernetes**. The **Kubernetes Overview** dashboard shows metrics for the entire Kubernetes Cluster. All the nodes, pods, and CPU and memory usage. + +:::{image} /solutions/images/screenshot-observability-monitoring-k8s-kubernetes-overview-cluster.png +:alt: Kubernetes overview dashboard +:screenshot: +::: + +Kibana allows you to analyze logs with interactive dashboards to derive insights, automate workflows, find anomalies and trends, and more. When you select **Dashboards** → **Analytics**, you can select **Create dashboard** and customize your new dashboard to your needs. + +### Set up alerts + +Select **Alerts** and then **Create rules**. This allows you to get notifications when various events happen, for example when latency is anomalous, metric aggregation exceeds threshold, and so on. Notifications are sent through email, Jira, Slack, and more. + +### Use machine learning to uncover insights + +Find **Machine Learning** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Then select **Anomaly Detection** → **Jobs** to create a machine learning job. By setting up machine learning jobs, for example, rather than having an alert when a specific percentage of memory usage has occurred, you can know when the usage is unusual. + +:::{image} /solutions/images/screenshot-observability-monitoring-k8s-leverage-machine-learning-to-uncover-insights.png +:alt: Machine learning job +:screenshot: +::: ## Troubleshooting and more [_troubleshooting_and_more] diff --git a/solutions/observability/get-started/quickstarts.md b/solutions/observability/get-started/quickstarts.md new file mode 100644 index 0000000000..68bbaa4186 --- /dev/null +++ b/solutions/observability/get-started/quickstarts.md @@ -0,0 +1,49 @@ +--- +navigation_title: Elastic Observability quickstarts +applies_to: + stack: ga + serverless: ga +products: + - id: cloud-serverless + - id: observability +--- + +# Elastic {{observability}} quickstarts + +Our quickstarts reduce your time-to-value by offering a fast path to ingest and visualize your Observability data. Each quickstart provides: + +* A highly opinionated, fast path to data ingestion +* Sensible configuration defaults with minimal configuration required +* Auto-detection of logs and metrics for monitoring hosts +* Quick access to related dashboards and visualizations + +Follow the steps in these guides to get started quickly: + +* [**Quickstart: Monitor hosts with OpenTelemetry**](/solutions/observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md). +* [**Quickstart: Monitor your application performance**](/solutions/observability/get-started/quickstart-monitor-your-application-performance.md). +* [**Quickstart: Monitor Kubernetes with OpenTelemetry**](/solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md). +* [**Quickstart: Send data to the Elastic Cloud Managed OTLP Endpoint**](/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md). +* [**Quickstart: Create a Synthetic monitor**](/solutions/observability/get-started/quickstart-create-synthetic-monitor.md). +* [**Quickstart: Collect data from AWS Firehose**](/solutions/observability/get-started/quickstart-collect-data-with-aws-firehose.md). + +## Get started with other features [_get_started_with_other_features] + +Want to use {{fleet}} or some other feature not covered in the quickstarts? Follow the steps in these guides to get started: + +* [Get started with system metrics](/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md). +* [Get started with application traces and APM](/solutions/observability/apm/get-started-fleet-managed-apm-server.md). +* [Get started with synthetic monitoring](/solutions/observability/synthetics/index.md). +* [Get started with Universal Profiling](/solutions/observability/infra-and-hosts/get-started-with-universal-profiling.md). + +## Additional guides [_additional_guides] + +Ready to dig into more features of Elastic Observability? See these guides: + +* [Add data from Splunk](/solutions/observability/get-started/other-tutorials/add-data-from-splunk.md). +* [Create an alert](/solutions/observability/incident-management/alerting.md). +* [Create a service-level objective (SLO)](/solutions/observability/incident-management/create-an-slo.md). + +## Related content for Elastic Stack [_related_content] + +* [Starting with the {{es}} Platform and its Solutions](/get-started/index.md) for new users. +* [Adding data to {{es}}](/manage-data/ingest.md) for other ways to ingest data. \ No newline at end of file diff --git a/solutions/observability/get-started/what-is-elastic-observability.md b/solutions/observability/get-started/what-is-elastic-observability.md index df2403ad68..48c6f60e32 100644 --- a/solutions/observability/get-started/what-is-elastic-observability.md +++ b/solutions/observability/get-started/what-is-elastic-observability.md @@ -1,4 +1,5 @@ --- +description: An introduction to Elastic Observability, a unified solution that provides insights into application behavior through logs, metrics, traces, and more. mapped_pages: - https://www.elastic.co/guide/en/observability/current/observability-introduction.html - https://www.elastic.co/guide/en/serverless/current/observability-serverless-observability-overview.html @@ -17,6 +18,10 @@ products: :alt: Elastic {{observability}} overview diagram ::: +:::{{tip}} +To get started with Elastic {{observability}}, refer to [Get started with {{observability}}](/solutions/observability/get-started.md). +::: + ## Log monitoring [apm-overview] Analyze log data from your hosts, services, Kubernetes, Apache, and many more. @@ -28,7 +33,7 @@ In **Discover**, you can quickly search and filter your log data, get informatio :class: screenshot ::: -[Learn more about log monitoring →](/solutions/observability/logs.md) +[Learn more about log monitoring](/solutions/observability/logs.md). ## Application performance monitoring (APM) [observability-serverless-observability-overview-application-performance-monitoring-apm] @@ -46,8 +51,7 @@ The **Service** inventory provides a quick, high-level overview of the health an :screenshot: ::: -[Learn more about Application performance monitoring (APM) →](/solutions/observability/apm/index.md) - +[Learn more about Application performance monitoring (APM)](/solutions/observability/apm/index.md). ## Infrastructure monitoring [metrics-overview] @@ -62,8 +66,7 @@ On the {{observability}} **Overview** page, the **Hosts** table shows your top h You can then drill down into the {{infrastructure-app}} by clicking **Show inventory**. Here you can monitor and filter your data by hosts, pods, containers,or EC2 instances and create custom groupings such as availability zones or namespaces. -[Learn more about infrastructure monitoring → ](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md) - +[Learn more about infrastructure monitoring](/solutions/observability/infra-and-hosts/analyze-infrastructure-host-metrics.md). % Stateful only for RUM. @@ -80,13 +83,13 @@ On the {{observability}} **Overview** page, the **{{user-experience}}** chart pr You can then drill down into the {{user-experience}} dashboard by clicking **Show dashboard** too see data by URL, operating system, browser, and location. - [Learn more about {{user-experience}} →](/solutions/observability/applications/user-experience.md) + [Learn more about {{user-experience}}](/solutions/observability/applications/user-experience.md). ## Synthetic monitoring [synthetic-monitoring-overview] Simulate actions and requests that an end user would perform on your site at predefined intervals and in a controlled environment. The end result is rich, consistent, and repeatable data that you can trend and alert on. -[Learn more about Synthetic monitoring →](/solutions/observability/synthetics/index.md) +[Learn more about Synthetic monitoring](/solutions/observability/synthetics/index.md). % Stateful only for Universal Profiling. @@ -94,8 +97,7 @@ Simulate actions and requests that an end user would perform on your site at pre Build stack traces to get visibility into your system without application source code changes or instrumentation. Use flamegraphs to explore system performance and identify the most expensive lines of code, increase CPU resource efficiency, debug performance regressions, and reduce cloud spend. -[Learn more about Universal Profiling →](/solutions/observability/infra-and-hosts/universal-profiling.md) - +[Learn more about Universal Profiling](/solutions/observability/infra-and-hosts/universal-profiling.md) ## Alerting [observability-serverless-observability-overview-alerting] @@ -108,8 +110,7 @@ On the **Alerts** page, the **Alerts** table provides a snapshot of alerts occur :screenshot: ::: -[Learn more about alerting → ](/solutions/observability/incident-management/alerting.md) - +[Learn more about alerting → ](/solutions/observability/incident-management/alerting.md). ## Service-level objectives (SLOs) [observability-serverless-observability-overview-service-level-objectives-slos] @@ -122,7 +123,7 @@ From the SLO overview list, you can see all of your SLOs and a quick summary of :screenshot: ::: -[Learn more about SLOs → ](/solutions/observability/incident-management/service-level-objectives-slos.md) +[Learn more about SLOs → ](/solutions/observability/incident-management/service-level-objectives-slos.md). ## Cases [observability-serverless-observability-overview-cases] @@ -133,7 +134,7 @@ Collect and share information about observability issues by creating cases. Case :screenshot: ::: -[Learn more about cases → ](/solutions/observability/incident-management/cases.md) +[Learn more about cases](/solutions/observability/incident-management/cases.md). ## Machine learning and AIOps [observability-serverless-observability-overview-aiops] @@ -148,4 +149,4 @@ Reduce the time and effort required to detect, understand, investigate, and reso :screenshot: ::: -[Learn more about machine learning and AIOps →](/explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md) \ No newline at end of file +[Learn more about machine learning and AIOps](/explore-analyze/machine-learning/machine-learning-in-kibana/xpack-ml-aiops.md). \ No newline at end of file diff --git a/solutions/observability/incident-management/service-level-objectives-slos.md b/solutions/observability/incident-management/service-level-objectives-slos.md index 01f44d0c7e..e66d0d8c54 100644 --- a/solutions/observability/incident-management/service-level-objectives-slos.md +++ b/solutions/observability/incident-management/service-level-objectives-slos.md @@ -95,10 +95,6 @@ Available SLO panels include: :screenshot: ::: -To learn more about Dashboards, see [Dashboards](/solutions/observability/get-started/get-started-with-dashboards.md). - -% Stateful only for upgrade. - ## Upgrade from beta to GA [slo-upgrade-to-ga] Starting in version 8.12.0, SLOs are generally available (GA). If you’re upgrading from a beta version of SLOs (available in 8.11.0 and earlier), you must migrate your SLO definitions to a new format. diff --git a/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md b/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md index 1e095941ae..d6c2977d9a 100644 --- a/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md +++ b/solutions/observability/infra-and-hosts/get-started-with-system-metrics.md @@ -89,7 +89,7 @@ In this step, add the System integration to monitor host logs and metrics. :::{tab-item} Serverless :sync: serverless -1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started/create-an-observability-project.md), or open an existing one. +1. [Create a new {{obs-serverless}} project](/solutions/observability/get-started.md), or open an existing one. 2. In your {{obs-serverless}} project, go to **Project Settings** → **Integrations**. 3. Type **System** in the search bar, then select the integration to see more details about it. 4. Click **Add System**. diff --git a/solutions/observability/logs/get-started-with-system-logs.md b/solutions/observability/logs/get-started-with-system-logs.md index 05cff60a0b..91e003b8f2 100644 --- a/solutions/observability/logs/get-started-with-system-logs.md +++ b/solutions/observability/logs/get-started-with-system-logs.md @@ -21,7 +21,7 @@ In this guide you’ll learn how to onboard system log data from a machine or se To onboard system log data: -1. Open an [{{obs-serverless}} project](../get-started/create-an-observability-project.md) or Elastic Stack deployment. +1. Open an [{{obs-serverless}} project](/solutions/observability/get-started.md) or Elastic Stack deployment. 2. From the Observability UI, go to **Add data**. 3. Under **What do you want to monitor?**, select **Host** → **Elastic Agent: Logs & Metrics**. 4. Follow the in-product steps to auto-detect your logs and install and configure the {{agent}}. diff --git a/solutions/security/get-started/ingest-data-to-elastic-security.md b/solutions/security/get-started/ingest-data-to-elastic-security.md index c123eac23d..35a78b2fb4 100644 --- a/solutions/security/get-started/ingest-data-to-elastic-security.md +++ b/solutions/security/get-started/ingest-data-to-elastic-security.md @@ -18,7 +18,7 @@ To ingest data, you can use: * The [{{agent}}](/reference/fleet/index.md) with the **{{elastic-defend}}** integration, which protects your hosts and sends logs, metrics, and endpoint security data to {{elastic-sec}}. See [Install {{elastic-defend}}](/solutions/security/configure-elastic-defend/install-elastic-defend.md). * The {{agent}} with integrations, which are available in the [Elastic Package Registry (EPR)](/reference/fleet/index.md#package-registry-intro). To install an integration that works with {{elastic-sec}}, go to the {{kib}} Home page or navigation menu and click **Add integrations**. On the Integrations page, click the **Security** category filter, then select an integration to view the installation instructions. For more information on integrations, refer to [{{integrations}}](https://docs.elastic.co/en/integrations). * **{{beats}}** shippers installed for each system you want to monitor. -* The {{agent}} to send data from Splunk to {{elastic-sec}}. See [Get started with data from Splunk](/solutions/observability/get-started/add-data-from-splunk.md). +* The {{agent}} to send data from Splunk to {{elastic-sec}}. See [Get started with data from Splunk](/solutions/observability/get-started/other-tutorials/add-data-from-splunk.md). * Third-party collectors configured to ship ECS-compliant data. [](/reference/security/fields-and-object-schemas/siem-field-reference.md) provides a list of ECS fields used in {{elastic-sec}}. ::::{important} diff --git a/solutions/toc.yml b/solutions/toc.yml index 1da35be459..225ca6a40b 100644 --- a/solutions/toc.yml +++ b/solutions/toc.yml @@ -33,8 +33,8 @@ toc: children: - file: search/vector/dense-vector.md children: - - file: search/vector/knn.md - - file: search/vector/bring-own-vectors.md + - file: search/vector/knn.md + - file: search/vector/bring-own-vectors.md - file: search/vector/sparse-vector.md - file: search/vector/dense-versus-sparse-ingest-pipelines.md - file: search/semantic-search.md @@ -90,18 +90,22 @@ toc: - file: observability/get-started.md children: - file: observability/get-started/what-is-elastic-observability.md - - file: observability/get-started/create-an-observability-project.md - - file: observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md - - file: observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md - - file: observability/get-started/quickstart-elastic-cloud-otel-endpoint.md - - file: observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md - - file: observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md - - file: observability/get-started/add-data-from-splunk.md - - file: observability/get-started/quickstart-collect-data-with-aws-firehose.md - - file: observability/get-started/get-started-with-dashboards.md + - file: observability/get-started/quickstarts.md + children: + - file: observability/get-started/quickstart-monitor-hosts-with-opentelemetry.md + - file: observability/get-started/quickstart-monitor-your-application-performance.md + - file: observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md + - file: observability/get-started/quickstart-elastic-cloud-otel-endpoint.md + - file: observability/get-started/quickstart-create-synthetic-monitor.md + - file: observability/get-started/quickstart-monitor-hosts-with-elastic-agent.md + - file: observability/get-started/quickstart-monitor-kubernetes-cluster-with-elastic-agent.md + - file: observability/get-started/quickstart-collect-data-with-aws-firehose.md + - file: observability/get-started/other-tutorials/index.md + children: + - file: observability/get-started/other-tutorials/tutorial-monitor-java-application.md + - file: observability/get-started/other-tutorials/add-data-from-splunk.md - file: observability/applications/index.md children: - - file: observability/applications/llm-observability.md - file: observability/apm/index.md children: - file: observability/apm/get-started.md @@ -305,6 +309,7 @@ toc: - file: observability/synthetics/support-matrix.md - file: observability/synthetics/encryption-security.md - file: observability/applications/user-experience.md + - file: observability/applications/llm-observability.md - file: observability/uptime/index.md children: - file: observability/uptime/get-started.md @@ -315,7 +320,6 @@ toc: - file: observability/uptime/inspect-duration-anomalies.md - file: observability/uptime/configure-settings.md - file: observability/otlp-visualize.md - - file: observability/applications/tutorial-monitor-java-application.md - file: observability/cicd.md - file: observability/cloud.md children: