Microsoft/alguidelines
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update content/docs/BestPractices/CustomTelemetry/index.md

Browse source 
Removed the word period
This commit is contained in:
Henrik Helgesen 2022-03-24 14:50:26 -07:00 • committed by GitHub
parent 42358aab34
commit 417cc2f025
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
content/docs/BestPractices/CustomTelemetry/index.md
View file

@ -71,7 +71,7 @@ Of course it is possible to have a single object as a central place to emit tele
## Candidate data for telemetry ## Candidate data for telemetry
Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on period (knowing about CPU performance counters on the database is useless if the partner cannot scale the database). Telemetry must be **actionable** for the customer. Do not emit signals that they cannot act on (knowing about CPU performance counters on the database is useless if the partner cannot scale the database).
Also, note that customers pay for data ingestion. So be mindful to not flood their telemetry resources. Consider to use TelemetryScope::ExtensionPublisher by default and only use TelemetryScope::All in case the customer can also act on the data. Also, note that customers pay for data ingestion. So be mindful to not flood their telemetry resources. Consider to use TelemetryScope::ExtensionPublisher by default and only use TelemetryScope::All in case the customer can also act on the data.