Skip to content

Commit e659073

Browse files
committed
Addressing feedback for image names
1 parent 037a872 commit e659073

File tree

3 files changed

+2
-2
lines changed

3 files changed

+2
-2
lines changed

articles/cosmos-db/audit-control-plane-logs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ You can enable diagnostic logs for control plane operations by using the Azure p
3535

3636
You can also store the logs in a storage account or stream to an event hub. This article shows how to send logs to log analytics and then query them. After you enable, it takes a few minutes for the diagnostic logs to take effect. All the control plane operations performed after that point can be tracked. The following screenshot shows how to enable control plane logs:
3737

38-
![Enable control plane requests logging](./media/audit-control-plane-logs/enable-control-plane-requests-logging.png)
38+
![Enable control plane requests logging](./media/audit-control-plane-logs/enable-control-plane-requests-logs.png)
3939

4040
## View the control plane operations
4141

@@ -62,7 +62,7 @@ The following screenshots capture logs when throughput of a Cassandra table is u
6262

6363
If you want to debug further, you can identify a specific operation in the **Activity log** by using the Activity ID or by the timestamp of the operation. Timestamp is used for some Resource Manager clients where the activity ID is not explicitly passed. The Activity log gives details about the identity with which the operation was initiated. The following screenshot shows ho to use the activity ID and find the operations associated with it in the Activity log:
6464

65-
![Use the activity ID and find the operations](./media/audit-control-plane-logs/find-operations-with-activityid.png)
65+
![Use the activity ID and find the operations](./media/audit-control-plane-logs/find-operations-with-activity-id.png)
6666

6767
## Next steps
6868

0 commit comments

Comments
 (0)