Merge pull request #2213 from splunk/tcarter-fix-broken-links

tcarter-fix-broken-links
splunk · Aug 5, 2024 · 2902e09 · 2902e09
2 parents 30c8e87 + 77ae2c9
commit 2902e09
Show file tree

Hide file tree

Showing 9 changed files with 14 additions and 15 deletions.
diff --git a/admin/notif-services/splunkoncall.rst b/admin/notif-services/splunkoncall.rst
@@ -55,7 +55,7 @@ Step 2: Get your Splunk On-Call alert routing key
 
 You must be a Splunk On-Call global admin or alert admin to complete this task.
 
-For information about how to get your Splunk On-Call alert routing key, see :new-page:`Create & Manage Alert Routing Keys <https://help.victorops.com/knowledge-base/spoc-routing-keys/>`.
+For information about how to get your Splunk On-Call alert routing key, see :ref:`spoc-routing-keys`.
 
 You'll need your alert routing key in :ref:`oncall3`.
 

diff --git a/sp-oncall/admin/sso/single-sign-sso.rst b/sp-oncall/admin/sso/single-sign-sso.rst
@@ -67,10 +67,10 @@ Azure Active Directory (SAML-based Sign-on)
 
 If you are configuring SSO for Azure Active Directory, use the following values:
 
--  Identifier: https://victorops.com
--  Reply URL: https://sso.victorops.com/sp/ACS.saml2
--  Sign on URL: https://portal.victorops.com/auth/sso/<<org-slug-here>>
--  Relay State: https://portal.victorops.com/auth/sso/<<org-slug-here>>
+-  Identifier: :samp:`https://victorops.com`
+-  Reply URL: :samp:`https://sso.victorops.com/sp/ACS.saml2`
+-  Sign on URL: :samp:`https://portal.victorops.com/auth/sso/<<org-slug-here>>`
+-  Relay State: :samp:`https://portal.victorops.com/auth/sso/<<org-slug-here>>`
 
 
 .. _sso-aws-spoc:

diff --git a/sp-oncall/admin/sso/sp-sso-google.rst b/sp-oncall/admin/sso/sp-sso-google.rst
@@ -67,9 +67,9 @@ To configure SSO for Splunk On-Call using Google Apps:
        :alt: Splunk On-Call SSO Google Apps Setup 5
 
 #. In the :guilabel:`Service Provider Details` step, enter the following values:
-   - in the :guilabel:`ACS URL` field: https://sso.victorops.com:443/sp/ACS.saml2
-   - in the :guilabel:`Entity ID` field: victorops.com
-   - in the :guilabel:`Start URL` field, enter the following with the correct Organization Slug at the end: https://portal.victorops.com/auth/sso/<<org-slug-here>>.
+   - in the :guilabel:`ACS URL` field: :samp:`https://sso.victorops.com:443/sp/ACS.saml2`
+   - in the :guilabel:`Entity ID` field: :samp:`victorops.com`
+   - in the :guilabel:`Start URL` field, enter the following with the correct Organization Slug at the end: :samp:`https://portal.victorops.com/auth/sso/<<org-slug-here>>.`
 
 
 #. Skip the attribute mapping step and select :guilabel:`Finish`.

diff --git a/sp-oncall/admin/sso/sp-sso-users.rst b/sp-oncall/admin/sso/sp-sso-users.rst
@@ -85,7 +85,7 @@ How to break your SSO linkage
 
 If you are receiving an error when trying to log into Splunk On-Call through SSO you may need to break the linkage between your Splunk On-Call username and password and your SSO provider.
 
-To break the linkage, ensure you are signed in to your IDP and then paste the following link into the address bar of your browser: https://portal.victorops.com/do-defederation . If the link between your Splunk On-Call credentials and your SSO provider is successfully broken, you will see the error, shown below.
+To break the linkage, ensure you are signed in to your IDP and then paste the following link into the address bar of your browser: :samp:`https://portal.victorops.com/do-defederation` . If the link between your Splunk On-Call credentials and your SSO provider is successfully broken, you will see the error, shown below.
 
 .. note:: You may have to paste the defederation link into your browser multiple times before the below error message will appear.
 

diff --git a/sp-oncall/spoc-integrations/catchpoint-integration.rst b/sp-oncall/spoc-integrations/catchpoint-integration.rst
@@ -74,8 +74,7 @@ In Catchpoint
 .. image:: /_images/spoc/Screenshot-2017-05-18-15.43.31.png
    :alt: An arrow points to a green buttoned stating "Save".
 
-If you're looking for additional variables to add to your payload,
-seek out the Alert Webhook Macros in :new-page:`the support section of the Catchpoint platform <https://support.catchpoint.com/>`.
+If you're looking for additional variables to add to your payload, log into your Catchpoint account and seek out the Alert Webhook Macros.
 You can add as many variables as you want, but customizing the
 parameters of the existing Template might result in degraded
 functionality.
diff --git a/sp-oncall/spoc-integrations/grafana-integration.rst b/sp-oncall/spoc-integrations/grafana-integration.rst
@@ -81,7 +81,7 @@ For those with Enterprise Splunk On-Call features, you can include the Grafana i
       :alt: include grafana image of alert in victorops
       :width: 65%
 
-#. In Splunk On-Call, go to :guilabel:`Settings` then :guilabel:`Alert Rules Engine` and add the following Rules Engine rule to surface the image_url as an annotation to the incident. Ensure that the image is hosted in a publicly accessible location so that Splunk On-Call can display it. For further information, see :new-page:`Enable images in notification <https://grafana.com/docs/grafana/latest/alerting/old-alerting/notifications/#external-image-store>` in Grafana documentation.
+#. In Splunk On-Call, go to :guilabel:`Settings` then :guilabel:`Alert Rules Engine` and add the following Rules Engine rule to surface the image_url as an annotation to the incident. Ensure that the image is hosted in a publicly accessible location so that Splunk On-Call can display it. For further information, see :new-page:`Use images in notifications <https://grafana.com/docs/grafana/latest/alerting/configure-notifications/template-notifications/images-in-notifications/>` in Grafana documentation.
 
    .. image:: /_images/spoc/Screen-Shot-2020-06-24-at-4.37.01-PM.png
       :width: 65%

diff --git a/sp-oncall/spoc-integrations/jira-app-integration-guide-victorops.rst b/sp-oncall/spoc-integrations/jira-app-integration-guide-victorops.rst
@@ -44,7 +44,7 @@ Configuring Application Settings
 2. In the **API ID** field in the same section, insert the API ID you
    noted in the Splunk On-Call step above.
 3. Copy the Splunk On-Call Org ID displayed in your VictorOps URL
-   (e.g. https://portal.victorops.com/client/%7BOrg_ID}) and paste it in
+   (for example :samp:`https://portal.victorops.com/client/%7BOrg_ID`) and paste it in
    Jira's **Organization ID** field. This is appended to the incident
    link within Jira tickets.
 4. Once all three fields have been populated, click **Connect**.  On

diff --git a/...-integrations/setup-single-sign-on-sso-and-user-provisioning-with-okta-beta.rst b/...-integrations/setup-single-sign-on-sso-and-user-provisioning-with-okta-beta.rst
@@ -136,7 +136,7 @@ Org Slug” is the organization identifier.
 
 -  In the **Default RelayState** text box add:
 
-https://portal.victorops.com/auth/ulm/sso/**{your-org-identifier}**
+   :samp:`https://portal.victorops.com/auth/ulm/sso/<your-org-identifier>`
 
 -  In the field **Organization identifier** enter just the
    org-identifier

diff --git a/sp-oncall/spoc-integrations/splunking-victorops-data.rst b/sp-oncall/spoc-integrations/splunking-victorops-data.rst
@@ -446,7 +446,7 @@ The Content Type field should be set to application/json
 
 The body of each webhook will vary according to the event-type. Be sure
 to replace your org slug (organization id found in the url of victorops,
-e.g. https://portal.victorops.com/dash/<org_slug>/outgoing-webhooks) in
+such as :samp:`https://portal.victorops.com/dash/<org_slug>/outgoing-webhooks`) in
 all instance of <org_slug>.
 
 --------------