<?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>topic Azure Linux app services staging slots in Cloud platforms</title>
    <link>https://community.dynatrace.com/t5/Cloud-platforms/Azure-Linux-app-services-staging-slots/m-p/295217#M2294</link>
    <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;&lt;BR /&gt;We have a linux app service running a .net application. When it got discovered it already has been discovered as one service, running on multiple app services, in which some are from staging slot 1 and other from slot 2.&lt;BR /&gt;&lt;BR /&gt;Is there a way to easily make it visible and distinguish whether request come from which slot. I want to keep the service (and process group) as 1 single group, while being able to make a distinguish on trace level of which slot it was.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In Windows app services I noticed that we got a &amp;lt;service&amp;gt;/&amp;lt;process group&amp;gt;.&amp;lt;deploymenslotid&amp;gt;, this isn't the case in linux.&lt;BR /&gt;&lt;BR /&gt;According to the documentation, if i would use custom metadata (or tags) that would go on the proceses group. Not necessarily on the process itself (at least according to the phrasing).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-web-app-for-containers#validatevariable" target="_blank" rel="noopener"&gt;https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-web-app-for-containers#validatevariable&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;/P&gt;</description>
    <pubDate>Wed, 25 Feb 2026 07:18:27 GMT</pubDate>
    <dc:creator>RikvdBrugge</dc:creator>
    <dc:date>2026-02-25T07:18:27Z</dc:date>
    <item>
      <title>Azure Linux app services staging slots</title>
      <link>https://community.dynatrace.com/t5/Cloud-platforms/Azure-Linux-app-services-staging-slots/m-p/295217#M2294</link>
      <description>&lt;P&gt;Hi everyone,&lt;BR /&gt;&lt;BR /&gt;We have a linux app service running a .net application. When it got discovered it already has been discovered as one service, running on multiple app services, in which some are from staging slot 1 and other from slot 2.&lt;BR /&gt;&lt;BR /&gt;Is there a way to easily make it visible and distinguish whether request come from which slot. I want to keep the service (and process group) as 1 single group, while being able to make a distinguish on trace level of which slot it was.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;In Windows app services I noticed that we got a &amp;lt;service&amp;gt;/&amp;lt;process group&amp;gt;.&amp;lt;deploymenslotid&amp;gt;, this isn't the case in linux.&lt;BR /&gt;&lt;BR /&gt;According to the documentation, if i would use custom metadata (or tags) that would go on the proceses group. Not necessarily on the process itself (at least according to the phrasing).&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-web-app-for-containers#validatevariable" target="_blank" rel="noopener"&gt;https://docs.dynatrace.com/docs/ingest-from/microsoft-azure-services/azure-integrations/azure-appservice/integrate-oneagent-on-web-app-for-containers#validatevariable&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;/P&gt;</description>
      <pubDate>Wed, 25 Feb 2026 07:18:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Cloud-platforms/Azure-Linux-app-services-staging-slots/m-p/295217#M2294</guid>
      <dc:creator>RikvdBrugge</dc:creator>
      <dc:date>2026-02-25T07:18:27Z</dc:date>
    </item>
  </channel>
</rss>

