To investigate performance issues—especially when a specific job might be consuming a large amount of CPU or memory—we need to find an easy way to identify which Automation Services (AS) instance executed that specific job.
We have already checked the AS logs, performance counter logs, server logs, and action logs, but none of them seem to provide this specific information.
