04 Jun 2026 08:00 AM
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:02:29.963Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:02:30.762Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:03:29.963Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:03:30.732Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:04:29.962Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:04:30.766Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:05:29.960Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:05:30.826Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:06:29.965Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:06:30.731Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:07:29.965Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:07:30.684Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:08:29.964Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:08:30.709Z |
| /opt/dynatrace-managed/launcher/nginx.sh | nginx.sh | bash /opt/dtrun/run service dynatrace-nginx status | dynatrace | bash | 2026-06-03T01:09:29.963Z |
| /opt/dynatrace-managed/nginx/services/nginx.sh | nginx.sh | bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to | dynatrace | bash | 2026-06-03T01:09:30.680Z |
09 Jun 2026 11:45 AM
This is normal and expected behaviour — not a security concern.
What you're seeing are two scheduled health-check commands that run every 60 seconds as part of Dynatrace Managed's internal service management
bash /opt/dtrun/run service dynatrace-nginx status — checks whether the dynatrace-nginx service is running
bash /opt/dynatrace-managed/firewall/services/firewall.sh get-redirect-to — current firewall redirect configuration for Nginx
This is how Dynatrace Managed ensures its embedded Nginx reverse proxy is healthy and routing traffic correctly. If the status check detects Nginx is down, it can trigger an automatic restart.
Thanks,
Sujit
Featured Posts