Product: PowerShell Universal
Version: 2026.1.2
Hi.
I have a job that runs very often, polling our e services platform for new tickets. 99% of the times there is nothing to fetch, so the job log is quickly getting filled up by jobs that are not interesting, so finding the jobs that actually did something is hard. Also, even though I’ve set the max history of this script very high, the log posts quickly get rotated out.
Wouldn’t it be nice with a cmdlet that you could put in a script, telling the PSU environment that this particular job shouldn’t be stored in the job log at all? Is this something that would be possible to implement?