Zahir_Sheikkari
Joined 11 months ago
User Profile
User Widgets
Contributions
Re: [Feature request] Custom PowerShell script: increase timeout
I think the ask here is to be able to tune the timeout per script -- not a bad idea in general. However, I think the actual feature you want is what Nagios and other monitoring systems call “passive checks”. We used that ALL the time to have long-running scripts generate results and inject them into monitoring. LM does not have that, but it does have Script Caching, which could potentially be useful to run scripts and fetch results asynchronously. Sadly, that is not a general distributed facility like redis (which I’d recommended years ago), it only works for Groovy scripts. There is no PowerShell binding (perhaps I am wrong on that, but I don’t see it in the documentation). You could fake this yourself with files, though. You would need to schedule your script to run asynchronously (e.g., via Task Scheduler) and write results into a known location on the collector (or a filesystem reachable by the collector). Then your datasource would just need to fetch the latest results from the filesystem and quickly process. You’d want to check whether the data is too old so you can produce no results if that is the case. Interesting last paragraph. Will look into this, thanks.1View1like0CommentsRe: [Feature request] Custom PowerShell script: increase timeout
Have you tried changing any of the collector’s agent.conf settingssuch as thecollector.script.timeout value? Yes I've raised various timeout settings including this one. Chat support confirmed there is a hardcoded setting of 120 seconds which cannot be increased. They weren’t aware as to why this is. They even recommended not changing the 120 value at all.0Views0likes0Comments[Feature request] Custom PowerShell script: increase timeout
Hello, I was advised to go here after chatting with support. I have run into an issue where our custom PowerShell script runs into the hardcoded 120 second timeout. We're initially testing it first via the Test button. The error after exactly 120 seconds is: “"Test script failed - no response was received from the Collector"”. The script runs okay in PowerShell 5.1, but it averages around 2,6 minutes. We have already cut the runtime down from around 4 minutes to 2,6 minutes and that's the best we can do. It starts generating “Write-Host” data within 50 seconds for each object. We are pulling data from public API endpoints and perform some logic for 2 large arrays. The script will run against a dedicated collector. Issue is in the sandbox as well as in the production environment.Solved67Views13likes7Comments