Merge branch 'detection-and-alerts-topics' of https://github.com/elastic/docs-content into detection-and-alerts-topics

Author: nastasha-solomon

solutions/observability/cloud/gcp-dataflow-templates.md

@@ -40,7 +40,7 @@ You’ll start with installing the Elastic GCP integration to add pre-built dash
 
 4. Click **Save integration**.
 
-:::::{admonition}
+:::::{note}
 This tutorial assumes the Elastic cluster is already running. To continue, you’ll need your **Cloud ID** and an **API Key**.
 
 To find the Cloud ID of your [deployment](https://cloud.elastic.co/deployments), go to the deployment’s **Overview** page.

solutions/observability/cloud/monitor-amazon-kinesis-data-streams.md

@@ -29,7 +29,7 @@ To collect Kinesis data stream metrics from Amazon CloudWatch, you typically nee
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
 :::::{dropdown} **Quick guide: Add data**
-::::{admonition}
+::::{note}
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon Kinesis Data Stream** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.
@@ -48,7 +48,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat
 7. Click **Save and continue**. This step takes a minute or two to complete. When it’s done, you’ll have an agent policy that contains an integration policy for the configuration you just specified. If an {{agent}} is already assigned to the policy, you’re done. Otherwise, you need to deploy an {{agent}}.
 8. To deploy an {{agent}}:
 
-    1. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent*** flyout. If you accidentally close the popup or the flyout doesn’t open, go to ***{{fleet}} → Agents**, then click **Add agent** to access the flyout.
+    1. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent** flyout. If you accidentally close the popup or the flyout doesn’t open, go to **{{fleet}} → Agents**, then click **Add agent** to access the flyout.
     2. Follow the steps in the **Add agent** flyout to download, install, and enroll the {{agent}}.
 
 9. When incoming data is confirmed—​after a minute or two—​click **View assets** to access the dashboards.

solutions/observability/cloud/monitor-amazon-simple-queue-service-sqs.md

@@ -25,7 +25,7 @@ To collect SQS metrics, you typically need to install the Elastic [Amazon SQS in
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
 :::::{dropdown} **Quick guide: Add data**
-::::{admonition}
+::::{note}
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon SQS** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.
@@ -44,7 +44,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat
 7. Click **Save and continue**. This step takes a minute or two to complete. When it’s done, you’ll have an agent policy that contains an integration policy for the configuration you just specified. If an {{agent}} is already assigned to the policy, you’re done. Otherwise, you need to deploy an {{agent}}.
 8. To deploy an {{agent}}:
 
-    1. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent*** flyout. If you accidentally close the popup or the flyout doesn’t open, go to ***{{fleet}} → Agents**, then click **Add agent** to access the flyout.
+    1. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent** flyout. If you accidentally close the popup or the flyout doesn’t open, go to **{{fleet}} → Agents**, then click **Add agent** to access the flyout.
     2. Follow the steps in the **Add agent** flyout to download, install, and enroll the {{agent}}.
 
 9. When incoming data is confirmed—​after a minute or two—​click **View assets** to access the dashboards.

solutions/observability/cloud/monitor-amazon-simple-storage-service-s3.md

@@ -28,7 +28,7 @@ To collect S3 metrics, you typically need to install the Elastic [Amazon S3 inte
 Expand the **quick guide** to learn how, or skip to the next section if your data is already in {{es}}.
 
 :::::{dropdown} **Quick guide: Add data**
-::::{admonition}
+::::{note}
 1. In the Observability UI, find **Integrations** in the main menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
 2. In the query bar, search for and select the **Amazon S3** integration.
 3. Read the overview to make sure you understand integration requirements and other considerations.
@@ -47,7 +47,7 @@ Expand the **quick guide** to learn how, or skip to the next section if your dat
 7. Click **Save and continue**. This step takes a minute or two to complete. When it’s done, you’ll have an agent policy that contains an integration policy for the configuration you just specified. If an {{agent}} is already assigned to the policy, you’re done. Otherwise, you need to deploy an {{agent}}.
 8. To deploy an {{agent}}:
 
-    1. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent*** flyout. If you accidentally close the popup or the flyout doesn’t open, go to ***{{fleet}} → Agents**, then click **Add agent** to access the flyout.
+    1. In the popup, click **Add {{agent}} to your hosts** to open the **Add agent** flyout. If you accidentally close the popup or the flyout doesn’t open, go to **{{fleet}} → Agents**, then click **Add agent** to access the flyout.
     2. Follow the steps in the **Add agent** flyout to download, install, and enroll the {{agent}}.
 
 9. When incoming data is confirmed—​after a minute or two—​click **View assets** to access the dashboards.

solutions/observability/cloud/monitor-amazon-web-services-aws-with-elastic-agent.md

@@ -45,7 +45,7 @@ In this step, you create an Amazon Simple Queue Service (SQS) queue and configur
 
 You should already have an S3 bucket that contains exported VPC flow logs. If you don’t, create one now. To learn how, refer to [publishing flow logs to an S3 bucket](https://docs.aws.amazon.com/vpc/latest/userguide/flow-logs-s3.md).
 
-::::{admonition}
+::::{note}
 **Why is an SQS queue needed?**
 
 Creating an SQS queue helps avoid significant lagging caused by polling all log files from each S3 bucket. Instead of polling each bucket, you configure the S3 buckets to send a notification to the SQS queue whenever a new object is created. The {{agent}} monitors the SQS queue for new object creation messages and uses information in the messages to retrieve logs from the S3 buckets. With this setup, periodic polling from each S3 bucket is not needed. Instead, the {{agent}} S3 input guarantees near real-time data collection from S3 buckets with both speed and reliability.
@@ -188,7 +188,7 @@ VPC flow logs are sent to an S3 bucket, which sends a notification to the SQS qu
 
 ## Step 4: Collect S3 access logs [aws-elastic-agent-collect-s3-access-logs]
 
-::::{admonition}
+::::{note}
 S3 access logs contain detailed records for the requests that are made to a bucket. Server access logs are useful for many applications. For example, access log information can be useful in security and access audits. It can also help you learn about your customer base and understand your Amazon S3 bill.
 
 ::::

solutions/observability/cloud/monitor-microsoft-azure-openai.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Monitor Microsoft Azure OpenAI [monitor-azure-openai]
 
-::::{admonition}
+::::{note}
 **New to Elastic?** Follow the steps in our [getting started guide](https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/getting-started-observability.html) instead of the steps described here. Return to this tutorial after you’ve learned the basics.
 
 ::::

solutions/observability/cloud/monitor-microsoft-azure-with-azure-native-isv-service.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Monitor Microsoft Azure with the Azure Native ISV Service [monitor-azure-native]
 
-::::{admonition}
+::::{note}
 The {{ecloud}} Azure Native ISV Service allows you to deploy managed instances of the {{stack}} directly in Azure, through the Azure integrated marketplace. The service includes native capabilities for consolidating Azure logs and metrics in Elastic. For more information, refer to [Azure Native ISV Service](../../../deploy-manage/deploy/elastic-cloud/azure-native-isv-service.md).
 
 **Using {{agent}} to monitor Azure?** Refer to [Monitor Microsoft Azure with {{agent}}](monitor-microsoft-azure-with-elastic-agent.md).

solutions/observability/cloud/monitor-microsoft-azure-with-beats.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Monitor Microsoft Azure with Beats [monitor-azure]
 
-::::{admonition}
+::::{note}
 **Are you sure you want to use {{beats}}?**
 
 {{agent}} is the recommended way to monitor Azure if you want to manage your agents centrally in {{fleet}}. To learn how to use {{agent}}, refer to [Monitor Microsoft Azure with {{agent}}](monitor-microsoft-azure-with-elastic-agent.md).

solutions/observability/cloud/monitor-microsoft-azure-with-elastic-agent.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Monitor Microsoft Azure with Elastic Agent [monitor-azure-elastic-agent]
 
-::::{admonition}
+::::{note}
 **New to Elastic?** Follow the steps in our [getting started guide](https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/getting-started-observability.html) instead of the steps described here. Return to this tutorial after you’ve learned the basics.
 
 **Using the native Azure integration from the marketplace?** Refer to [Monitor Microsoft Azure with the Azure Native ISV Service](monitor-microsoft-azure-with-azure-native-isv-service.md).
@@ -195,7 +195,7 @@ To create an Azure event hub:
 7. Click **Review + create**, and then click **Create** to deploy the resource.
 8. Make a note of the namespace and event hub name because you will need them later.
 
-:::::{admonition}
+:::::{note}
 **When do I need more than one event hub?**
 
 Typically you create an event hub for each service you want to monitor. For example, imagine that you want to collect activity logs from the Azure Monitor service plus signin and audit logs from the Active Directory service. Rather than sending all logs to a single event hub, you create an event hub for each service:

solutions/observability/get-started/create-an-observability-project.md

@@ -9,8 +9,7 @@ mapped_pages:
 # Create an observability project [observability-create-an-observability-project]
 
 
-::::{admonition} Required role
-:class: note
+::::{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).