revise Troubleshooting links, references

Author: joepeeples

content/en/tests/troubleshooting/_index.md

@@ -13,7 +13,7 @@ This page provides information to help you troubleshot issues with Test Optimiza
 ## Your tests are instrumented, but Datadog isn't showing any data
 
 1. Go to the [**Tests**][3] page for the language you're instrumenting and check that the testing framework you are using is supported in the **Compatibility** section.
-2. Check if you see any test results in the [**Test Runs**][4] section. If you do see results there, but not in the [**Tests**][5] section, Git information is missing. See [Data appears in Test Runs but not Tests](#data-appears-in-test-runs-but-not-tests) to troubleshoot it.
+2. Check if you see any test results in the [**Test Runs**][4] section. If you do see results there, but not in [**Test Health**][5] when viewing the repositories list or an individual repository, Git information is missing. See [Data appears in Test Runs but not Test Health](#data-appears-in-test-runs-but-not-test-health) to troubleshoot it.
 3. If you are reporting the data through the Datadog Agent, make sure there is [network connectivity][15] from your test-running host to the Agent's host and port. Run your tests with the appropriate Agent hostname set in the `DD_AGENT_HOST` and the appropriate port in `DD_TRACE_AGENT_PORT` environment variables. You can activate [debug mode][6] in the tracer to verify connectivity to the Agent.
 4. If you are reporting the data directly to Datadog ("Agentless mode"), make sure there is [network connectivity][16] from the test-running hosts to Datadog's hosts. You can activate [debug mode][6] in the tracer to verify connectivity to Datadog.
 5. If you still don't see any results, [contact Support][2] for troubleshooting help.
@@ -25,9 +25,9 @@ The following aspects make a JUnit test report incorrect:
 * A timestamp of the reported tests that is older than **71 hours** before the moment the report is uploaded.
 * A testsuite without a name.
 
-## Data appears in test runs but not tests
+## Data appears in Test Runs but not Test Health
 
-If you can see test results data in the **Test Runs** tab, but not the **Tests** tab, Git metadata (repository, commit, or branch) is probably missing. To confirm this is the case, open a test execution in the [**Test Runs**][4] section, and check that there is no `git.repository_url`, `git.commit.sha`, or `git.branch`. If these tags are not populated, nothing shows in the [**Tests**][5] section.
+If you can see test results data in the **Test Runs** tab, but not in **Test Health** when viewing the repositories list or an individual repository, Git metadata (repository, commit, or branch) is probably missing. To confirm this is the case, open a test execution in the [**Test Runs**][4] section, and check that there is no `git.repository_url`, `git.commit.sha`, or `git.branch`. If these tags are not populated, nothing shows in repository sections of the [**Test Health**][5] page.
 
 1. Tracers first use the environment variables, if any, set by the CI provider to collect Git information. See [Running tests inside a container][7] for a list of environment variables that the tracer attempts to read for each supported CI provider. At a minimum, this populates the repository, commit hash, and branch information.
 2. Next, tracers fetch Git metadata using the local `.git` folder, if present, by executing `git` commands. This populates all Git metadata fields, including commit message, author, and committer information. Ensure the `.git` folder is present and the `git` binary is installed and in `$PATH`. This information is used to populate attributes not detected in the previous step.
@@ -182,8 +182,8 @@ When retrying a flaky test multiple times within a short span of time (less than
 [1]: https://www.jenkins.io/doc/book/system-administration/viewing-logs/
 [2]: /help/
 [3]: /continuous_integration/tests/
-[4]: https://app.datadoghq.com/ci/test-runs
-[5]: https://app.datadoghq.com/ci/test-repositories
+[4]: https://app.datadoghq.com/ci/test/runs
+[5]: https://app.datadoghq.com/ci/test/health
 [6]: /tracing/troubleshooting/tracer_debug_logs
 [7]: /continuous_integration/tests/containers/
 [8]: https://github.com/travisjeffery/timecop