semantic tagging for ui strings - partners, pr gates, product analytics, profiler (#37712)

Author: cswatt

content/en/partners/cloud_cost_management/aws.md

@@ -51,7 +51,7 @@ To create a billing conductor CUR, follow the [AWS Cost and Usage Reports user g
 Before starting, verify the following:
 
 **MSP access**  
-Access to the **management account** to configure Billing Conductor (Pricing Rules, Pricing Plans, Billing Groups).
+Access to the **management account** to configure Billing Conductor ({{< ui >}}Pricing Rules{{< /ui >}}, {{< ui >}}Pricing Plans{{< /ui >}}, {{< ui >}}Billing Groups{{< /ui >}}).
 
 **Customer permissions**  
 The customer must have permission to:
@@ -69,22 +69,22 @@ These steps **must be completed in the MSP’s management account**.
 
 ### Step 1 - Create a pricing rule
 
-Billing Conductor computes pro forma costs by adjusting **AWS public on‑demand rates** using a **Discount** or **Markup**.
+Billing Conductor computes pro forma costs by adjusting **AWS public on‑demand rates** using a {{< ui >}}Discount{{< /ui >}} or {{< ui >}}Markup{{< /ui >}}.
 
 You must explicitly choose between these options:
-- **Discount**: applies a percentage discount to public on-demand  
-- **Markup**: applies a percentage increase to public on-demand  
+- {{< ui >}}Discount{{< /ui >}}: applies a percentage discount to public on-demand  
+- {{< ui >}}Markup{{< /ui >}}: applies a percentage increase to public on-demand  
 
 <div class="alert alert-info">
-Entering 0% (whether Discount or Markup) results in public on-demand pricing. The allowed range is 0-100%.
+Entering 0% (whether {{< ui >}}Discount{{< /ui >}} or {{< ui >}}Markup{{< /ui >}}) results in public on-demand pricing. The allowed range is 0-100%.
 </div>
 
 For example:
 
 | Type | Calculation |
 |------|-------------|
-| Discount (20%) | public on-demand × 0.8 |
-| Markup (30%) | public on-demand × 1.3 |
+| {{< ui >}}Discount{{< /ui >}} (20%) | public on-demand × 0.8 |
+| {{< ui >}}Markup{{< /ui >}} (30%) | public on-demand × 1.3 |
 
 ### Step 2 - Create a pricing plan
 
@@ -119,35 +119,35 @@ Because of this limitation, the customer must modify the template before deploym
 ### Step 2 - Deploy the CloudFormation stack in AWS
 
 1. Use the template above and deploy a stack in the customer’s member account.
-2. To deploy the stack, follow the AWS documentation: [Create a stack from the CloudFormation][7]. When creating the stack, choose: **With new resources (standard)**.
+2. To deploy the stack, follow the AWS documentation: [Create a stack from the CloudFormation][7]. When creating the stack, choose: {{< ui >}}With new resources (standard){{< /ui >}}.
 
 ### Step 3 - Configure the Cost and Usage Report settings in AWS
 
 Enter the following information during deployment:
-- **Bucket Name**: S3 bucket where CUR files are stored  
-- **Bucket Region**: AWS region of that bucket (for example, `us-east-1`)  
-- **Export Path Prefix**: S3 path prefix for CUR files  
-- **Export Name**: Name of the Cost and Usage Report  
+- {{< ui >}}Bucket Name{{< /ui >}}: S3 bucket where CUR files are stored  
+- {{< ui >}}Bucket Region{{< /ui >}}: AWS region of that bucket (for example, `us-east-1`)  
+- {{< ui >}}Export Path Prefix{{< /ui >}}: S3 path prefix for CUR files  
+- {{< ui >}}Export Name{{< /ui >}}: Name of the Cost and Usage Report  
 
 These values define where AWS writes the CUR and where Datadog reads it.
 
 ### Step 4 - Enter the member account's CUR parameters in Datadog
 
-1. After deploying the CloudFormation stack, navigate to **Datadog → Cloud Cost → Settings → [Accounts][8]**.
+1. After deploying the CloudFormation stack, navigate to {{< ui >}}Datadog{{< /ui >}} → {{< ui >}}Cloud Cost{{< /ui >}} → {{< ui >}}Settings{{< /ui >}} → [{{< ui >}}Accounts{{< /ui >}}][8].
 
 
    {{< img src="partners/cloud_cost/select_aws_account_ccm.png" alt="Select AWS Account for CCM" style="width:100%;" >}}
 
 2. Select the member account and enter the following fields using the exact values from **Step 3**:
-   - Bucket Name  
-   - Bucket Region
-   - Export Path Prefix
-   - Export Name
+   - {{< ui >}}Bucket Name{{< /ui >}}  
+   - {{< ui >}}Bucket Region{{< /ui >}}
+   - {{< ui >}}Export Path Prefix{{< /ui >}}
+   - {{< ui >}}Export Name{{< /ui >}}
 
-3. Skip the **Create CloudFormation stack step** (the stack was already deployed in **Step 3**).
+3. Skip the {{< ui >}}Create CloudFormation stack step{{< /ui >}} (the stack was already deployed in **Step 3**).
 
 
-4. Click **Activate now** to activate CCM for the member account.
+4. Click {{< ui >}}Activate now{{< /ui >}} to activate CCM for the member account.
 
 
 {{< img src="partners/cloud_cost/configure_aws_ccm.png" alt="Configure AWS Cloud Cost Management" style="width:100%;" >}}
@@ -159,8 +159,8 @@ After configuration is complete, the account status updates as shown below.
 ## Validation
 
 After activation, verify that cost data is flowing into Datadog:
-1. Go to **[Cloud Cost > Cost Explorer][9]** in Datadog.
-2. Select **AWS** as the provider, then use filters such as **Product**, **Member Accoun Id**, or other dimensions to group and validate the data.
+1. Go to [{{< ui >}}Cloud Cost{{< /ui >}} > {{< ui >}}Cost Explorer{{< /ui >}}][9] in Datadog.
+2. Select {{< ui >}}AWS{{< /ui >}} as the provider, then use filters such as {{< ui >}}Product{{< /ui >}}, {{< ui >}}Member Accoun Id{{< /ui >}}, or other dimensions to group and validate the data.
 3. Confirm that cost data appears for the expected time range.
 
 

content/en/partners/getting_started/laying-the-groundwork.md

@@ -62,7 +62,7 @@ As a result:
 
 There are two options for this step:
 
-- Use the UI: Click "New Organization" as described in [Managing Multiple Organization Accounts][1].
+- Use the UI: Click {{< ui >}}New Organization{{< /ui >}} as described in [Managing Multiple Organization Accounts][1].
 - Use the API: Use the [Create a child organization][18] endpoint.
 
 ### Retrieve the new client org's org ID
@@ -89,7 +89,7 @@ There are two options for this step:
 
 ### Register the new client details in the DPN portal
 
-- Log in to the [DPN portal][16] and click `+Register Deal` on the Deal Dashboard.
+- Log in to the [DPN portal][16] and click {{< ui >}}+Register Deal{{< /ui >}} on the {{< ui >}}Deal Dashboard{{< /ui >}}.
 
 - Enter the new client details including the new client organization's Org ID to register the new client org.
 

content/en/partners/sales-enablement.md

@@ -6,7 +6,7 @@ The Datadog Partner Network provides many resources for partners. This is a guid
 
 ## Datadog basics
 
-First, head over to the [Partner Portal][1]. Log in and click **Training**. Under Sales Certification, click **Get started today**.
+First, head over to the [Partner Portal][1]. Log in and click {{< ui >}}Training{{< /ui >}}. Under {{< ui >}}Sales Certification{{< /ui >}}, click {{< ui >}}Get started today{{< /ui >}}.
 
 {{<img src="partners/portal_sales_go.png" alt="Partner Portal Sales Certification" style="max-width:734px">}}
 
@@ -58,7 +58,7 @@ In order to complete your quote, you need pricing basics.
 
 - [Datadog's pricing][3] describes how pricing works, including the units of measurement and the metering approach at Datadog.
 - [Customer plans][4] provides details about standard end-customer pricing options.
-- Finally, to understand discounts offered, check out the Partner Portal pricing tab:
+- Finally, to understand discounts offered, check out the Partner Portal {{< ui >}}pricing{{< /ui >}} tab:
 
 {{<img src="partners/portal_pricing_go.png" alt="Partner Portal Pricing Info" style="max-width:734px">}}
 

content/en/pr_gates/_index.md

@@ -122,7 +122,7 @@ To create a PR Gate rule, see the [Setup documentation][7].
 
 ## Manage rules
 
-You can manage and update PR Gates rules on the [**PR Gates Rules**][8] page. Improve your security and quality practices based on your project requirements and risk tolerances. 
+You can manage and update PR Gates rules on the [{{< ui >}}PR Gates Rules{{< /ui >}}][8] page. Improve your security and quality practices based on your project requirements and risk tolerances. 
 
 You can see all of the rules defined by the organization.
 

content/en/pr_gates/setup/_index.md

@@ -11,7 +11,7 @@ further_reading:
 
 ## Overview
 
-To use Datadog PR Gates, you can define one or more rules on the [**PR Gate Rules**][1] page.
+To use Datadog PR Gates, you can define one or more rules on the [{{< ui >}}PR Gate Rules{{< /ui >}}][1] page.
 
 {{< img src="pr_gates/rules_list_3.png" alt="PR Gates page in Datadog" style="width:100%" >}}
 
@@ -21,34 +21,34 @@ PR Gates ensure that only the code changes that meet your security and quality s
 
 To create a PR Gates rule in Datadog:
 
-1. Navigate to [**Software Delivery** > **PR Gates** > **PR Gate Rules**][1] and click **New Rule**.
+1. Navigate to [{{< ui >}}Software Delivery{{< /ui >}} > {{< ui >}}PR Gates{{< /ui >}} > {{< ui >}}PR Gate Rules{{< /ui >}}][1] and click {{< ui >}}New Rule{{< /ui >}}.
 
-1. Under **Select your source**, select a rule type:
-   - Static Code Analysis (SAST)
-   - Software Composition Analysis (SCA)
-   - Code Coverage
-   - Infrastructure as Code Scanning (IaC)
-   - Secret Scanning
-   - New Flaky Tests
+1. Under {{< ui >}}Select your source{{< /ui >}}, select a rule type:
+   - {{< ui >}}Static Code Analysis (SAST){{< /ui >}}
+   - {{< ui >}}Software Composition Analysis (SCA){{< /ui >}}
+   - {{< ui >}}Code Coverage{{< /ui >}}
+   - {{< ui >}}Infrastructure as Code Scanning (IaC){{< /ui >}}
+   - {{< ui >}}Secret Scanning{{< /ui >}}
+   - {{< ui >}}New Flaky Tests{{< /ui >}}
 
-1. Under **Define condition**, set the conditions that will cause the rule to fail. Each rule type has its own condition options, and you can use the existing default condition settings when you select a rule type.
+1. Under {{< ui >}}Define condition{{< /ui >}}, set the conditions that will cause the rule to fail. Each rule type has its own condition options, and you can use the existing default condition settings when you select a rule type.
 
-1. Under **Define scope**, set which repositories the rule should evaluate:
-   - **All repositories**: The rule evaluates all repositories configured for the rule type.
-   - **Selected repositories**: The rule evaluates only the repositories you specify. Use `IN` to include only specified repositories, or `NOT IN` to evaluate all configured repositories _except_ the ones you specify.
+1. Under {{< ui >}}Define scope{{< /ui >}}, set which repositories the rule should evaluate:
+   - {{< ui >}}All repositories{{< /ui >}}: The rule evaluates all repositories configured for the rule type.
+   - {{< ui >}}Selected repositories{{< /ui >}}: The rule evaluates only the repositories you specify. Use `IN` to include only specified repositories, or `NOT IN` to evaluate all configured repositories _except_ the ones you specify.
 
    The following example illustrates a Static Code Analysis (SAST) rule that fails when a pull request introduces at least one Static Code Analysis code vulnerability violation with at least `Critical` severity. The rule evaluates all repositories configured for Static Code Analysis:
 
    {{< img src="pr_gates/setup/static_analysis_4.png" alt="A Static Code Analysis rule that runs on all repos and fails when a PR has at least one Static Code Analysis code vulnerability with at least `Critical` severity" style="width:100%" >}}
 
-1. Under **Preview checks**, select your source code management provider to preview the status check to be added to pull requests. To set the check so it blocks PRs when it fails, follow your provider's instructions for making a status check _required_:
+1. Under {{< ui >}}Preview checks{{< /ui >}}, select your source code management provider to preview the status check to be added to pull requests. To set the check so it blocks PRs when it fails, follow your provider's instructions for making a status check _required_:
 
    - [GitHub][2]
    - [Azure DevOps][3]
 
    Non-blocking rules can be helpful when you roll out a new rule and want to verify its behavior before making it blocking.
 
-1. Click **Create Rule**.
+1. Click {{< ui >}}Create Rule{{< /ui >}}.
 
 1. It is recommended that you test your PR Gate rule by creating a new branch and PR that purposely introduces code changes that would violate the rule's condition. Please note that PR Gates will not:
    - Retroactively block existing PRs unless new commits are pushed to them after the PR Gate rule has been created
@@ -69,7 +69,7 @@ To make these checks blocking, they must be set as required in the branch polici
 
 ## Manage rules
 
-You can edit or delete a PR Gates rule by hovering over it on the [**PR Gates Rules**][1] list and clicking the **Edit** or **Delete** icon.
+You can edit or delete a PR Gates rule by hovering over it on the [{{< ui >}}PR Gates Rules{{< /ui >}}][1] list and clicking the {{< ui >}}Edit{{< /ui >}} or {{< ui >}}Delete{{< /ui >}} icon.
 
 {{< img src="pr_gates/setup/delete_3.png" alt="Edit, clone, or delete a PR Gates rule" style="width:100%;">}}
 

content/en/product_analytics/_index.md

@@ -66,9 +66,9 @@ After you set up client-side collection, you can use the [Product Analytics API]
 
 For each application you want to monitor user behavior for, enable Product Analytics:
 
-1. In Datadog, go to **Digital Experience** > **Real User Monitoring** > [**Manage Applications**][9]. In the list of applications under **Active**, select the application you want to monitor.
-2. Under PRODUCT SETTINGS, click **Product Analytics**.
-3. Click the **Enable** button.
+1. In Datadog, go to {{< ui >}}Digital Experience{{< /ui >}} > {{< ui >}}Real User Monitoring{{< /ui >}} > [{{< ui >}}Manage Applications{{< /ui >}}][9]. In the list of applications under {{< ui >}}Active{{< /ui >}}, select the application you want to monitor.
+2. Under {{< ui >}}PRODUCT SETTINGS{{< /ui >}}, click {{< ui >}}Product Analytics{{< /ui >}}.
+3. Click the {{< ui >}}Enable{{< /ui >}} button.
 
 {{< img src="product_analytics/enable-product-analytics.png" alt="Enable Product Analytics from the Application Management page.">}}
 
@@ -82,10 +82,10 @@ The Datadog SDK automatically collects three levels of client-side user data: Se
 : A view represents each page or screen a user visits within a session.
 
 **Actions**
-: An action is something a user does on a page, such as a click, tap, or scroll. Actions are automatically collected by the RUM SDK. When configuring features like [Funnels][4] and [Segments][6], you can select specific Actions as steps or filters. To see which Actions are available, open the [RUM Explorer][20] and filter by **Actions**.
+: An action is something a user does on a page, such as a click, tap, or scroll. Actions are automatically collected by the RUM SDK. When configuring features like [Funnels][4] and [Segments][6], you can select specific Actions as steps or filters. To see which Actions are available, open the [RUM Explorer][20] and filter by {{< ui >}}Actions{{< /ui >}}.
 
 **Server-side events**
-: A server-side event is a custom event sent through the [Product Analytics API][21], such as a completed checkout or processed payment. In the event picker, select **Server Events** to scope your analysis to server-side data.
+: A server-side event is a custom event sent through the [Product Analytics API][21], such as a completed checkout or processed payment. In the event picker, select {{< ui >}}Server Events{{< /ui >}} to scope your analysis to server-side data.
 
 ## Navigate the Product Analytics UI
 Each Product Analytics feature provides context about your users' journeys.

content/en/product_analytics/action_management.md

@@ -27,21 +27,21 @@ Visual labeling requires [the Datadog test recorder Chrome extension][1]. If you
 
 1. Go to the [Actions][3] page in Datadog and select your application.
 
-2. Select **Visual Labeler**.
+2. Select {{< ui >}}Visual Labeler{{< /ui >}}.
 
-3. Use the **Navigate Site** mode to browse to the location of the actions you want to label.
+3. Use the {{< ui >}}Navigate Site{{< /ui >}} mode to browse to the location of the actions you want to label.
 
-4. When you are ready to label an action, switch to **Label Actions** mode.
+4. When you are ready to label an action, switch to {{< ui >}}Label Actions{{< /ui >}} mode.
 
 5. Click on the element you would like to add as an action.
 
    {{< img src="product_analytics/action_management/pana-label-mode-2.png" alt="Click on and label your actions." style="width:90%;">}}
 
-6. Select **New Labeled Action** and use the modal to define the scope of your label. Add a label name, description (optional), and tags (optional). You can specify a custom CSS selector for tracking clicks, or use the CSS builder to label events, for more control and granularity.
+6. Select {{< ui >}}New Labeled Action{{< /ui >}} and use the modal to define the scope of your label. Add a label name, description (optional), and tags (optional). You can specify a custom CSS selector for tracking clicks, or use the CSS builder to label events, for more control and granularity.
 
    You can also hold the Shift key to select multiple actions on the page and label them under the same name. This functionality enables "OR" analysis.
 
-7. Select **Save**.
+7. Select {{< ui >}}Save{{< /ui >}}.
 
 After you define an action, it appears in the list of labeled actions on the [Actions][3] page, and you can use it in any Product Analytics chart.
 
@@ -50,13 +50,13 @@ After you define an action, it appears in the list of labeled actions on the [Ac
 Manual labeling is available for both web and mobile applications and does not require the Chrome extension.
 
 1. Go to the [Actions][3] page in Datadog and select your application. 
-2. Select **Add Labeled Action**, then select **Create manually**.
+2. Select {{< ui >}}Add Labeled Action{{< /ui >}}, then select {{< ui >}}Create manually{{< /ui >}}.
 3. Add a label name, description (optional), and tags (optional).
-4. Under **Definition**, define one or more events to track:
-   - **Action Type**: `click` or `custom` events. For `click` events, you can specify a custom CSS selector for tracking clicks, or use the CSS builder to label events, for more control and granularity. 
-   - **Action Name**: Use the drop-down to select an action
-   - **Page Location**: Use the drop-down to target one or more pages
-   Select **Add New Definition** to add a definition.
+4. Under {{< ui >}}Definition{{< /ui >}}, define one or more events to track:
+   - {{< ui >}}Action Type{{< /ui >}}: `click` or `custom` events. For `click` events, you can specify a custom CSS selector for tracking clicks, or use the CSS builder to label events, for more control and granularity. 
+   - {{< ui >}}Action Name{{< /ui >}}: Use the drop-down to select an action
+   - {{< ui >}}Page Location{{< /ui >}}: Use the drop-down to target one or more pages
+   Select {{< ui >}}Add New Definition{{< /ui >}} to add a definition.
 5. Select **Save**.
 
 After you define an action, it appears in the list of labeled actions on the [Actions][3] page, and you can use it in any Product Analytics chart.

content/en/product_analytics/charts/analytics_explorer/events.md

@@ -16,11 +16,11 @@ The Product Analytics Explorer displays individual events in a side panel format
 
 General context information is provided at the top. Scroll to the waterfall to see the content of the event. 
 
-Context about your users and their applications, including the OS, country, code version, and more, is captured when the event is generated. Context also refers to the event itself, which includes information specific to the event type. For example, the event side panel shows the view path while the **Errors** side panel shows the error message.
+Context about your users and their applications, including the OS, country, code version, and more, is captured when the event is generated. Context also refers to the event itself, which includes information specific to the event type. For example, the event side panel shows the view path while the {{< ui >}}Errors{{< /ui >}} side panel shows the error message.
 
 ## Event side panel
 
-To open the event side panel in the [Analytics Explorer][1], click on a table row in the **List** visualization type. Alternatively, click in the side panel list displayed after you click on **Show related events**. 
+To open the event side panel in the [Analytics Explorer][1], click on a table row in the {{< ui >}}List{{< /ui >}} visualization type. Alternatively, click in the side panel list displayed after you click on {{< ui >}}Show related events{{< /ui >}}. 
 
 The event side panel displays all the information relative to a Product Analytics event. The waterfall displays related views and actions.