<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Capturing Outgoing Calls in Azure Functions with Dynatrace in Troubleshooting</title>
    <link>https://community.dynatrace.com/t5/Troubleshooting/Capturing-Outgoing-Calls-in-Azure-Functions-with-Dynatrace/ta-p/268247</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;&lt;H1&gt;Problem&lt;/H1&gt;&lt;P&gt;When integrating Dynatrace with Azure Functions, you might notice that only the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Invoke&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;call appears in the distributed trace. If you're wondering why there are no further outgoing calls displayed under&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Invoke, this guide is for you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H1&gt;Explanation&lt;/H1&gt;&lt;P&gt;This behavior is expected. The Dynatrace packages provide instrumentation only for incoming Azure Functions calls. To capture outgoing requests, whether to a database, a service, or another entity, you need to use the appropriate OpenTelemetry instrumentations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H1&gt;Resolution&lt;/H1&gt;&lt;P&gt;Here are the steps to implement OpenTelemetry instrumentation for different programming languages:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;For .NET : &lt;A class="" title="Monitor Azure Functions with OpenTelemetry for .NET and Dynatrace." href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions/func-dynamic-plans/opentelemetry-on-azure-functions-dotnet" target="_blank" rel="noopener"&gt;Trace Azure Functions written in .NET&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;For Node.js :&amp;nbsp;&lt;A class="" title="Monitor Azure Functions with OpenTelemetry for Node.js and Dynatrace." href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions/func-dynamic-plans/opentelemetry-on-azure-functions-nodejs" target="_blank" rel="noopener"&gt;Trace Azure Functions written in Node.js&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;For Python :&amp;nbsp;&lt;A class="" title="Monitor Azure Functions with OpenTelemetry for Python and Dynatrace." href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions/func-dynamic-plans/opentelemetry-on-azure-functions-python" target="_blank" rel="noopener"&gt;Trace Azure Functions written in Python&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P data-unlink="true"&gt;Since there are various options for hosting your functions, if a specific scenario is not covered, you can refer to the comprehensive guide on &lt;A href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions#distributed-tracing" target="_blank"&gt;Distributed Tracing for Azure Functions&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H1&gt;&lt;SPAN&gt;What's next&lt;/SPAN&gt;&lt;/H1&gt;&lt;P&gt;&lt;SPAN&gt;If your OpenTelemetry instrumentation is not working as expected, please review the limitations specific to each technology. If the issue persists, you can engage Dynatrace support for further assistance.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Tue, 11 Feb 2025 08:53:03 GMT</pubDate>
    <dc:creator>bhushangholap</dc:creator>
    <dc:date>2025-02-11T08:53:03Z</dc:date>
    <item>
      <title>Capturing Outgoing Calls in Azure Functions with Dynatrace</title>
      <link>https://community.dynatrace.com/t5/Troubleshooting/Capturing-Outgoing-Calls-in-Azure-Functions-with-Dynatrace/ta-p/268247</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;&lt;H1&gt;Problem&lt;/H1&gt;&lt;P&gt;When integrating Dynatrace with Azure Functions, you might notice that only the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Invoke&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;call appears in the distributed trace. If you're wondering why there are no further outgoing calls displayed under&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Invoke, this guide is for you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H1&gt;Explanation&lt;/H1&gt;&lt;P&gt;This behavior is expected. The Dynatrace packages provide instrumentation only for incoming Azure Functions calls. To capture outgoing requests, whether to a database, a service, or another entity, you need to use the appropriate OpenTelemetry instrumentations.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H1&gt;Resolution&lt;/H1&gt;&lt;P&gt;Here are the steps to implement OpenTelemetry instrumentation for different programming languages:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN&gt;For .NET : &lt;A class="" title="Monitor Azure Functions with OpenTelemetry for .NET and Dynatrace." href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions/func-dynamic-plans/opentelemetry-on-azure-functions-dotnet" target="_blank" rel="noopener"&gt;Trace Azure Functions written in .NET&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;For Node.js :&amp;nbsp;&lt;A class="" title="Monitor Azure Functions with OpenTelemetry for Node.js and Dynatrace." href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions/func-dynamic-plans/opentelemetry-on-azure-functions-nodejs" target="_blank" rel="noopener"&gt;Trace Azure Functions written in Node.js&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;For Python :&amp;nbsp;&lt;A class="" title="Monitor Azure Functions with OpenTelemetry for Python and Dynatrace." href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions/func-dynamic-plans/opentelemetry-on-azure-functions-python" target="_blank" rel="noopener"&gt;Trace Azure Functions written in Python&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;DIV class=""&gt;&lt;P data-unlink="true"&gt;Since there are various options for hosting your functions, if a specific scenario is not covered, you can refer to the comprehensive guide on &lt;A href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-functions#distributed-tracing" target="_blank"&gt;Distributed Tracing for Azure Functions&lt;/A&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H1&gt;&lt;SPAN&gt;What's next&lt;/SPAN&gt;&lt;/H1&gt;&lt;P&gt;&lt;SPAN&gt;If your OpenTelemetry instrumentation is not working as expected, please review the limitations specific to each technology. If the issue persists, you can engage Dynatrace support for further assistance.&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 11 Feb 2025 08:53:03 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Troubleshooting/Capturing-Outgoing-Calls-in-Azure-Functions-with-Dynatrace/ta-p/268247</guid>
      <dc:creator>bhushangholap</dc:creator>
      <dc:date>2025-02-11T08:53:03Z</dc:date>
    </item>
  </channel>
</rss>

