fixing links

Signed-off-by: angelinalg <[email protected]>

doc/source/_toc.yml

@@ -394,15 +394,16 @@ parts:
  - file: ray-observability/user-guides/index
  title: User Guides
  sections:
- - file: ray-observability/user-guides/troubleshoot-apps/index
- title: Troubleshooting Applications
+ - file: ray-observability/user-guides/debug-apps/index
+ title: Debugging Applications
  sections:
- - file: ray-observability/user-guides/troubleshoot-apps/general-troubleshoot
- - file: ray-observability/user-guides/troubleshoot-apps/troubleshoot-failures
- - file: ray-observability/user-guides/troubleshoot-apps/troubleshoot-hangs
- - file: ray-observability/user-guides/troubleshoot-apps/optimize-performance
- - file: ray-observability/user-guides/troubleshoot-apps/ray-debugging
- - file: ray-observability/user-guides/troubleshoot-apps/ray-core-profiling
+ - file: ray-observability/user-guides/debug-apps/general-troubleshoot
+ - file: ray-observability/user-guides/debug-apps/debug-memory
+ - file: ray-observability/user-guides/debug-apps/debug-hangs
+ - file: ray-observability/user-guides/debug-apps/debug-failures
+ - file: ray-observability/user-guides/debug-apps/optimize-performance
+ - file: ray-observability/user-guides/debug-apps/ray-debugging
+ - file: ray-observability/user-guides/debug-apps/ray-core-profiling
  - file: ray-observability/user-guides/cli-sdk
  - file: ray-observability/user-guides/configure-logging
  - file: ray-observability/user-guides/add-app-metrics

doc/source/cluster/configure-manage-dashboard.rst

@@ -8,7 +8,7 @@ Setting up the dashboard may require some configuration depending on your use mo
 Port forwarding
 ---------------
 
-:ref:`The dashboard <ray-dashboard>` provides detailed information about the state of the cluster,
+:ref:`The dashboard <observability-getting-started>` provides detailed information about the state of the cluster,
 including the running jobs, actors, workers, nodes, etc.
 By default, the :ref:`cluster launcher <vm-cluster-quick-start>` and :ref:`KubeRay operator <kuberay-quickstart>` will launch the dashboard, but will
 not publicly expose the port.
@@ -248,7 +248,7 @@ Then go to to the location of the binary and run grafana using the built in conf
  ./bin/grafana-server --config /tmp/ray/session_latest/metrics/grafana/grafana.ini web
 
 Now, you can access grafana using the default grafana url, `http:https://localhost:3000`.
-You can then see the default dashboard by going to dashboards -> manage -> Ray -> Default Dashboard. The same :ref:`metric graphs <system-metrics>` are also accessible via :ref:`Ray Dashboard <ray-dashboard>`.
+You can then see the default dashboard by going to dashboards -> manage -> Ray -> Default Dashboard. The same :ref:`metric graphs <system-metrics>` are also accessible via :ref:`Ray Dashboard <observability-getting-started>`.
 
 .. tip::
 
@@ -288,7 +288,7 @@ For example, if Prometheus is hosted at port 9000 on a node with ip 55.66.77.88,
 Alternate Grafana host location
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 You can choose to run Grafana on a non-default port or on a different machine. If you choose to do this, the
-:ref:`Dashboard <ray-dashboard>` needs to be configured with a public address to that service so the web page
+:ref:`Dashboard <observability-getting-started>` needs to be configured with a public address to that service so the web page
 can load the graphs. This can be done with the `RAY_GRAFANA_HOST` env var when launching ray. The env var takes
 in the address to access Grafana. More info can be found :ref:`here <multi-node-metrics-grafana>`. Instructions
 to use an existing Grafana instance can be found :ref:`here <multi-node-metrics-grafana-existing>`.

doc/source/cluster/running-applications/monitoring-and-observability.rst

@@ -3,7 +3,7 @@ Scraping and Persisting Metrics
 
 Ray ships with the following observability features:
 
-1. :ref:`The dashboard <ray-dashboard>`, for viewing cluster state.
+1. :ref:`The dashboard <observability-getting-started>`, for viewing cluster state.
 2. CLI tools such as the :ref:`Ray state APIs <state-api-overview-ref>` and :ref:`ray status <monitor-cluster>`, for checking application and cluster status.
 3. :ref:`Prometheus metrics <multi-node-metrics>` for internal and custom user-defined metrics.
 
@@ -16,7 +16,7 @@ The rest of this page will focus on how to access these services when running a
 Monitoring the cluster via the dashboard
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-:ref:`The dashboard <ray-dashboard>` provides detailed information about the state of the cluster,
+:ref:`The dashboard <observability-getting-started>` provides detailed information about the state of the cluster,
 including the running jobs, actors, workers, nodes, etc.
 By default, the :ref:`cluster launcher <vm-cluster-quick-start>` and :ref:`KubeRay operator <kuberay-quickstart>` will launch the dashboard, but will
 not publicly expose the port.
@@ -96,14 +96,14 @@ below.
 Prometheus
 ^^^^^^^^^^
 Ray supports Prometheus for emitting and recording time-series metrics.
-See :ref:`metrics <ray-metrics>` for more details of the metrics emitted.
+See :ref:`metrics <dash-metrics-view>` for more details of the metrics emitted.
 To use Prometheus in a Ray cluster, decide where to host it, then configure
 it so that it can scrape the metrics from Ray.
 
 Scraping metrics
 ################
 
-Ray runs a metrics agent per node to export :ref:`metrics <ray-metrics>` about Ray core as well as
+Ray runs a metrics agent per node to export :ref:`metrics <dash-metrics-view>` about Ray core as well as
 custom user-defined metrics. Each metrics agent collects metrics from the local
 node and exposes these in a Prometheus format. You can then scrape each
 endpoint to access Ray's metrics.

doc/source/data/performance-tips.rst

@@ -7,7 +7,7 @@ Monitoring your application
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 View the Ray dashboard to monitor your application and troubleshoot issues. To learn
-more about the Ray dashboard, read :ref:`Ray Dashboard <ray-dashboard>`.
+more about the Ray dashboard, read :ref:`Ray Dashboard <observability-getting-started>`.
 
 Debugging Statistics
 ~~~~~~~~~~~~~~~~~~~~

doc/source/ray-air/getting-started.rst

@@ -216,4 +216,4 @@ Next Steps
 - :ref:`air-examples-ref`
 - :ref:`API reference <air-api-ref>`
 - :ref:`Technical whitepaper <whitepaper>`
-- To check how your application is doing, you can use the :ref:`Ray dashboard<ray-dashboard>`. 
+- To check how your application is doing, you can use the :ref:`Ray dashboard<robservability-getting-started>`. 

doc/source/ray-core/scheduling/ray-oom-prevention.rst

@@ -1,7 +1,7 @@
 Out-Of-Memory Prevention
 ========================
 
-If application tasks or actors consume a large amount of heap space, it can cause the node to run out of memory (OOM). When that happens, the operating system will start killing worker or raylet processes, disrupting the application. OOM may also stall metrics and if this happens on the head node, it may stall the :ref:`dashboard <ray-dashboard>` or other control processes and cause the cluster to become unusable.
+If application tasks or actors consume a large amount of heap space, it can cause the node to run out of memory (OOM). When that happens, the operating system will start killing worker or raylet processes, disrupting the application. OOM may also stall metrics and if this happens on the head node, it may stall the :ref:`dashboard <observability-getting-started>` or other control processes and cause the cluster to become unusable.
 
 In this section we will go over:
 

doc/source/ray-core/walkthrough.rst

@@ -60,7 +60,7 @@ As seen above, Ray stores task and actor call results in its :ref:`distributed o
 Next Steps
 ----------
 
-.. tip:: To check how your application is doing, you can use the :ref:`Ray dashboard <ray-dashboard>`. 
+.. tip:: To check how your application is doing, you can use the :ref:`Ray dashboard <observability-getting-started>`. 
 
 Ray's key primitives are simple, but can be composed together to express almost any kind of distributed computation.
 Learn more about Ray's :ref:`key concepts <core-key-concepts>` with the following user guides: