Skip to content

[synthetics] Document private locations space awareness #4873

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 29, 2025
Merged

[synthetics] Document private locations space awareness #4873

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
199c572
document private locations space awareness
colleenmcginnis Apr 8, 2025
a4c7790
read @mdbirnstiehl's mind before he even reviews
colleenmcginnis Apr 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions docs/en/observability/synthetics-private-location.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,8 +147,11 @@ When the {agent} is running you can add a new {private-location} in {kib}:
. Find `Synthetics` in the {kibana-ref}/introduction.html#kibana-navigation-search[global search field].
. Click **Settings**.
. Click **{private-location}s**.
. Click **Add location**.
. Give your new location a unique _Location name_ and select the _Agent policy_ you created above.
. Click **Create location**.
. Give your new location a unique _Location name_.
. Select the _Agent policy_ you created above.
. (Optional) In _Tags_, select {kibana-ref}/managing-tags.html[tags] to assign to this location.
. (Optional) In _Spaces_, specify the {kibana-ref}/xpack-spaces.html[spaces] where this location will be available.
. Click **Save**.

IMPORTANT: It is not currently possible to use custom CAs for synthetics browser tests in private locations without following a workaround. To learn more about the workaround, refer to the following GitHub issue: https://github.com/elastic/synthetics/issues/717[elastic/synthetics#717].
Expand Down