Skip to content

Commit 03f5412

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-metadata
2 parents 7fb4e92 + 25914c0 commit 03f5412

31 files changed

+27
-27
lines changed

articles/azure-monitor/app/convert-classic-resource.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -416,7 +416,7 @@ The structure of a Log Analytics workspace is described in [Log Analytics worksp
416416
| traces | AppTraces | Detailed logs (traces) emitted through application code/logging frameworks recorded via `TrackTrace()`. |
417417

418418
> [!CAUTION]
419-
> Don't take a production dependency on Log Analytics tables until you see new telemetry records show up directly in Log Analytics. Initially, after you trigger the migration, new telemetry will continue to be ingested into the Classic Application Insights tables. The switch to writing new telemetry records directly into Log Analytics tables may take up to 24 hours. During this transition period, there is no interruption or loss of data, and telemetry will not be written to both systems simultaneously. Once the migration operation is complete, all new telemetry will only be recorded in the Log Analytics tables.
419+
> Wait for new telemetry in Log Analytics before relying on it. After starting the migration, telemetry first goes to Classic Application Insights. Aim to switch to Log Analytics within 24 hours, avoiding data loss or double writing. Once done, Log Analytics solely captures new telemetry.
420420
421421
### Table schemas
422422

-3.16 KB
Loading
-1.92 KB
Loading
-221 KB
Loading
Loading
-9.95 KB
Loading

articles/stream-analytics/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -882,7 +882,7 @@
882882
- name: Feedback forum
883883
href: https://feedback.azure.com/d365community/forum/d12ec4e3-b825-ec11-b6e6-000d3a4f0f1c
884884
- name: Microsoft Q&A question page
885-
href: /answers/topics/azure-stream-analytics.html
885+
href: /answers/tags/179/azure-stream-analytics
886886
- name: Pricing
887887
href: https://azure.microsoft.com/pricing/details/stream-analytics/
888888
- name: Pricing calculator

articles/stream-analytics/automation-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -440,7 +440,7 @@ Once the script is understood, it's straightforward to rework it to extend its s
440440

441441
## Get support
442442

443-
For further assistance, try our [Microsoft Q&A question page for Azure Stream Analytics](/answers/topics/azure-stream-analytics.html).
443+
For further assistance, try our [Microsoft Q&A question page for Azure Stream Analytics](/answers/tags/179/azure-stream-analytics).
444444

445445
## Next steps
446446

articles/stream-analytics/input-validation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -551,7 +551,7 @@ Finally, we can do some light integration testing in VS Code. We can insert reco
551551

552552
## Get support
553553

554-
For further assistance, try our [Microsoft Q&A question page for Azure Stream Analytics](/answers/topics/azure-stream-analytics.html).
554+
For further assistance, try our [Microsoft Q&A question page for Azure Stream Analytics](/answers/tags/179/azure-stream-analytics).
555555

556556
## Next steps
557557

articles/stream-analytics/sql-database-upsert.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -426,7 +426,7 @@ Each approach offers different value proposition and capabilities:
426426

427427
## Get support
428428

429-
For further assistance, try our [Microsoft Q&A question page for Azure Stream Analytics](/answers/topics/azure-stream-analytics.html).
429+
For further assistance, try our [Microsoft Q&A question page for Azure Stream Analytics](/answers/tags/179/azure-stream-analytics).
430430

431431
## Next steps
432432

0 commit comments

Comments
 (0)