<?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 Re: No response from apache to nginx in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274112#M5553</link>
    <description>&lt;P&gt;my nginx version is 1.20.2 which is supposed to be working&lt;/P&gt;</description>
    <pubDate>Tue, 01 Apr 2025 16:02:14 GMT</pubDate>
    <dc:creator>tchatzi</dc:creator>
    <dc:date>2025-04-01T16:02:14Z</dc:date>
    <item>
      <title>No response from apache to nginx</title>
      <link>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274097#M5550</link>
      <description>&lt;P&gt;In kubernetes I have a pod with nginx and a pod with apache. Requests come from outside clients to nginx, nginx response all static files (js, css,jpg) and all api calls are being proxy passed to apache pod. Everything warks great untill I install dynatrace and redeploy my pods. Then all static files work great but the api calls that are being proxy passed to apache fail. No errors, just nginx dies. Ningx does not get any response from apache.&amp;nbsp;&lt;BR /&gt;I used the following to nginx&lt;/P&gt;
&lt;LI-CODE lang="markup"&gt;dynatrace.com/inject: 'false'
metadata-enrichment.dynatrace.com/inject: 'false'
oneagent.dynatrace.com/inject: 'false'&lt;/LI-CODE&gt;
&lt;P&gt;I redeployed and nginx does get the response from apache pod, but the json is truncated.&lt;BR /&gt;If i disable dynatrace for apache as well using the above lines everything work fine.&lt;BR /&gt;&lt;BR /&gt;Is there anyone that can share any thoughts, Thanks for your time and consideration.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 06:55:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274097#M5550</guid>
      <dc:creator>tchatzi</dc:creator>
      <dc:date>2025-04-02T06:55:59Z</dc:date>
    </item>
    <item>
      <title>Re: No response from apache to nginx</title>
      <link>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274105#M5551</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/88656"&gt;@tchatzi&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have checked the nginx support matrix?&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/nginx-binaries#nginx-versions" target="_blank"&gt;https://docs.dynatrace.com/docs/shortlink/nginx-binaries#nginx-versions&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;János&lt;/P&gt;</description>
      <pubDate>Tue, 01 Apr 2025 15:04:54 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274105#M5551</guid>
      <dc:creator>Mizső</dc:creator>
      <dc:date>2025-04-01T15:04:54Z</dc:date>
    </item>
    <item>
      <title>Re: No response from apache to nginx</title>
      <link>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274112#M5553</link>
      <description>&lt;P&gt;my nginx version is 1.20.2 which is supposed to be working&lt;/P&gt;</description>
      <pubDate>Tue, 01 Apr 2025 16:02:14 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274112#M5553</guid>
      <dc:creator>tchatzi</dc:creator>
      <dc:date>2025-04-01T16:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: No response from apache to nginx</title>
      <link>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274202#M5558</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/88656"&gt;@tchatzi&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;YES, this version is supported based on the matrix. Unfortunately I do not have any other idea.&lt;/P&gt;&lt;P&gt;Could you please raise a support ticket?&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;János&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 14:03:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274202#M5558</guid>
      <dc:creator>Mizső</dc:creator>
      <dc:date>2025-04-02T14:03:15Z</dc:date>
    </item>
    <item>
      <title>Re: No response from apache to nginx</title>
      <link>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274229#M5559</link>
      <description>&lt;P&gt;Hi!&amp;nbsp;&lt;SPAN&gt;Hope your hump day is going great!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;If you are interested in service level monitoring you can try to disable sensor on process group - if there is such process group - nginx. Easiest way to find it on smartscape - you can use search.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Romanenkov_Al3x_0-1743605534056.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/27362iE34D71336AEAF31E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Romanenkov_Al3x_0-1743605534056.png" alt="Romanenkov_Al3x_0-1743605534056.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;You can drill down to process group settings and try to disable this checkbox.&lt;/P&gt;&lt;P&gt;Also you can try to disable specific sensor in OneAgent features, try filter with 'webserver' sensor.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Romanenkov_Al3x_1-1743605626663.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/27363i64449C41A5640A87/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Romanenkov_Al3x_1-1743605626663.png" alt="Romanenkov_Al3x_1-1743605626663.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If this is public image - nice to share it / We can add more recomendations / reproduce at our env.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also you can try to add:&lt;/P&gt;&lt;P&gt;Settings &amp;gt; Processes and containers &amp;gt; Custom process monitoring rules&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Romanenkov_Al3x_2-1743605997506.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/27365i27B3BC2B8E7289D4/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Romanenkov_Al3x_2-1743605997506.png" alt="Romanenkov_Al3x_2-1743605997506.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;apiVersion: apps/v1
kind: Deployment
metadata:
  name: web-servers
spec:
  replicas: 1
  selector:
    matchLabels:
      app: web-servers
  template:
    metadata:
      labels:
        app: web-servers
    spec:
      containers:
      - name: apache
        image: httpd:latest
        ports:
        - containerPort: 80
      - name: nginx
        image: nginx:latest
        ports:
        - containerPort: 80
        env:
        - name: DOG
          value: "CORGI"&lt;/LI-CODE&gt;&lt;TABLE border="1" width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="100%"&gt;&lt;SPAN&gt;If nothing helps, it's best to create a support ticket as recommended by&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/47783"&gt;@Mizső&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aleksandr&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Apr 2025 15:07:58 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/No-response-from-apache-to-nginx/m-p/274229#M5559</guid>
      <dc:creator>Romanenkov_Al3x</dc:creator>
      <dc:date>2025-04-02T15:07:58Z</dc:date>
    </item>
  </channel>
</rss>

