topic Re: Dynatrace hourly license - Auto stop agent monitoring during non-business hours in Dynatrace Managed Q&A

Dynatrace hourly license: auto-stop agent monitoring during non-business hours

RazTN7 — Tue, 20 Jun 2023 12:41:23 GMT

Hello Team,

Customer is using DT hourly license. Where we wanted to stop Dynatrace agent monitoring during non-business hour as the nature of the application don't have customer landing during non-business hours (between 7pm to 8am)

Customer is expecting this feature to be included within Dynatrace as it is providing the flexi with hourly license consumption.

Just wanted to know what the other options are to handle this request.

Cheers!

Re: Dynatrace hourly license - Auto stop agent monitoring during non-business hours

Julius_Loman — Tue, 14 Mar 2023 07:30:35 GMT

The easiest way is to utilize the Settings API with the schema builtin:host.monitoring to enable and disable the hosts as required. You need to disable them individually (one call per host). However you will need to keep in mind if some processes have been restarted on the hosts while OneAgent was disabled, then they need to be restarted again after monitoring was enabled back to get the code modules injected.

We've developed an automation tool to handle such situations for our customers (managing agents per hostgroup or tag, getting license utilization and getting the list of processes to be restarted).

Re: Dynatrace hourly license - Auto stop agent monitoring during non-business hours

Mizső — Tue, 14 Mar 2023 07:54:31 GMT

Hi @Julius_Loman ,

Nice tool...

Best regads,

Mizső

Re: Dynatrace hourly license - Auto stop agent monitoring during non-business hours

Julius_Loman — Tue, 14 Mar 2023 09:53:12 GMT

@Mizső thanks - the power comes when combined with automatic disabling of new OneAgent installations. Then you can safely roll out OneAgents across the environment and enable them afterwards where required.

It saves a huge amount of manual work in the UI.

Re: Dynatrace hourly license - Auto stop agent monitoring during non-business hours

RazTN7 — Wed, 15 Mar 2023 03:26:16 GMT

Thank you @Julius_Loman. Can this tool be available in Dynatrace Hub/gitHub someday.

Re: Dynatrace hourly license - Auto stop agent monitoring during non-business hours

theharithsa — Thu, 21 Mar 2024 05:15:28 GMT

This is already there in our Official GitHub repository.
https://github.com/Dynatrace/auto-update-manager

This will help you in configuring settings 2.0 APIs.

Re: Dynatrace hourly license: auto-stop agent monitoring during non-business hours

cesarsaravia — Thu, 21 Mar 2024 14:25:50 GMT

Hi @RazTN7
Another option or workaround is creating a workflow with the desired rules, and you can execute on-demand or on a fixed timeframe.
Example:

And remember what @Julius_Loman mentions, if a process has been restarted on those non-business hours, you should restart the processes after the OneAgent it's initiated. In that case you should add a task on your workflow and connect with an automation tool like ansible or terraform to make the restart of the processes.

Regards,

Re: Dynatrace hourly license: auto-stop agent monitoring during non-business hours

MarwanC — Tue, 15 Jul 2025 12:45:39 GMT

cesarsaravia, thank for you sharing the workflow, would you be kind to share some more info on the details of each box in your workflow, some screenshots is much appreciated.

Re: Dynatrace hourly license: auto-stop agent monitoring during non-business hours

Hillman — Fri, 07 Nov 2025 09:33:33 GMT

@cesarsaravia That sounds a good idea! Do you have the sample DQL that get the list of hosts and the scripts / commands to disable OneAgent? Is it feasible on Kubernetes one as well?

Re: Dynatrace hourly license: auto-stop agent monitoring during non-business hours

Julius_Loman — Fri, 07 Nov 2025 10:07:40 GMT

I use something like this in my workflows - when disabling by host groups (sort is not necessary of course)

fetch dt.entity.host, from: -7d | fieldsAdd hostGroupName | filter in(hostGroupName, array("test.host_group1","preprod.host_group1")) | sort entity.name

It works also for kubernetes, but it might depend on your deployment type (applicationOnly vs cloudNativeFullStack)