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.
20 Nov 2023 01:01 PM
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.
20 Nov 2023 01:09 PM
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
20 Nov 2023 01:15 PM
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.
20 Nov 2023 01:20 PM
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! 🙂
20 Nov 2023 01:15 PM
This is scheduled to be added to the SQL datasource somewhere in the first half of 2024 to bridge the most important gap with the Custom DB Query extension.
22 Apr 2024 01:56 PM
Hi Mike_L!
Are there any news on this? Thanks!
22 Apr 2024 02:06 PM
It has been postponed for now. It might be that this functionality is not present before the removal of extension framework 1.0.
22 Apr 2024 03:24 PM
I'm sad to hear this but I do appreciate the update here. I'm not quite ready to start moving everything over to the 2.0 extension I've developed but when ready I will work with the app team to adjust the scheduling.
23 Apr 2024 09:55 AM - edited 23 Apr 2024 01:44 PM
Is there any way to leave the admins some time between you adding the cron functionality to the 2.0 extensions in case that it is not ready in time before the framework 1.0 removal and the framework 1.0 extensions removal?
It will make our monitoring unavailable only dued to this.
23 Apr 2024 11:14 AM
I'm working on the priority of this. I'll point the product manager to your comment about unavailable monitoring.
28 Jun 2024 03:55 PM
@Mike_L just checking in on this being it has been 2 months. Is there any more definitive timeframe of when cron like scheduling will be available for this?
28 Jun 2024 05:06 PM
It's currently in active development for the SQL data source and we expect it to be there before the removal of EF1 🙂
28 Jun 2024 05:44 PM
When will EF1 be removed, @Mike_L?
We need to know exactly when our custom DB query extension 1.0 will stop working.
28 Jun 2024 05:51 PM
Python extensions built in EF1 will be removed in October. More precisely ActiveGate and OneAgent 1.301.
JMX will keep working until March.
28 Jun 2024 10:14 PM
Just to make sure I am clear here, we are using the sqlOracle datasource to query Oracle databases. This upcoming feature applies to this right? Not sure if there is a separate datasource for something like MSSQL but just wanted to be clear on what we are hoping for (this new feature to work for queries we are running against Oracle databases)
28 Jun 2024 11:28 PM
It is indeed planned to work with all the SQL data sources, including Oracle.
26 Jul 2024 11:36 AM
This will be added to all SQL data sources in AG 1.299. Example YAML:
26 Jul 2024 01:23 PM
Great news here Mike. Thank you to all involved with this effort!
14 Aug 2024 02:14 PM
EDIT: cron support for the SQL data sources have been delayed to AG 1.301.