[PROF-13394] Improve setup source code integration documentation

content/en/profiler/enabling/ddprof.md

@@ -107,7 +107,7 @@ exec ./ddprof --environment prod --service my-web-app --service_version 1.0.3 my
 {{< /tabs >}}
 
 
-5. A few minutes after starting your application, your profiles appear on the [Datadog APM > Profiler page][3].
+5. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][3]. If they do not, refer to the [Troubleshooting][8] guide.
 
 ### Library
 
@@ -224,3 +224,4 @@ The [Getting Started with Profiler][6] guide takes a sample service with a perfo
 [5]: https://github.com/DataDog/ddprof/blob/main/docs/Commands.md
 [6]: /getting_started/profiler/
 [7]: /profiler/enabling/supported_versions/
+[8]: /profiler/profiler_troubleshooting/ddprof/

content/en/profiler/enabling/dotnet.md

@@ -229,9 +229,13 @@ To install the .NET Profiler per-webapp:
 
 4. For standalone applications, manually restart the application as you normally would.
 
-5. A minute or two after starting your application, your profiles appear on the [Datadog APM > Profiler page][1].
+5. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+6. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][1]. If they do not, refer to the [Troubleshooting][3] guide.
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
+[3]: /profiler/profiler_troubleshooting/dotnet/
 {{% /tab %}}
 
 {{% tab "Internet Information Services (IIS)" %}}
@@ -283,9 +287,13 @@ To install the .NET Profiler per-webapp:
      <strong>Note:</strong> Use <code>stop</code> and <code>start</code> commands. A reset or restart does not always work.
    </div>
 
-5. A minute or two after starting your application, your profiles appear on the [Datadog APM > Profiler page][1].
+5. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+6. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][1]. If they do not, refer to the [Troubleshooting][3] guide.
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
+[3]: /profiler/profiler_troubleshooting/dotnet/
 {{% /tab %}}
 
 {{% tab "Windows services" %}}
@@ -351,9 +359,13 @@ To install the .NET Profiler per-webapp:
    Set-ItemProperty HKLM:SYSTEM\CurrentControlSet\Services\MyService -Name Environment -Value $v
    ```
 
-4. A minute or two after you start your application, your profiles appear on the [Datadog APM > Profiler page][1].
+4. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+5. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][1]. If they do not, refer to the [Troubleshooting][3] guide.
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
+[3]: /profiler/profiler_troubleshooting/dotnet/
 {{% /tab %}}
 
 {{% tab "Windows Standalone applications" %}}
@@ -390,9 +402,13 @@ To install the .NET Profiler per-webapp:
    REM start the application here
    ```
 
-4. A minute or two after you start your application, your profiles appear on the [Datadog APM > Profiler page][1].
+4. Optional: Set up [Source Code Integration][2] to connect your profiling data with your Git repositories.
+
+5. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][1]. If they do not, refer to the [Troubleshooting][3] guide.
 
 [1]: https://app.datadoghq.com/profiling
+[2]: /integrations/guide/source-code-integration/?tab=net
+[3]: /profiler/profiler_troubleshooting/dotnet/
 {{% /tab %}}
 
 {{% tab "NuGet" %}}

content/en/profiler/enabling/go.md

@@ -81,7 +81,7 @@ To begin profiling applications:
 
 5. Optional: Set up [Source Code Integration][9] to connect your profiling data with your Git repositories.
 
-6. After a minute or two, visualize your profiles in the [Datadog APM > Profiler page][10].
+6. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][10]. If they do not, refer to the [Troubleshooting][25] guide.
 
 **Note**: By default, only the CPU and Heap profiles are enabled. Use [profiler.WithProfileTypes][22] and [profile types][23]. For legacy v1 documentation, view [profiler.WithProfileTypes][11] to enable additional [profile types][12].
 
@@ -164,4 +164,5 @@ The [Getting Started with Profiler][17] guide takes a sample service with a perf
 [21]: https://pkg.go.dev/github.com/DataDog/dd-trace-go/v2/profiler#pkg-constants
 [22]:https://pkg.go.dev/github.com/DataDog/dd-trace-go/v2/profiler#WithProfileTypes
 [23]:https://pkg.go.dev/github.com/DataDog/dd-trace-go/v2/profiler#ProfileType
-[24]: https://go.dev/doc/devel/release
+[24]: https://go.dev/doc/devel/release
+[25]: /profiler/profiler_troubleshooting/go/

content/en/profiler/enabling/java.md

@@ -155,7 +155,7 @@ When the service binary is built, you can use environment variables to enable an
 
 4. Optional: Set up [Source Code Integration][7] to connect your profiling data with your Git repositories.
 
-5. After a minute or two, you can visualize your profiles on the [Datadog APM > Profiling page][8].
+5. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiling page][8]. If they do not, refer to the [Troubleshooting][16] guide.
 
 ### Enabling CPU profiler engine options
 
@@ -363,3 +363,4 @@ The [Getting Started with Profiler][11] guide takes a sample service with a perf
 [13]: /profiler/enabling/supported_versions/
 [14]: /tracing/trace_collection/compatibility/java/?tab=graalvm#setup
 [15]: https://docs.datadoghq.com/profiler/enabling/java/?tab=datadogprofiler#
+[16]: /profiler/profiler_troubleshooting/java/

content/en/profiler/enabling/nodejs.md

@@ -76,9 +76,9 @@ const tracer = require('dd-trace/init')
 {{% /tab %}}
 {{< /tabs >}}
 
-4. Optional: Set up [Source Code Integration][4].
+4. Optional: Set up [Source Code Integration][4] to connect your profiling data with your Git repositories.
 
-5. A minute or two after starting your Node.js application, your profiles will appear on the [APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][9] guide.
+5. A couple of minutes after you start your application, your profiles appear on the [APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][9] guide.
 
 ## Not sure what to do next?
 

content/en/profiler/enabling/php.md

@@ -109,7 +109,9 @@ To begin profiling applications:
         with datadog-profiling v1.13.0, Copyright Datadog, by Datadog
     ```
 
-5. A minute or two after receiving a request, profiles appear on the [APM > Profiler page][5].
+6. Optional: Set up [Source Code Integration][16] to connect your profiling data with your Git repositories.
+
+7. A couple of minutes after receiving a request, your profiles appear on the [APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][17] guide.
 
 ## Not sure what to do next?
 
@@ -130,3 +132,4 @@ The [Getting Started with Profiler][6] guide takes a sample service with a perfo
 [14]: /profiler/enabling/supported_versions/
 [15]: /profiler/profile_visualizations/#timeline-view
 [16]: /integrations/guide/source-code-integration/?tab=php
+[17]: /profiler/profiler_troubleshooting/php/

content/en/profiler/enabling/python.md

@@ -63,7 +63,7 @@ See [Configuration](#configuration) for more advanced usage.
 
 Optionally, set up [Source Code Integration][4] to connect your profiling data with your Git repositories.
 
-After a couple of minutes, visualize your profiles on the [Datadog APM > Profiler page][5].
+A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][18] guide.
 
 If you want to manually control the lifecycle of the profiler, use the `ddtrace.profiling.Profiler` object:
 
@@ -146,3 +146,4 @@ The [Getting Started with Profiler][7] guide takes a sample service with a perfo
 [15]: /profiler/profile_visualizations/#timeline-view
 [16]: /serverless/aws_lambda/profiling/
 [17]: /tracing/trace_collection/compatibility/python
+[18]: /profiler/profiler_troubleshooting/python/

content/en/profiler/enabling/ruby.md

@@ -107,7 +107,7 @@ end
 
 6. Optional: Set up [Source Code Integration][4] to connect your profiling data with your Git repositories.
 
-7. A minute or two after starting your Ruby application, your profiles will show up on the [Datadog APM > Profiler page][5].
+7. A couple of minutes after you start your application, your profiles appear on the [Datadog APM > Profiler page][5]. If they do not, refer to the [Troubleshooting][26] guide.
 
 ## Configuration
 
@@ -174,3 +174,4 @@ The [Getting Started with Profiler][6] guide takes a sample service with a perfo
 [23]: https://packages.fedoraproject.org/pkgs/pkgconf/pkgconf-pkg-config
 [24]: https://rpmfind.net/linux/rpm2html/search.php?query=pkgconf-pkg-config
 [25]: /tracing/trace_collection/automatic_instrumentation/single-step-apm/
+[26]: /profiler/profiler_troubleshooting/ruby/