20 Nov 2023
12:39 PM
- last edited on
21 Nov 2023
08:33 AM
by
MaciejNeumann
The EF 1.0 custom db queries extension allows for use of a cron like schedule for when the queries will be executed. I have only seen the ability to specific how often (every 5 minutes, 10 minutes, etc) to run the query for EF 2.0 extensions.
Does 2.0 have the ability to specify a cron like schedule? We use that pretty heavily today with the 1.0 extension. With the sunset of EF 1.0 in Oct next year I've started looking at replacing the one we use today with 2.0.
Solved! Go to Solution.
Please see this thread. Although documention does not (yet) reflect the availability. It's just not possible to have this configured as configurable variable of the extension configuration and must be "hardcoded" in the extension yaml.
What is referenced here is a standard interval such as every 5 minutes. I am aware of being able to change that to something else (10, 30, whatever) but that is not what I am referring to. As an example we have the 1.0 extension running a query on a cron schedule such as the below to run at a very specific time Monday - Friday. I don't see that being possible yet in the 2.0 framework.
0-5 12 * * MON-FRI
Yes, my fault. You can right now enable/disable extensions configuration using API. So, this can be accomplished for example by calling it from a workflow (if you are on SaaS and you have the new Dynatrace platform available) or triggering the API call remotely - for example from a cron scheduler.
Thanks for the information @Julius_Loman but I could see this still being a huge headache. If I recall correctly the query does not show up in a 'separate config object', or something you can individually manipulate. This means we would have to have a new extension for each query that has a unique schedule that cannot be put into the standard interval format.
While yes API calls are great, it just doesn't make much sense to not have this ability added to the new framework as it causes a lot more maintenance, unless I am missing something.
@Mike_L glad to see this is being brought in, thank you! 🙂