Skip to content
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

Pulling refs/heads/main into main #1079

Merged
merged 3 commits into from
Dec 5, 2023
Merged

Pulling refs/heads/main into main #1079

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
adebde6
Merge pull request #1571 from splunk/repo-sync
theletterf Dec 4, 2023
02ba3fa
reformat
gschatz-splunk Dec 4, 2023
2d0aa9f
Merge pull request #1572 from splunk/gschatz-O11YDOCS-5383
gschatz-splunk Dec 4, 2023
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
21 changes: 14 additions & 7 deletions synthetics/test-config/public-locations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,40 +11,47 @@ Public locations are global checkpoints from which you can run synthetic tests t

Splunk Synthetic Monitoring partners with infrastructure and connectivity providers around the world to create a global network of checkpoints from which to run tests. You can configure each of your tests to run from any or all of the available monitoring locations.

The following table provides a full list of locations, available in Splunk Synthetic Monitoring, along with their DNS, region code, and IP address. You can use this information to exclude locations from your site analytics or add them to your browser's allow list.
Best practices
===============
Locations denoted with `Amazon (Local Zone)` as the Provider are located in AWS Local Zones and the display names are prefixed with `AWS LZ`. These locations have less redundancy than other Amazon locations and are primarily intended for performance testing. If uptime testing is required, run the tests concurrently with multiple locations.


Locations
===========

The following tables provide a full list of locations, available in Splunk Synthetic Monitoring, along with their DNS, region code, and IP address. You can use this information to exclude locations from your site analytics or add them to your browser's allow list.

Locations denoted with `Amazon (Local Zone)` as the Provider are located in AWS Local Zones and the display names are prefixed with `AWS LZ`. These locations have less redundancy than other Amazon locations and are primarily intended to be used for performance testing. If uptime testing is required, run the tests concurrently with multiple locations.

AU0
============
----
.. csv-table::
:file: au0-public-locations.csv
:widths: 10, 10, 10, 10, 20
:header-rows: 1

EU0
============
----
.. csv-table::
:file: eu0-public-locations.csv
:widths: 10, 10, 10, 10, 20
:header-rows: 1

JP0
============
----
.. csv-table::
:file: jp0-public-locations.csv
:widths: 10, 10, 10, 10, 20
:header-rows: 1

US0
============
----
.. csv-table::
:file: us0-public-locations.csv
:widths: 10, 10, 10, 10, 20
:header-rows: 1

US1
============
----
.. csv-table::
:file: us1-public-locations.csv
:widths: 10, 10, 10, 10, 20
Expand Down