-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add delay for telemetry requests #198
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one concern about the exposure of raw setting names leading to inadvertent breaking changes. Other than that looks good!
--- | ||
features: | ||
- | | ||
Added a /test/settings endpoint to change the settings on the fly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
little bit iffy about exposing the raw config values direct to users. This'll probably result in accidental breakages to downstream test suites that depend on config values that we might accidentally change in the test agent.
If we do wanna go this route then I'll want to ensure we have tests covering the config names we want to be stable. Otherwise can we hold off on adding this endpoint for now?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done in faf6994
Extend
--trace-request-delay
to also affect trace requests.Also, add a
test/settings
endpoint to change the value of settings on the fly.