Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Telemetry design #11175

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from
Draft

Telemetry design #11175

wants to merge 3 commits into from

Conversation

JanProvaznik
Copy link
Member

Fixes #10947

Context

Writeup of proposed telemetry implementation based on experimentation in #11084

Copy link
Member

@JanKrivanek JanKrivanek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thanks!!

documentation/specs/proposed/VS-OpenTelemetry.md Outdated Show resolved Hide resolved
documentation/specs/proposed/VS-OpenTelemetry.md Outdated Show resolved Hide resolved
### Data handling

- Implement head [Sampling](https://opentelemetry.io/docs/concepts/sampling/) with the granularity of a MSBuild.exe invocation/VS instance.
- VS Data handle tail sampling in their infrastructure not to overwhelm storage with a lot of build events.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed - we should not prevent ourselves to be able to add (in future versions):

  • different sampling rates for different namespaces/activities
  • ability to configure the overal and per-namespace sampling from server side (e.g. storing it in the .msbuild folder in user profile if different then default values set from server side - this would obviously have a delay of the default sample rate # of executions)


## Looking ahead

- Create a way of using a "HighPrioActivitySource" which would override sampling and initialize Collector in MSBuild.exe scenario/tracerprovider in VS.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

More generaly - sample rate per Activity/namespace (higher even always or even lower or newer)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Propose/Design the way of referencing/using VS OTel
2 participants