topic Re: "Inactive" Services in Service App in Open Q&A

"Inactive" Services in Service App

ASE — Thu, 29 Aug 2024 13:42:23 GMT

We continue to see some of our existing legacy services show up as "Inactive" in the Services page.

When asking our ENG team, we are often told no changes have been made to that service.

In general, what are some of the reasons why a service (that we know is online and actively running) would show as Inactive in Dynatrace?

Thank you.

Re: "Inactive" Services in Service App

marina_pollehn — Mon, 02 Sep 2024 14:53:02 GMT

Are you monitoring the underlying processes/process groups? Were there any changes made to the process detection? Or in the versions of technologies? Possibly any end of support interfering after OneAgent updates? Automatic OneAgent updates might surprise you with stopped support for "old" technologies... End of support announcements - Dynatrace Docs OneAgent release notes - Dynatrace Docs

Re: "Inactive" Services in Service App

Peter_Youssef — Mon, 16 Sep 2024 20:30:06 GMT

Hi @ASE validate the below concerns:

Process technology version.
Service version.
Oneagent version. > try to update oneagent version.
apply process restart for further checks are these samples still inactive or the issue is resolved.

Re: "Inactive" Services in Service App

Maheedhar_T — Wed, 18 Sep 2024 10:28:43 GMT

Hi @ASE ,
Apart from the points that @marina_pollehn and @Peter_Youssef have mentioned there is one more possibility that when your process is restarted, the underlying services are also restarted and after restart OneAgent might sometimes consider them as a whole new process instead of resuming monitoring on the older ones. This is again a very rare condition so check if you already have another process with the same name as running.

Re: "Inactive" Services in Service App

ASE — Tue, 07 Jan 2025 15:55:47 GMT

Thank you all for your responses.

We determined what was causing this issue.

Here's a brief summary from one of our engineers:

"wanted to finally close the loop on this, we know what happened now.
we have a custom python package specific for OTEL -> DT, I added it to a legacy project that already had OTEL setup code in it. While I did not actually call or deliberately invoke said python package, it conflicted with the setup (essentially double setup, clashing env vars) b/c the python package used opentelementry plugin hooks that automatically load the library during otel initialization. removing the package fixed this."