Is it possible to run inline Groovy with Invoke-LMCollectorDebugCommand?

[rdmarsh]

I’m trying to figure out how to pass Groovy code with Invoke-LMCollectorDebugCommand, and I’m not sure it’s possible.

There isn't much documentation from LogicMonitor, and everything I’ve tried so isn't working.

Here’s a minimal example that fails:

Invoke-LMCollectorDebugCommand -Id 241 -GroovyCommand "println 'hello world'" -IncludeResult

which relults in this error:

Error when executing the script -

exception:org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
Script1148.groovy: 8: Unexpected input: '{\n    hostProps = CollectorDb.getInstance().getHost("").getProperties();\n    instanceProps["wildvalue"] = "";\n    }\ncatch' @ line 8, column 1.
   catch(Exception e) {
   ^

1 error
[snip]

If I open the collector debug console, open the groovy popup window and run Groovy manually, it works fine:

$ !groovy
returns null
output:
hello world

The only clue I have that I can pass groovy to the the collector is the help output. The second usage suggests the collector should accept inline "scriptbody" if prefixed with \n, but I haven’t managed to get anything working on the console or the PowerShell wrapper.

$ help !groovy
Usage:
    !groovy [options] scriptFilePath
    !groovy [options] \nscriptbody
Options:
    timeout: timeout in seconds, default 180 seconds
    runner: where to run the script. Runner must be agent or sse, and agent is the default runner
    hostId: send which host(in the portal) properties to groovy runner.
    h: indicates which host(in the collector) the hostProps will bound to
Arguments:
    scriptFilePath: specify the script path in collector side for executing
    scriptbody: embedded script body from the !groovy popup window

Has anyone managed to send inline Groovy to a collector using Invoke-LMCollectorDebugCommand or via the collector debug window? Is inline Groovy supported, or is the help text misleading?

Any working example or clarification would be appreciated.

[stevevillardi]

You should be able to achieve what your trying to do via the PowerShell module/Rest API. It's been a minute since I've personally tried to run a remote groovy cmd via the module but let me take a look and see what's causing the issue if any. I don't have a unit tests for this particular cmdlet due to the nature of how it works but let me check if possibly the API structure has changed.

[stevevillardi]

@rdmarsh I think I see what the issue was. I just released a new version 7.7.4 that fixes the issue. I have some pre execution code that runs when using the inline -GroovyCommand that I have to autoPopulate the hostProps and instanceProps when specifying a -CommandHostName and -CommandWildValue:

!groovy
import com.santaba.agent.collector3.CollectorDb;
def hostProps = [:];
def instanceProps = [:];
try {
    hostProps = CollectorDb.getInstance().getHost("$CommandHostName").getProperties();
    instanceProps["wildvalue"] = "$CommandWildValue";
    }
catch(Exception e) {

};

Somehow it was picked up and reformatted by my code linting. I went and fix the bug if you want to try running that v7.7.4 version and see if that fixes your issue: