<?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 Multiple DT_CLUSTER_ID variable for several apache processes in one machine in Open Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Open-Q-A/Multiple-DT-CLUSTER-ID-variable-for-several-apache-processes-in/m-p/112649#M8423</link>
    <description>&lt;P&gt;Hi all, &lt;/P&gt;&lt;P&gt;I've multiple Apache instances in a single machine and, in order to create a process group for every instance we want to assign the DT_CLUSTER_ID, DT_NODE_ID and DT_CUSRTOM_PROP environment variables.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;My doubt here is, if we put the instruction &lt;EM&gt;&lt;STRONG&gt;export &lt;EM&gt;DT_CLUSTER_ID&lt;/EM&gt;=name&lt;/STRONG&gt; &lt;/EM&gt;in every script that runs every apache, with a different name for each instance, the value of DT_CLUSTER_ID is overwritten? Or every apache has its own DT_CLUSTER_ID environment variable?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards, Josep Maria&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 13 May 2020 10:44:18 GMT</pubDate>
    <dc:creator>jcamps</dc:creator>
    <dc:date>2020-05-13T10:44:18Z</dc:date>
    <item>
      <title>Multiple DT_CLUSTER_ID variable for several apache processes in one machine</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Multiple-DT-CLUSTER-ID-variable-for-several-apache-processes-in/m-p/112649#M8423</link>
      <description>&lt;P&gt;Hi all, &lt;/P&gt;&lt;P&gt;I've multiple Apache instances in a single machine and, in order to create a process group for every instance we want to assign the DT_CLUSTER_ID, DT_NODE_ID and DT_CUSRTOM_PROP environment variables.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;My doubt here is, if we put the instruction &lt;EM&gt;&lt;STRONG&gt;export &lt;EM&gt;DT_CLUSTER_ID&lt;/EM&gt;=name&lt;/STRONG&gt; &lt;/EM&gt;in every script that runs every apache, with a different name for each instance, the value of DT_CLUSTER_ID is overwritten? Or every apache has its own DT_CLUSTER_ID environment variable?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards, Josep Maria&lt;EM&gt;&lt;BR /&gt;&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2020 10:44:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Multiple-DT-CLUSTER-ID-variable-for-several-apache-processes-in/m-p/112649#M8423</guid>
      <dc:creator>jcamps</dc:creator>
      <dc:date>2020-05-13T10:44:18Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple DT_CLUSTER_ID variable for several apache processes in one machine</title>
      <link>https://community.dynatrace.com/t5/Open-Q-A/Multiple-DT-CLUSTER-ID-variable-for-several-apache-processes-in/m-p/112650#M8424</link>
      <description>&lt;P&gt;I'm not sure if you are using standard apache startup scripts or not. If you are using standard ones, there is even a place for that and that file is called envvars. You will just have to put correct  DT_CLUSTER_ID for each instance. Something like this:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;PRE&gt;export DT_CLUSTER_ID="apache1"&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;In general - you must ensure the process will have the environment variable set. This applies if you are using custom startup scripts.&lt;BR /&gt;&lt;BR /&gt;Another way would be to use the process group detection rules or process group naming rules - depending on if the processes are "glued" together or you just want to rename them to a name you need.&lt;/P&gt;</description>
      <pubDate>Wed, 13 May 2020 12:10:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Open-Q-A/Multiple-DT-CLUSTER-ID-variable-for-several-apache-processes-in/m-p/112650#M8424</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2020-05-13T12:10:21Z</dc:date>
    </item>
  </channel>
</rss>

