fix broken links

Author: bhillmer

alerts-detectors-notifications/alert-condition-reference/custom-threshold.rst

@@ -25,7 +25,7 @@ When specifying compound conditions, AND conditions are applied before OR condit
 
 .. note:: For a compound condition to trigger an alert, all the values involved in the condition must be non-null.
 
-If you need to build more complex conditions than this alert condition supports, such as "a AND (b OR c) AND d", or "a AND NOT b", you can do so by using the :new-page:`Splunk Observability Cloud API <https://dev.splunk.com/observability/docs/detectors/detectors_events_alerts#Detectors>` to create the detector. 
+If you need to build more complex conditions than this alert condition supports, such as "a AND (b OR c) AND d", or "a AND NOT b", you can do so by using the :new-page:`Splunk Observability Cloud API <https://dev.splunk.com/observability/docs/detectors/detector_examples>` to create the detector. 
 
 
 .. _compare-signals:

alerts-detectors-notifications/create-detectors-for-alerts.rst

@@ -82,11 +82,12 @@ Create a detector using the API
 
 Using the API to create a detector provides a number of capabilities that are not available in the UI, letting you build detectors with more advanced rules and conditions. You can view these detectors in the UI. The program text appears in place of the signals displayed in standard detectors.
 
--  For general information on creating detectors using the API, see the :new-page:`Detect Anomalies with Detectors <https://dev.splunk.com/observability/docs/detectors/detectors_events_alerts/>` topic in the Splunk Observability Cloud Developer Guide.
+-  For general information on creating detectors using the API, see the :new-page:`Detect Anomalies with Detectors <https://dev.splunk.com/observability/docs/detectors>` topic in the Splunk Observability Cloud Developer Guide.
 
 -  For information on using the UI to edit detectors created using the API, see :ref:`v2-detector-signalflow`.
 
-.. note:: If a detector display includes a SignalFlow tab, you are viewing a detector created programmatically using the :new-page:`Splunk Observability Cloud Detectors API <https://dev.splunk.com/observability/reference/api/detectors/latest>`. If you are familiar with that API, you can use the detector display to view and edit the detector code and make changes to the detector rules.
+.. note:: If a detector display includes a SignalFlow tab, you are viewing a detector created programmatically using the :new-page:`Splunk Observability Cloud Detectors API <https://dev.splunk.com/observability/reference/api/detectors/latest>`. If you are familiar with that API, you can use the detector display to 
+   view and edit the detector code and make changes to the detector rules.
 
 
 .. _build-rules:

data-visualization/charts/chart-analytics-reference.rst

@@ -9,7 +9,7 @@ Functions reference for Splunk Observability Cloud
 
 You can run calculations on observability data and visualize the output in :ref:`charts <data-visualization-charts>` using :ref:`SignalFlow <get-started-signalflow>` analytics functions. To use analytics functions in your charts select :strong:`Add Analytics` in the :strong:`Plot Editor` tab.
 
-Use the following list to learn more about each SignalFlow analytics function, including sample calculations. To use analytics functions in SignalFlow programs, see the :new-page:`SignalFlow Functions and Methods <https://dev.splunk.com/observability/docs/signalflow/function_method_list>` topic in the Splunk Observability Cloud Developer Guide.
+Use the following list to learn more about each SignalFlow analytics function, including sample calculations. To use analytics functions in SignalFlow programs, see the :new-page:`SignalFlow Functions and Methods <https://dev.splunk.com/observability/docs/signalflow>` topic in the Splunk Observability Cloud Developer Guide.
 
 .. hlist::
    :columns: 3

sp-oncall/admin/get-started/custom-outbound-webhooks.rst

@@ -135,7 +135,7 @@ example, the condition occurs when the state_message contains the phrase “esca
 
 In the “Transform these alert fields” portion, we'll create a new field called “vo-webhook-field” and populate it with part of the destination URL you're sending the webhook to.
 
-In this example, the full destination URL we're hoping to send to is “https://dev.oscato.com/2tn6xfh” so we'll put “oscato.com” as the vo-webhook-field value.
+In this example, the full destination URL we're hoping to send to is “\https://dev.oscato.com/2tn6xfh” so we'll put “oscato.com” as the vo-webhook-field value.
 
 Next, you'll navigate to Outgoing Webhooks under :guilabel:`Integrations`, then :guilabel:`Outgoing Webhooks`. Select :guilabel:`Add Webhook`.
 

sp-oncall/spoc-integrations/hipchat-integration.rst

@@ -125,7 +125,7 @@ by posting to this URL”. Copy this URL to your clipboard. The URL
 contains two items we will need to use in later parts of this article,
 the room ID and the authentication token. Find them in bold here:
 
-https://**YOUR_DOMAIN**.hipchat.com/v2/room/**ROOM_ID**/notification?auth_token=\ **AUTH_TOKEN_HERE**
+\https://**YOUR_DOMAIN**.hipchat.com/v2/room/**ROOM_ID**/notification?auth_token=\ **AUTH_TOKEN_HERE**
 
 Save your new custom integration.
 
@@ -165,8 +165,7 @@ created in the Rules Engine. For example:
 https://**YOUR_DOMAIN**.hipchat.com/v2/room/:math:`{{ALERT.room\_id}}/notification?auth\_token=`\ {{ALERT.auth_token}}
 
 For the payload section, you can add a number of different variables.
-For more information see the HipChat documentation
-`here <https://www.hipchat.com/docs/apiv2/method/send_room_notification>`__.
+For more information see the HipChat documentation.
 In our example we are sending a simple colored message that contains
 alert information found in the “entity_display_name” field.
 

sp-oncall/spoc-integrations/new-twilio.rst

@@ -27,7 +27,7 @@ Requirements
 
 - A Twilio account
 - Splunk On-Call Versions: Getting Started, Growth, or Enterprise
-- At this time, trial Twilio accounts require all phone numbers the integration might end up calling. Follow the phone number verification process for all Splunk On-Call VictorOps users' phone numbers. See :new-page:`https://support.twilio.com/hc/en-us/articles/223180048-Adding-a-Verified-Phone-Number-or-Caller-ID-with-Twilio`. To see how this integration works before verifying numbers or purchasing a Twilio phone number, contact Splunk On-Call Support.
+- At this time, trial Twilio accounts require all phone numbers the integration might end up calling. Follow the phone number verification process for all Splunk On-Call VictorOps users' phone numbers. Search "How to Add and Remove a Verified Phone Number or Caller ID with Twilio" in Twilio documentation. To see how this integration works before verifying numbers or purchasing a Twilio phone number, contact Splunk On-Call Support.
 
 Twilio integration overview
 ===============================
@@ -349,7 +349,7 @@ The caller hears "Trying next on-call representative, Trying next on-call repres
 This might be because a trial Twilio account is being used instead of a paid Twilio account. You have to verify phone numbers in Twilio before they can be
 called. Additionally, even with a paid Twilio account, phone numbers in certain countries (such as Slovakia) need to be verified in Twilio numbers before calling them.
 
-To verify the numbers you're calling, follow the documented steps in :new-page:`Add a Verified Caller ID via the Console Site<https://support.twilio.com/hc/en-us/articles/223180048-Adding-a-verified-outbound-caller-ID-with-Twilio>`.
+To verify the numbers you're calling, search for "Add a Verified Caller ID via the Console Site" in Twillio documentaiton and follow the documented steps.
 
 Problem 2: There is a missing configuration value. Please contact your administrator to fix the problem.
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

sp-oncall/spoc-integrations/splunking-victorops-data.rst

@@ -456,7 +456,7 @@ all instance of <org_slug>.
 *Body*:
 
 { “sourcetype”: “\_json”, “event”: { “slug”: “<org_slug>”, “link”:
-“https://portal.victorops.com/client/<org_slug>/popoutIncident?incidentName=\ :math:`{{STATE.INCIDENT\_NAME}}",  "type": "incident",  "alertService": "`\ {{ALERT.service}}”,
+“\https://portal.victorops.com/client/<org_slug>/popoutIncident?incidentName=\ :math:`{{STATE.INCIDENT\_NAME}}",  "type": "incident",  "alertService": "`\ {{ALERT.service}}”,
 “hostName”:
 “:math:`{{ALERT.host\_name}}",  "service": "`\ {{ALERT.service}}”,
 “ENTITY_TYPE”: