05 Feb 2024 09:03 PM - last edited on 07 Feb 2024 10:13 AM by MaciejNeumann
When migrating "Generic DB Query Plugin" from 3.1.4 (old version) to latest version, are there any configuration differences that might apply?
Reason: Have a big number of configurations...
Solved! Go to Solution.
07 Feb 2024 11:22 AM
There are no breaking changes between 3.1.4 and now. That being said, there are a lot of fixes and improvements, so if your configurations relied on an unexpected behavior there could be changes to the data after the upgrade.
07 Feb 2024 07:43 PM
The configuration parameters have slight changes, they really don't seem to be a problem.
But, the metrics seemed to have shifted from metrics ingested by the Extensions framework to (maybe?) Metric ingestion protocol ? I say this because of the changes in plugin.json.
If this is the case, it would break dashboards that rely on the old metrics. Is this maybe the case?
07 Feb 2024 08:32 PM
It was always MINT, we changed the supporting metrics though in version 3.0 and again in 3.3 or so.
@david_lopes wrote the extension and can give the final verdict.
08 Feb 2024 01:09 AM
The metric that matter never changed, it was always custom.db.query even in 2.X versions.
What did change was the statistics metrics. They don't exist in plugin.json anymore and are sent via MINT. I doubt many customers use statistics metrics on dashboards though as they are more of a troubleshooting tool, but please check with your customers.