Microsoft/bcquality
1
0
Fork 0
mirror of https://github.com/microsoft/BCQuality.git synced 2026-08-07 01:46:53 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
bcquality/community/knowledge/telemetry/default-telemetryscope-to-extensionpublisher.md
Jeremy Vyska f5156c61de Add 15 community knowledge articles from BC Code Intel ingest 
Ingests net-new /community knowledge from BC Code Intelligence, surviving
the admission test, gray-zone salvage, and dedup against the full corpus.

Domains: ui (6), error-handling (3), performance (2), upgrade (1),
appsource (1), security (1), telemetry (1). The two BC24 No. Series
migration drafts are merged into one article.

Adds good/bad AL samples for the clean-fit articles (error-handling,
performance, security, telemetry). UI and appsource remain knowledge-only.

Validator and knowledge-index checks pass (207 articles).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-01 11:02:48 +02:00

1.7 KiB
Raw Permalink Blame History

bc-version domain keywords technologies countries application-area
all
telemetry
telemetry
session-logmessage
telemetryscope
application-insights
extensionpublisher
ingestion-cost
al
w1
all

Default TelemetryScope to ExtensionPublisher, not All

Contributions welcome — open a PR to refine or extend this article.

Description

The TelemetryScope parameter of Session.LogMessage (and LogError) controls where a custom telemetry signal is routed, not just whether it is emitted. TelemetryScope::ExtensionPublisher sends the signal only to the extension publisher's own Application Insights resource. TelemetryScope::All sends it to both the publisher's resource and the customer's environment-level Application Insights resource. The distinction is easy to get wrong because both values compile and both "emit telemetry" — but All silently adds to the customer's ingestion volume and cost.

Best Practice

Default to TelemetryScope::ExtensionPublisher for diagnostic telemetry that only the publisher acts on. Reserve TelemetryScope::All for signals the customer's own administrators are expected to monitor and act on (for example, a business event surfaced to their environment telemetry). Treat the choice as a deliberate routing decision per signal, not a copy-paste default.

Anti Pattern

Emitting all custom telemetry with TelemetryScope::All "to be safe." This pushes the publisher's internal diagnostics into every customer's Application Insights, inflating their ingestion cost and burying their own signals in noise — a footgun a code reviewer can catch by flagging All on any signal the customer would not act on.