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

Initial sampling rate from applicationHost.config fix #1048

Merged
merged 19 commits into from
Jan 10, 2019

Conversation

Mikhail-msft
Copy link
Contributor

@Mikhail-msft Mikhail-msft commented Jan 9, 2019

Fix of an InitialSamplingRate, when setting it through the applicationHost.config would not apply it.
Also resolves #926.

For significant contributions please make sure you have completed the following items:

  • [] Design discussion issue #
  • Changes in public surface reviewed
  • CHANGELOG.md updated with one line description of the fix, and a link to the original issue.
  • The PR will trigger build, unit test, and functional tests automatically. If your PR was submitted from fork - mention one of committers to initiate the build for you.

cijothomas and others added 17 commits November 20, 2018 14:14
* Fix: Start/StopOperation does not work when W3C is enabled

* build and changelog
Customer asked if we log Exception.Data.
This was not clear from our documentation.
#1028)

* Metrics: Use dedicated thread instead of the thread pool for the default aggregation cycle (code only, does not build not NetStandard).

* Add missing reference to System.Threading.Thread on netstandard1.3

* changelog
@SergeyKanzhelev
Copy link
Contributor

SergeyKanzhelev commented Jan 9, 2019

Does it address #926 as well? If not - can you please include that fix as well.

@Mikhail-msft
Copy link
Contributor Author

Mikhail-msft commented Jan 9, 2019

Does it address #926 as well? If not - can you please include that fix as well.

@SergeyKanzhelev, I cannot repro the issue you mentioned using latest develop bits. Do you have more details on the repro steps?

@Mikhail-msft
Copy link
Contributor Author

Does it address #926 as well? If not - can you please include that fix as well.

@SergeyKanzhelev, I cannot repro the issue you mentioned using latest develop bits. Do you have more details on the repro steps?

The issue was that inner SamplingTelemetryProcessor did not have the SamplingPercentage set to initial value. This is now fixed. Note changing behavior of Min-Max vs InitialSamplingPercentage is out of scope of this PR.

Copy link
Contributor

@SergeyKanzhelev SergeyKanzhelev left a comment

Choose a reason for hiding this comment

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

LGTM, thanks for fixing an additional issue. Please allow others to review as well

@SergeyKanzhelev
Copy link
Contributor

Note changing behavior of Min-Max vs InitialSamplingPercentage is out of scope of this PR.

Can you please make a remark in issue I referred to explaining what is fixed and what is not. Or create a separate one

@Mikhail-msft Mikhail-msft reopened this Jan 10, 2019
@Mikhail-msft Mikhail-msft merged commit 6b70c45 into develop Jan 10, 2019
@Mikhail-msft Mikhail-msft deleted the mikp/InitialSamplingRateFix branch January 10, 2019 01:29
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.

AdaptiveSamplingProcessor constructor doesn't respect arguments passed
8 participants