Targeting Sessions in ControlUp’s Analyze Logon Latency Script

A user asked about the Analyze Logon Duration script and how to target it to specific sessions. Another user suggested using a built-in trigger that runs after a login duration of 75 seconds and can also send an email output. The trigger name is "Analyze Logon Duration 75 Seconds" and is disabled by default.

Read the entire ‘Targeting Sessions in ControlUp’s Analyze Logon Latency Script’ thread below:

Hi! I have another query regarding analyze logon latency script. I am testing this script, and found that i cannot point the script action just to a machine/ folder. It seems like i should point this to a session.

so the script ran on all active sessions in the console , and generated whole bunch of alerts in our ticketing system.

is there a way that we can point this script to run only to particular sessions?

Yes you can. We have a built in trigger you can enable that it will run after a users login duration is 75secs+. It will do an email output as well if the results.

awesome, thanks. What is the trigger name for 75+?

Analyze Logon Duration 75 Seconds. It’s a built in trigger that is disabled by default.

Thank you

Continue reading and comment on the thread ‘Targeting Sessions in ControlUp’s Analyze Logon Latency Script’.  Not a member? Join Here!