Merge pull request #2703 from splunk/kopta_database_query_performance_changes

kopta_database_query_performance_changes

Author: pkopta-splunk

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

@@ -32,6 +32,12 @@ Follow these steps to turn on Database Query Performance and begin indexing data
          :width: 25%
          :alt: Screenshot of the APM Configuration menu on the APM landing page.
 
+    .. note:: Before proceeding, ensure that you have configured the instrumentation for your specific programming language:
+            * Java, see :ref:`instrument-java-applications`.
+            * .NET, see :ref:`configure-otel-dotnet`.
+            * Python, see :ref:`instrument-python-applications`. 
+            * Node.js, see :ref:`instrument-nodejs-applications-3x`.                   
+
 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. 
 
     .. image:: /_images/apm/db-query-perf/db-cardinality-success.png

gdi/get-data-in/application/otel-dotnet/instrumentation/instrument-dotnet-application.rst

@@ -359,6 +359,8 @@ SQL statements might contain sensitive information. To configure this behavior,
 * ``OTEL_DOTNET_AUTO_ENTITYFRAMEWORKCORE_SET_DBSTATEMENT_FOR_TEXT``
 * ``OTEL_DOTNET_AUTO_ORACLEMDA_SET_DBSTATEMENT_FOR_TEXT``
 
+For more details on enabling Database Query Performance, visit :ref:`turn-on-db-perf`.
+
 .. _docker-install-otel-dotnet:
 
 Instrument an application running within a Docker container