Skip to content

Commit

Permalink
fix(Infinite Tracing): Make regions bold so we can read them
Browse files Browse the repository at this point in the history
  • Loading branch information
rhetoric101 committed Mar 15, 2022
1 parent 1de81f9 commit ddbdfff
Showing 1 changed file with 14 additions and 14 deletions.
Expand Up @@ -34,13 +34,13 @@ To create a new trace observer if you're using New Relic APM agents or third-par
2. Select an account in the upper-left dropdown. If you have access to multiple accounts, make sure you're in the account where you want Infinite Tracing enabled.
3. If no trace observers are already present, click **New trace observer** to add one, fill out the information, and click **Create**. Note that we offer the following regions:

* eu-central-1 (EU): Select this region if you are collecting data from EU requests and you have an EU-based New Relic account that reports in EU data centers.
* us-east-1 (US)
* us-west-2 (US)
* eu-west-1 (US): Select this region if you are collecting data from EU requests and you have a US-based New Relic account that reports in US data centers.
* ap-southeast-1 (US)
* ap-southeast-2 (US)
* us-east-2 (US, FedRAMP)
* **eu-central-1 (EU):** Select this region if you are collecting data from EU requests and you have an EU-based New Relic account that reports in EU data centers.
* **us-east-1 (US)**
* **us-west-2 (US)**
* **eu-west-1 (US):** Select this region if you are collecting data from EU requests and you have a US-based New Relic account that reports in US data centers.
* **ap-southeast-1 (US)**
* **ap-southeast-2 (US)**
* **us-east-2 (US, FedRAMP)**

4. Under the **Endpoints** dropdown, copy the endpoint value under **For other integrations** and have it ready. This value is referenced in our code examples as <var>YOUR_TRACE_OBSERVER_URL</var>. This is used to test the [trace observer](#sample-payload), as well as to configure our [telemetry integrations](/docs/distributed-tracing/enable-configure/quick-start) and for sending data via the [Trace API](/docs/distributed-tracing/trace-api/introduction-trace-api/).

Expand Down Expand Up @@ -179,13 +179,13 @@ If you haven't already set up a trace observer, complete the following:
2. Select an account in the upper-left dropdown. If you have access to multiple accounts, make sure you're in the account where you want Infinite Tracing enabled.
3. If no trace observers are already present, click **New trace observer** to add one, fill out the information, and click **Create**. Note that we offer the following regions:

* eu-central-1 (EU): Select this region if you are collecting data from EU requests and you have an EU-based New Relic account that reports in EU data centers.
* us-east-1 (US)
* us-west-2 (US)
* eu-west-1 (US): Select this region if you are collecting data from EU requests and you have a US-based New Relic account that reports in US data centers.
* ap-southeast-1 (US)
* ap-southeast-2 (US)
* us-east-2 (US, FedRAMP)
* **eu-central-1 (EU):** Select this region if you are collecting data from EU requests and you have an EU-based New Relic account that reports in EU data centers.
* **us-east-1 (US)**
* **us-west-2 (US)**
* **eu-west-1 (US):** Select this region if you are collecting data from EU requests and you have a US-based New Relic account that reports in US data centers.
* **ap-southeast-1 (US)**
* **ap-southeast-2 (US)**
* **us-east-2 (US, FedRAMP)**

4. Under the **Endpoints** dropdown, copy the endpoint value under **For other integrations** and have it ready. This value is referenced in our code examples as <var>YOUR_TRACE_OBSERVER_URL</var>. This is used to test the [trace observer](#sample-payload).

Expand Down

0 comments on commit ddbdfff

Please sign in to comment.