Skip to content

Commit fc1b9ed

Browse files
committed
all links fixed
1 parent d402502 commit fc1b9ed

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

apm/db-query-perf/turn-on-db-perf.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,9 +34,9 @@ Follow these steps to turn on Database Query Performance and begin indexing data
3434

3535
.. note:: Before proceeding, ensure that you have configured the instrumentation for your specific programming language:
3636
* Java, see :ref:`instrument-java-applications`.
37-
* .NET, see :ref:`instrument-dotnet-application.html#database-query-performance-settings`.
38-
* Python, see :ref:`instrument-python-application`.
39-
* Node.js, see :ref:`instrument-nodejs-application`.
37+
* .NET, see :ref:`install-dotnet-otel-instrumentation`.
38+
* Python, see :ref:`instrument-python-applications`.
39+
* Node.js, see :ref:`instrument-nodejs-applications-3x`.
4040

4141
2. In the Database Query Performance section, check that the :guilabel:`Status` is Active. If it is, skip to the next step. If it's not, select :guilabel:`Resume Indexing` to initiate cardinality analysis, and then wait for the cardinality analysis to run in the Pending MetricSet section at the top of the table.
4242

0 commit comments

Comments
 (0)