powershell

2 Topics

[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.
Solved
Zahir_Sheikkari
2 years ago Place Feature Requests
109Views
14likes
7Comments
PowerShell -- Instance Property Support
It had been ages since I had to write a datasource in PowerShell so I haven't stayed up-to-date on the latest bells and whistles available. But I was very surprised to see that instance properties are still notsupported. With the substitution engine and enhancements made on the Groovy-side, I would have thought this trivial to implement. Is supporting instance properties on the horizon for PowerShell scripting for Datasources?
Joe_Tran
3 years ago Place Feature Requests
19Views
0likes
6Comments