From ddbdfff90c8ec4fd3383fb4aa90816d4b313e78a Mon Sep 17 00:00:00 2001 From: rhetoric101 Date: Tue, 15 Mar 2022 12:42:33 -0700 Subject: [PATCH] fix(Infinite Tracing): Make regions bold so we can read them --- .../infinite-tracing/set-trace-observer.mdx | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx b/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx index 09e641a3ff7..a81c4436e76 100644 --- a/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx +++ b/src/content/docs/distributed-tracing/infinite-tracing/set-trace-observer.mdx @@ -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 YOUR_TRACE_OBSERVER_URL. 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/). @@ -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 YOUR_TRACE_OBSERVER_URL. This is used to test the [trace observer](#sample-payload).