Groovy 4 timeline and Collector question
https://www.logicmonitor.com/release-notes/collector-release-notes-timelinecollector
Right now, because we have a lot of custom things that use groovy, we are still working on making sure all of our custom modules are groovy4 compliant. All the out-of-box ones are upgraded.
But in order to do that, I paused our portal updates by ONLY having the checkbox set for REQUIRED. So our version is in the 35.xxx range because I paused it in November or December.
One item I'm having a bug with is jsonslurper giving a faststring service error, but i found out its been fixed since 36.200 by setting a parameter ( groovy.v4.classloader.enable ) to true. But the collector version we have doesnt even have that in the Agent.conf.
So in order to test properly, and make sure its working, I want to upgrade to a version PRIOR to EA 37.100. EA 37.100 will absolutely force us onto Groovy4. But if I briefly toggle the schedule to also include Optional General, it looks like I will get 37.002.
So I'm just hoping someone can sanity check me ..... I assume 37.002 is BEFORE the forced 37.200? And that 37.002 still supports both groovy2 and groovy4? So I may have a short window where I could upgrade our collectors.
I'm just confused because the URL I posted lists the date for EA 37.100 as coming BEFORE GD 37.002, and now of course the latest EA is 37.200.
If I take advantage of my short window, which shows that Optional General will gove me 37.002, will that version still support groovy2 AND groovy4? I expect to be done with my testing within 1-2 weeks but I'm stuck on this faststring bug.
Thanks!
Hello Lewis_Beard,
The FastStringService bug is resolved in Collector Version 36.200 or later. Collector version 37.002 will default to Groovy 2 but still support Groovy 4! Let me know if you have any other questions.
Skyla!