need method to set properties in groovy code

Totally agreed that LMConfig should be included in base. That one's above my paygrade.

Unless I miss your meaning, I think LMConfig does alert on changes:

Totally agreed that LMConfig should be included in base. That one's above my paygrade.

Unless I miss your meaning, I think LMConfig does alert on changes:

LMConfig does not send changes.  It can alert that "something changed", which is about as useful as a red light in your car console saying "something is wrong".

As far as the rest -- the issue is there is currently no viable way to solve this without bolting on an API method entirely outside of LM.  I can do this, but I hate being forced to do it all the time.  There are some simple fixes, like allow tables to display properties and allow setting properties without cutting and pasting 50+ lines of API code repeatedly (glad you are on that one!), that would make things much better.  I have had numerous conversations with product development folks and improvements happen all the time.  Unfortunately, most of those are the glitzy marketable types, and the lower level nuts and bolts tend to get less attention.

Ah, I see what you mean. I think there is a FR in to have the changed lines, before lines, and after lines as tokens so they can be included in the alarm message.

I'm going to silently nod about the rest (pun intended).

On 10/19/2019 at 3:42 AM, mnagel said:

If there could be a hostProps.set method, that would be very helpful. 

 +1 from me

I am also looking for this feature.

My use case is different but basically it boils down to "How can I maintain a variable between executions of a script"

I will be doing the 'file in tmp' suggestion, but as stated this is flawed as it might disappear, get cleaned out, etc. My use case is not sensitive to failure so this will work, but a hostProps.set would be ideal.

For a more sensitive flow that required maintaining of state, I did a API request to the devices endpoint in Logic monitor to 'set' properties with a limited api user account created for this purpose. Basically got a 'two way flow' working: LM -> Collector and Collector -> LM (though the API). It was so dirty I showered after.

I can post the link later but there is a script caching capability that will allow you to carry values from one run of a script to the next through a cache on the collector.

Here's the info on script caching: https://www.logicmonitor.com/support/collectors/collector-configurations/collector-script-caching

Does this work between collectors in ABCG? Like if a device balances to another collector or if there is a failover/failback?

No. ABCG don't share a single cache.

You should have logic in your code to compensate when the cache doesn't have the data so that it can be fetched brand new if needed. Typical cache logic is build for performance so you don't have to do "heavy" calls for stuff that doesn't change that often. But if that thing doesn't exist in the cache you should do the heavy call and store it in cache for subsequent runs.