add synthetics get started

Author: mdbirnstiehl

solutions/observability/apps/get-started.md

@@ -4,17 +4,46 @@ mapped_urls:
   - https://www.elastic.co/guide/en/serverless/current/observability-synthetics-get-started.html
 ---
 
-# Get started
+# Get started [observability-synthetics-get-started]
 
-% What needs to be done: Align serverless/stateful
+To set up a synthetic monitor, you need to configure the monitor, run it, and send data back to Elastic. After setup is complete, the data will be available in your serverless Observability project or in {{kib}} to view, analyze, and alert on.
 
-% Use migrated content from existing pages that map to this page:
+There are two ways to set up a synthetic monitor:
 
-% - [ ] ./raw-migrated-files/observability-docs/observability/synthetics-get-started.md
-% - [ ] ./raw-migrated-files/docs-content/serverless/observability-synthetics-get-started.md
+* Synthetics project
+* The Synthetics UI
 
-% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
+Read more about each option below, and choose the approach that works best for you.
 
-$$$choose-projects$$$
 
-$$$observability-synthetics-get-started-synthetics-project$$$
+## Synthetics project [observability-synthetics-get-started-synthetics-project]
+
+With a Synthetics project, you write tests in an external version-controlled Node.js project using YAML for lightweight monitors and JavaScript or TypeScript for browser monitors. Then, you use the `@elastic/synthetics` NPM library’s `push` command to create monitors.
+
+This approach works well if you want to create both browser monitors and lightweight monitors. It also allows you to configure and update monitors using a GitOps workflow.
+
+Get started in [Create monitors in a Synthetics project](../../../solutions/observability/apps/create-monitors-with-project-monitors.md).
+
+:::{image} ../../../images/observability-synthetics-get-started-projects.png
+:alt: Diagram showing which pieces of software are used to configure monitors
+:::
+
+
+## Synthetics UI [observability-synthetics-get-started-synthetics-ui]
+
+You can create monitors directly in the user interface. This approach works well if you want to create and manage your monitors in the browser.
+
+Get started in [Create monitors in the Synthetics UI](../../../solutions/observability/apps/create-monitors-in-synthetics-app.md).
+
+:::{image} ../../../images/observability-synthetics-get-started-ui.png
+:alt: Diagram showing which pieces of software are used to configure monitors
+:::
+
+::::{note}
+The Elastic Synthetics integration is a method for creating synthetic monitors that is no longer recommended. **Do not use the Elastic Synthetics integration to set up new monitors.**
+
+For details on how to migrate from Elastic Synthetics integration to {{project-monitors}} or the {{synthetics-app}}, refer to [Migrate from the Elastic Synthetics integration](../../../solutions/observability/apps/migrate-from-elastic-synthetics-integration.md).
+
+If you’ve used the Elastic Synthetics integration to create monitors in the past and need to reference documentation about the integration, go to the [8.3 documentation](https://www.elastic.co/guide/en/observability/8.3/uptime-set-up.html#uptime-set-up-choose-agent).
+
+::::

solutions/observability/apps/writer-role.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Writer role [synthetics-role-write]
 
-::::{important} 
+::::{important}
 To minimize the privileges required by the writer role, use the [setup role](setup-role.md) to enable Monitor Management. This section assumes another user has already enabled Monitor Management.
 ::::
 
@@ -16,13 +16,13 @@ For users who need to create, modify, and delete monitors, provide write access.
 * **Limited write access**: If you want to limit write access to the {{synthetics-app}} only, you can use [Limited write access](#synthetics-write-privileges-limited), which requires additional configuration.
 
 
-## General write access [synthetics-write-privileges-general] 
+## General write access [synthetics-write-privileges-general]
 
 Create a **writer role**, called something like `synthetics_writer`:
 
 1. Start with the `editor` [built-in role](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md). This role grants full access to all features in {{kib}} (including the {{observability}} solution) and read-only access to data indices.
 
-    ::::{note} 
+    ::::{note}
     The `editor` [built-in role](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md) will grant write access to *all* {{kib}} apps. If you want to limit write access to the {{synthetics-app}} only, refer to [Limited write access](#synthetics-write-privileges-limited).
     ::::
 
@@ -36,7 +36,7 @@ Create a **writer role**, called something like `synthetics_writer`:
 
 
 
-## Limited write access [synthetics-write-privileges-limited] 
+## Limited write access [synthetics-write-privileges-limited]
 
 If you want to limit write access to the {{synthetics-app}} only, do *not* use the `editor` [built-in role](../../../deploy-manage/users-roles/cluster-or-deployment-auth/built-in-roles.md).
 
@@ -51,7 +51,7 @@ Instead to you can create a writer role, called something like `synthetics_write
 Additional privileges will depend on the factors below.
 
 
-### To restrict using Elastic’s global managed infrastructure [disable-managed-locations] 
+### To restrict using Elastic’s global managed infrastructure [disable-managed-locations]
 
 To restrict users assigned this role from using monitors hosted on Elastic’s global managed infrastructure:
 
@@ -60,7 +60,7 @@ To restrict users assigned this role from using monitors hosted on Elastic’s g
 3. Uncheck *Elastic managed locations enabled*.
 
 
-### If using Private Locations [synthetics-role-write-private-locations] 
+### If using Private Locations [synthetics-role-write-private-locations]
 
 The user who initially sets up a new Private Location needs additional privileges. Users who create or update monitors hosted on that Private Location do not need any additional permissions.
 
@@ -72,9 +72,9 @@ The user who is setting up a new Private Location will need the following privil
 | [Kibana](../../../deploy-manage/users-roles/cluster-or-deployment-auth/kibana-privileges.md) | `Integrations`: `read` | Access to Integrations in {{kib}}. |
 
 
-### If using projects [_if_using_projects] 
+### If using projects [_if_using_projects]
 
-If the user should be able to create and update monitors using [projects](get-started.md#choose-projects), add *at least one* of following privileges:
+If the user should be able to create and update monitors using [projects](get-started.md#observability-synthetics-get-started-synthetics-project), add *at least one* of following privileges:
 
 | Type | Privilege | Purpose |
 | --- | --- | --- |