-
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
Support Elasticsearch HTTPS & Basic Auth #10
Support Elasticsearch HTTPS & Basic Auth #10
Conversation
Merged, thanks! |
Hi @lmars, I tried to email you but I got no response so I'm trying my luck here as well. We have exciting plans for the Packetbeat project and I'm writing to you because we'd like to change the license for the next version of Packetbeat from GPLv2 to Apache 2, which we think will encourage the adoption even more. You have contributed code to the project, so we'd like to ask for your approval before we do the change. If you agree with the license change, a simple reply saying that you are fine with it would be enough. If you have any questions about the license change or the project in general, feel free to ask me. |
@tsg fine by me |
Thanks! |
This implementation uses a channel to pass the bulk messages. The caller needs to write the operations to the channel, close the channel and call the Bulk method.
- Add basic authentication to connect to Elasticsearch. Username and password are configurable. - Add path prefix to the HTTP API calls to Elasticsearch
The problem appears when the bulkChannel reaches the maximum size, the go-routine blocks and no more data are consumed from the channel. To fix the problem, make sure the bulkChannel doesn't reach the maximum size by consuming the data before the channel is full.
The maximum bulk size is configurable (bulk_size) from the output/<output> section.
Add a `make dist` target to package the dashboards.
Set skip_cleanup to true
This implementation uses a channel to pass the bulk messages. The caller needs to write the operations to the channel, close the channel and call the Bulk method.
- Add basic authentication to connect to Elasticsearch. Username and password are configurable. - Add path prefix to the HTTP API calls to Elasticsearch
The problem appears when the bulkChannel reaches the maximum size, the go-routine blocks and no more data are consumed from the channel. To fix the problem, make sure the bulkChannel doesn't reach the maximum size by consuming the data before the channel is full.
The maximum bulk size is configurable (bulk_size) from the output/<output> section.
Glide improvements
Create linter configuration and address found issues. Also added magefile targets so it's running on the CI.
No description provided.