Skip to content

Commit 58b3013

Browse files
committed
update image name
1 parent 165c6f9 commit 58b3013

2 files changed

Lines changed: 1 addition & 1 deletion

File tree

support/sql/database-engine/availability-groups/media/use-agdiag-diagnose-availability-group-health-events/launch-sql-logscout-powershell.png renamed to support/sql/database-engine/availability-groups/media/use-agdiag-diagnose-availability-group-health-events/launch-sql-log-scout-powershell.png

File renamed without changes.

support/sql/database-engine/availability-groups/use-agdiag-diagnose-availability-group-health-events.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ To diagnose an availability group health event, use SQL LogScout to collect logs
4040
.\SQL_LogScout.ps1 -Scenario "Basic" -ServerName "<Your_Sql_Instance_Name>"
4141
```
4242

43-
:::image type="content" source="media/use-agdiag-diagnose-availability-group-health-events/launch-sql-logscout-powershell.png" alt-text="Screenshot of starting SQL LogScout from an elevated PowerShell command window":::
43+
:::image type="content" source="media/use-agdiag-diagnose-availability-group-health-events/launch-sql-log-scout-powershell.png" alt-text="Screenshot of starting SQL LogScout from an elevated PowerShell command window":::
4444

4545
1. When the log capture process completes, you can point AGDiag to the `\output` folder created inside the SQL LogScout folder. This folder contains the logs collected by SQL LogScout.
4646

0 commit comments

Comments
 (0)