Skip to content

Commit e4dae81

Browse files
Merge pull request #261538 from khelanmodi/vCore-diag-logging
Updating diagnostics-logs
2 parents aa5c3d3 + e3945d5 commit e4dae81

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/cosmos-db/mongodb/vcore/how-to-monitor-diagnostics-logs.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,8 +108,11 @@ Platform metrics and Activity logs are gathered automatically. To collect resour
108108
109109
> [!IMPORTANT]
110110
> By enabling the `--export-to-resource-specific true` setting, you ensure that the API for MongoDB vCore request log events are efficiently ingested into the `vCoreMongoRequests` table specifically designed with a dedicated schema.
111-
>
111+
>
112112
> In contrast, neglecting to configure `--export-to-resource-specific true` would result in the API for MongoDB vCore request log events being routed to the general `AzureDiagnostics` table.
113+
>
114+
> It's important to note that when creating the diagnostic setting through the Portal, log events will currently flow to the `AzureDiagnostics` table. For customers who prefer exporting logs to the resource-specific `VCoreMongoRequests` table, utilizing the Azure CLI with the `--export-to-resource-specific true` option is recommended.
115+
>
113116
114117
### [Azure Storage account](#tab/azure-storage)
115118

0 commit comments

Comments
 (0)