186d8a1314
* Complete AL review knowledge readiness Fill telemetry and Query coverage, strengthen thin review domains, correct audited content defects, and add deterministic cheap-model evaluation and reference-integrity safeguards. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27 * Generalize review fixture discovery Derive smoke cases from the leaf, domain, and paired-sample conventions so new leaves require no scoring-contract changes. Keep only exceptional selection/context overrides and fail when retrieval metadata cannot rank the selected article. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27 * Preserve published field IDs in sample Keep the existing Email and Contact Email field IDs unchanged, clarify that the sample represents an independent baseline, and use a local breaking-change rule for the generic smoke evaluation. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27 * Clarify published field identity rules State explicitly that a published field keeps its ID, name, and type while a replacement is added as a separate field under an unused ID. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27 * Align field obsoletion sample baselines Use Email field ID 3 as the shared baseline so the bad example demonstrates a same-ID rename while the good example retains the original field and adds a separate replacement. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 9825b012-e653-496a-9310-c1f4b6f8ac27 --------- Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
1.5 KiB
| bc-version | domain | keywords | technologies | countries | application-area | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
telemetry |
|
|
|
|
Match telemetry Verbosity to the signal's actual severity
Description
Verbosity becomes the Application Insights severityLevel and participates in on-premises diagnostic trace filtering. Critical represents abnormal termination, Error a severe error, Warning a warning, Normal a non-error event, and Verbose detailed tracing. Logging a caught failure as Normal is not cosmetic: severity-based alerts miss it, and an on-premises service configured to emit only warnings and above can drop it completely.
Best Practice
Use Error for failed operations that need investigation and Critical only for abnormal termination or equivalent loss of service. Use Warning for degraded but completed behavior, Normal for successful business events, and Verbose for detailed diagnostics. Judge the outcome, not the procedure name: an expected optional lookup miss can legitimately remain Normal or Verbose.
See sample: match-verbosity-to-signal-severity.good.al.
Anti Pattern
A Session.LogMessage in a failed TryFunction, failed Codeunit.Run, unsuccessful HTTP response, or other explicit failure branch that uses Verbosity::Normal or Verbose without evidence that the failure is expected and benign.
See sample: match-verbosity-to-signal-severity.bad.al.