Skip to content

Commit d78a44a

Browse files
authored
Merge pull request #127386 from MGoedtel/task1764637
new log section
2 parents d6daf55 + a596f52 commit d78a44a

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

articles/automation/automation-hrw-run-runbooks.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Run Azure Automation runbooks on a Hybrid Runbook Worker
33
description: This article tells how to run runbooks on machines in your local datacenter or cloud provider with the Hybrid Runbook Worker.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 01/29/2019
6+
ms.date: 08/26/2020
77
ms.topic: conceptual
88
---
99
# Run runbooks on a Hybrid Runbook Worker
@@ -299,6 +299,14 @@ When starting a runbook using PowerShell, use the `RunOn` parameter with the [St
299299
Start-AzAutomationRunbook –AutomationAccountName "MyAutomationAccount" –Name "Test-Runbook" -RunOn "MyHybridGroup"
300300
```
301301
302+
## Logging
303+
304+
To help troubleshoot issues with your runbooks running on a hybrid runbook worker, logs are stored locally in the following location:
305+
306+
* On Windows at `C:\ProgramData\Microsoft\System Center\Orchestrator\<version>\SMA\Sandboxes` for detailed job runtime process logging. High-level runbook job status events are written to the **Application and Services Logs\Microsoft-Automation\Operations** event log.
307+
308+
* On Linux, the user hybrid worker logs can be found at `/home/nxautomation/run/worker.log`, and system runbook worker logs can be found at `/var/opt/microsoft/omsagent/run/automationworker/worker.log`.
309+
302310
## Next steps
303311
304312
* If your runbooks aren't completing successfully, review the troubleshooting guide for [runbook execution failures](troubleshoot/hybrid-runbook-worker.md#runbook-execution-fails).

0 commit comments

Comments
 (0)