Skip to content

Commit c35c3a7

Browse files
authored
Update enable-diagnostic-logging.md
1 parent 4b3400a commit c35c3a7

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/healthcare-apis/dicom/enable-diagnostic-logging.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ In this article, you'll learn how to enable diagnostic logging in DICOM® ser
3535
* **Stream to an event hub** for ingestion by a third-party service or custom analytic solution. You need to create an event hub namespace and event hub policy before you can configure this step.
3636
* **Send to partner solution** that you're working with as a partner organization in Azure. For information about potential partner integrations, see [Azure partner solutions documentation](../../partner-solutions/overview.md)
3737

38-
For information about supported metrics, see [Supported metrics with Azure Monitor](azure/azure-monitor/essentials/metrics-supported).
38+
For information about supported metrics, see [Supported metrics with Azure Monitor](/azure/azure-monitor/essentials/metrics-supported).
3939

4040
6. Select **Save**.
4141

@@ -146,6 +146,6 @@ MicrosoftHealthcareApisAuditLogs
146146

147147
## Next steps
148148

149-
Having access to diagnostic logs is essential for monitoring a service and providing compliance reports. The DICOM service allows you to do these actions through diagnostic logs. For more information, see [Azure Activity Log event schema](azure/azure-monitor/essentials/activity-log-schema)
149+
Having access to diagnostic logs is essential for monitoring a service and providing compliance reports. The DICOM service allows you to do these actions through diagnostic logs. For more information, see [Azure Activity Log event schema](/azure/azure-monitor/essentials/activity-log-schema)
150150

151151
[!INCLUDE [DICOM trademark statement](../includes/healthcare-apis-dicom-trademark.md)]

0 commit comments

Comments
 (0)