Skip to content

Commit a596f52

Browse files
committed
updated logging section
1 parent d4402d8 commit a596f52

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -26,14 +26,6 @@ Define permissions for your runbook to run on the Hybrid Runbook Worker in the f
2626
* Configure authentication using [managed identities for Azure resources](../active-directory/managed-identities-azure-resources/tutorial-windows-vm-access-arm.md#grant-your-vm-access-to-a-resource-group-in-resource-manager).
2727
* Specify a Run As account to provide a user context for all runbooks.
2828

29-
## Logging
30-
31-
Logs are stored locally on each hybrid worker to the following location:
32-
33-
* On Windows at `C:\ProgramData\Microsoft\System Center\Orchestrator\<version>\SMA\Sandboxes`. High-level runbook job status events are written to the **Application and Services Logs\Microsoft-Automation\Operations** event log.
34-
35-
* 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`.
36-
3729
## Use runbook authentication to local resources
3830

3931
If preparing a runbook that provides its own authentication to resources, use [credential](./shared-resources/credentials.md) and [certificate](./shared-resources/certificates.md) assets in your runbook. There are several cmdlets that allow you to specify credentials so that the runbook can authenticate to different resources. The following example shows a portion of a runbook that restarts a computer. It retrieves credentials from a credential asset and the name of the computer from a variable asset and then uses these values with the `Restart-Computer` cmdlet.
@@ -307,6 +299,14 @@ When starting a runbook using PowerShell, use the `RunOn` parameter with the [St
307299
Start-AzAutomationRunbook –AutomationAccountName "MyAutomationAccount" –Name "Test-Runbook" -RunOn "MyHybridGroup"
308300
```
309301
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+
310310
## Next steps
311311
312312
* 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)