Merge pull request #1036 from wavefrontHQ/mari-rebranding

internal links and hidden pages

pages/doc/2023-52.x_release_notes.md

@@ -40,7 +40,7 @@ Example: An annotated screenshot of the create traces security policy for origin
 
 ### Onboarded Subscriptions
 
-**New Admin Permission and Service Role**: With this release, we introduce the **Admin** [permission](csp_permissions_overview.html#operations-for-applications-permissions) and [service role](csp_users_roles.html#operations-for-applications-service-roles-built-in). **Admin** users can manage the Tanzu Observability organization settings.
+**New Admin Permission and Service Role**: With this release, we introduce the **Admin** [permission](csp_permissions_overview.html#tanzu-observability-permissions) and [service role](csp_users_roles.html#tanzu-observability-service-roles-built-in). **Admin** users can manage the Tanzu Observability organization settings.
 
 
 ### Original and Onboarded Subscriptions

pages/doc/csp_api_tokens.md

@@ -92,7 +92,7 @@ To generate and manage the API tokens for an existing **service account**:
 
 As a user with the **Admin** service role, you can view and revoke the API tokens of any service account in your service instance.
 
-{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-an-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%}
+{% include warning.html content="If your original Tanzu Observability subscription was onboarded to VMware Cloud services, for backward compatibility, you might have some legacy Tanzu Observability API tokens that are associated with user accounts. It’s recommended that you incrementally [replace them with VMware Cloud services API tokens](csp_migration.html#how-to-replace-a-tanzu-observability-api-token-with-a-vmware-cloud-services-access-token)."%}
 
 1. Log in to your service instance as an **Admin** user.
 2. Click the gear icon <i class="fa fa-cog"/> on the toolbar and select **Accounts**.

pages/doc/csp_area_differences.md

@@ -161,7 +161,7 @@ Last sentence: Тo temporarily enable service accounts for your service instance
 
 For original subscriptions, using the Tanzu Observability REST API requires an API token associated with a user account or a service account. To generate API tokens for your user account you need the **API Tokens** permission. To generate API tokens for service accounts and to manage the API tokens in your Tanzu Observability organization, you need the **Accounts** permission.
 
-When your service is onboarded to VMware Cloud services and you want to access the Tanzu Observability REST API, you need a VMware Cloud services **access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens), authentication with a Tanzu Observability API token is also supported. However, using a VMware Cloud services **access token** is the recommended way as we will deprecate the service accounts in the future. To obtain an **access token**, you can:
+When your service is onboarded to VMware Cloud services and you want to access the Tanzu Observability REST API, you need a VMware Cloud services **access token**. In a few cases, when setting up a [limited list of integrations](integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens), authentication with a Tanzu Observability API token is also supported. However, using a VMware Cloud services **access token** is the recommended way as we will deprecate the service accounts in the future. To obtain an **access token**, you can:
 
 * Generate a VMware Cloud services API token associated with your user account and exchange it for an access token.
 
@@ -366,7 +366,7 @@ For details, see <a href="api_tokens.html">Manage API Tokens</a>.</p>
 <ul>
 <li>All users can view and revoke their own VMware Cloud services API tokens. For details, see <a href="https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-1BA71988-387C-42E1-8C98-EE2C1370826B.html">How do I manage my API tokens</a> in the VMware Cloud services documentation.</li>
 <li>Users with the VMware Cloud <strong>Organization Owner</strong> role can monitor the API tokens created in the organization and can set constraints for idle and maximum Time to live (TTL) for all newly created tokens. For details and instructions, see <a href="https://docs.vmware.com/en/VMware-Cloud-services/services/Using-VMware-Cloud-Services/GUID-3A9C29E0-460B-4586-B51A-084443A960D0.html">How do I manage API tokens in my Organization</a> in the VMware Cloud services documentation.</li>
-<li>Users with the <strong>Admin</strong> service role can view and revoke any Tanzu Observability API token in the service instance. For details, see <a href="csp_api_tokens.html#manage-the-operations-for-applications-api-tokens-in-your-service-instance">Managing the Tanzu Observability API Tokens in Your Service Instance</a>.</li>
+<li>Users with the <strong>Admin</strong> service role can view and revoke any Tanzu Observability API token in the service instance. For details, see <a href="csp_api_tokens.html#manage-the-tanzu-observability-api-tokens-in-your-service-instance">Managing the Tanzu Observability API Tokens in Your Service Instance</a>.</li>
 </ul></p>
 </td>
 </tr>
@@ -425,7 +425,7 @@ For details, see <a href="api_tokens.html">Manage API Tokens</a>.</p>
 <p><strong>Where</strong>: In the Tanzu Observability user interface.</p>
 <p><strong>How</strong>: As a user with the <strong>Proxies</strong> permission, you must configure the proxy to authenticate to Tanzu Observability with a Tanzu Observability API token that have the <strong>Proxies</strong> permission. For details, see <a href="proxies_installing.html#install-a-proxy-from-the-ui">Install a Proxy from the UI</a>.</p>
 </td>
-<td><strong>Note</strong>: The Wavefront proxy authenticates with a VMware Cloud services access token obtained from server to server OAuth app credentials or from a VMware Cloud services API token. Proxy authentication with a Tanzu Observability API token is still possible and supported only for a <a href="integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens">limited list of integrations</a>.
+<td><strong>Note</strong>: The Wavefront proxy authenticates with a VMware Cloud services access token obtained from server to server OAuth app credentials or from a VMware Cloud services API token. Proxy authentication with a Tanzu Observability API token is still possible and supported only for a <a href="integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens">limited list of integrations</a>.
 <p><strong>Who</strong>:
 <ul>
 <li>For proxy installation, users with the <strong>Proxies</strong> Tanzu Observability service role.</li>
@@ -451,7 +451,7 @@ In both ways, the access token is directly issued to the proxy. For details, see
 <p><strong>Where</strong>: In the Tanzu Observability user interface.</p>
 <p><strong>How</strong>: Follow the instructions on the <strong>Setup</strong> tab of the integration that you want to install.</p>
 </td>
-<td><strong>Note</strong>: <a href="integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens">Most of the integrations</a> that use a Wavefront proxy authenticate with a VMware Cloud services access token. A <a href="integrations_onboarded_subscriptions.html#integrations-that-use-operations-for-applications-api-tokens">limited list of integrations</a> still use proxy authentication with a Tanzu Observability API token.
+<td><strong>Note</strong>: <a href="integrations_onboarded_subscriptions.html#integrations-that-use-vmware-cloud-services-access-tokens">Most of the integrations</a> that use a Wavefront proxy authenticate with a VMware Cloud services access token. A <a href="integrations_onboarded_subscriptions.html#integrations-that-use-tanzu-observability-api-tokens">limited list of integrations</a> still use proxy authentication with a Tanzu Observability API token.
 <p><strong>Who</strong>: Users with the <strong>Proxies</strong> Tanzu Observability service role who must have one of the following:
 <ul>
 <li>A valid VMware Cloud services API token with the <strong>Proxies</strong> service role assigned.</li>

pages/doc/csp_getting_started.md

@@ -81,9 +81,9 @@ See [What organization roles are available in VMware Cloud Services](https://doc
 
 ## What Are Service Roles and Custom Roles?
 
-VMware Cloud services includes service-specific built-in roles, including [Tanzu Observability service roles](csp_users_roles.html#operations-for-applications-service-roles-built-in). A service role is required to grant certain access to the corresponding service instance in the organization.
+VMware Cloud services includes service-specific built-in roles, including [Tanzu Observability service roles](csp_users_roles.html#tanzu-observability-service-roles-built-in). A service role is required to grant certain access to the corresponding service instance in the organization.
 
-While the service roles are built-in and not editable, as a VMware Cloud **Organization Administrator** or **Organization Owner**, you can create [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role) with service permissions of your choice, including [Operations for Application permissions](csp_permissions_overview.html#operations-for-applications-permissions). Custom roles are optional and apply to all service instances for which the target user or server to server app has at least one service role.
+While the service roles are built-in and not editable, as a VMware Cloud **Organization Administrator** or **Organization Owner**, you can create [custom roles](csp_users_roles.html#create-edit-or-delete-a-custom-role) with service permissions of your choice, including [Operations for Application permissions](csp_permissions_overview.html#tanzu-observability-permissions). Custom roles are optional and apply to all service instances for which the target user or server to server app has at least one service role.
 
 ## What's a Server to Server App?
 

pages/doc/csp_invite-AoA-users_tutorial.md

@@ -58,10 +58,10 @@ If do not have the VMware Cloud **Organization Owner** or **Organization Adminis
 
 We provide a number of built-in Tanzu Observability service roles.
 
-- A corresponding service role for each [permission](csp_permissions_overview.html#operations-for-applications-permissions).
+- A corresponding service role for each [permission](csp_permissions_overview.html#tanzu-observability-permissions).
 - Two special service roles - one that grants full administrative access to the service, and another one that grants read-only access to the service.
 
-For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#operations-for-applications-service-roles-built-in).
+For more information, see [Tanzu Observability Roles (Built-in)](csp_users_roles.html#tanzu-observability-service-roles-built-in).
 
 ### Step 1: Enter the New User Details