You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix stacked headings, interval text, and format JSON in tables
- Add intro paragraph between H1/H2 to fix stacked headings
- Remove 5-min interval reference, keep only 30-min default
- Format JSON in tables with line breaks and indentation using br/nbsp
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy file name to clipboardExpand all lines: articles/cosmos-db/monitor-activity-logs-elastic-operations.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -92,15 +92,15 @@ The image below shows how these properties appear in the JSON tab of the Activit
92
92
93
93
:::image type="content" source="media/monitor-activity-logs-elastic-operations/split-succeeded-status.png" lightbox="media/monitor-activity-logs-elastic-operations/split-succeeded-status.png" alt-text="Screenshot of the Succeeded status entry for a completed partition split operation.":::
94
94
95
-
### Activity Log Status JSON Table
95
+
### Activity Log status JSON
96
96
97
-
The table below shows the JSON properties emitted at each stage of a partition split operation. Checkpoint 1 and Checkpoint 2 illustrate how the In Progress status updates over time as partitions complete their work.
97
+
The following JSON properties are emitted at each stage of a partition split operation. Checkpoint 1 and Checkpoint 2 illustrate how the In Progress status updates over time as partitions complete their work.
| Started |`{"isSharedThroughput": "False","resourceRid": "<id>","databaseName": "database1","collectionName": "container1","targetThroughput": "15000","status": "Will split partitions 0 into different partitions"}`||
@@ -156,26 +156,26 @@ In this example view, Round 1 of the split is surrounded by the blue box and sho
156
156
157
157
:::image type="content" source="media/monitor-activity-logs-elastic-operations/multi-round-split-rounds.png" lightbox="media/monitor-activity-logs-elastic-operations/multi-round-split-rounds.png" alt-text="Screenshot of the Activity Log portal view showing Round 1 and Round 2 split entries highlighted in separate boxes.":::
158
158
159
-
### Activity Log Status JSON Table
159
+
### Activity Log status JSON
160
160
161
-
The table below shows the JSON content extracted directly from the Activity Log entries. For clarity, the common JSON fields are omitted and only the status is left.
161
+
The following JSON content is extracted directly from the Activity Log entries. For clarity, the common JSON fields are omitted and only the status is left.
Partition 0 has finished splitting, as shown by the transition from an In Progress operation to a Completed Operation. Now we move on to split Partition 2.
@@ -225,12 +225,12 @@ The image below shows how these properties appear in the JSON tab of the Activit
225
225
226
226
:::image type="content" source="media/monitor-activity-logs-elastic-operations/merge-succeeded-status.png" lightbox="media/monitor-activity-logs-elastic-operations/merge-succeeded-status.png" alt-text="Screenshot of the Succeeded status entry for a completed partition merge operation.":::
227
227
228
-
### Activity Log Status JSON Table
228
+
### Activity Log status JSON
229
229
230
-
The table below shows the JSON properties emitted at each stage of a merge operation. Checkpoint 1 and Checkpoint 2 illustrate how the In Progress status updates over time as partitions complete their work.
230
+
The following JSON properties are emitted at each stage of a merge operation. Checkpoint 1 and Checkpoint 2 illustrate how the In Progress status updates over time as partitions complete their work.
0 commit comments