-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Refactoring] Consolidate common HTTP settings #16856
Labels
libbeat
refactoring
Stalled
Team:Services
(Deprecated) Label for the former Integrations-Services team
Comments
ycombinator
added
refactoring
libbeat
good first issue
Indicates a good issue for first-time contributors
labels
Mar 5, 2020
2 tasks
andresrc
added
[zube]: Inbox
[zube]: Backlog
Team:Services
(Deprecated) Label for the former Integrations-Services team
and removed
good first issue
Indicates a good issue for first-time contributors
[zube]: Inbox
labels
Mar 5, 2020
Pinging @elastic/integrations-services (Team:Services) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
libbeat
refactoring
Stalled
Team:Services
(Deprecated) Label for the former Integrations-Services team
We have a few HTTP clients spread across the Beats codebase. There is a common set of configuration options that apply to any HTTP client, e.g. host, timeouts, SSL-related configuration, etc. It would be nice to consolidate such common options into a struct somewhere under
libbeat/common/transport
perhaps and then use it in the various HTTP clients. This would ensure that all clients support the same common configuration optinos and users can specify them using the same setting names.The text was updated successfully, but these errors were encountered: