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

fix(tracing) lower tracing_sampling_rate to 0.01 #10774

Merged
merged 2 commits into from
May 5, 2023

Conversation

kikito
Copy link
Member

@kikito kikito commented May 2, 2023

Summary

Lower the default for tracing_sampling_rate. Tracing every request is not operative for any production system.

Notice that tracing_sampling_rate = 1 is appropriate for testing purposes, where it's more convenient and faster to always produce traces.

Checklist

Full changelog

Changed default value of tracing_sampling_rate from 1 to 0.01

Issue reference

FTI-5032

@kikito kikito added this to the 3.3.0 milestone May 2, 2023
@kikito kikito force-pushed the fix/lower-tracing-sampling branch 3 times, most recently from 3c21b6d to 6f38494 Compare May 2, 2023 14:20
@hbagdi
Copy link
Member

hbagdi commented May 2, 2023

The admin API spec change looks unrelated. I suggest sending a separate PR for it.

@kikito kikito force-pushed the fix/lower-tracing-sampling branch from 6f38494 to dd2ffef Compare May 2, 2023 21:48
@kikito kikito requested a review from samugi May 3, 2023 11:08
kong-admin-api.yml Outdated Show resolved Hide resolved
@kikito kikito force-pushed the fix/lower-tracing-sampling branch from 5332ee8 to e6d8282 Compare May 5, 2023 08:33
@pull-request-size pull-request-size bot added size/M and removed size/XL labels May 5, 2023
@kikito kikito merged commit b269802 into master May 5, 2023
@kikito kikito deleted the fix/lower-tracing-sampling branch May 5, 2023 15:36
team-gateway-bot pushed a commit that referenced this pull request May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants