Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-10-05 14:46:55 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
bcquality/microsoft/knowledge/telemetry/match-verbosity-to-signal-severity.md
Jesper Schulz-Wedde 2b5550c346
Some checks failed
Validate knowledge index / validate-index (push) Has been cancelled
Details
Validate AL review fixtures / validate-review-fixtures (push) Has been cancelled
Details
Validate frontmatter and structure / validate (push) Has been cancelled
Details
Improve partner onboarding and documentation navigation (#174) 
Lead with a complete plugin quick start and add task-oriented usage, troubleshooting, customization, and contribution guides. Preserve the broader plugin framing, correct conflicting contract guidance, support Agents folder reviews, and align repository validation. Convert existing sample references to clickable links without changing knowledge rules.

Co-authored-by: Jesper Schulz-Wedde <jesper.schulzwedde@microsoft.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
2026-09-09 17:31:03 +02:00

1.6 KiB
Raw Blame History

bc-version domain keywords technologies countries application-area
17..
telemetry
verbosity
severitylevel
critical
error
warning
normal
verbose
logmessage
al
w1
all

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.