-
Notifications
You must be signed in to change notification settings - Fork 16.8k
Conversation
/assign @mgoodness |
Related: #4372 |
@sstarcher between this and #4372 which PR do you think would make more sense to merge first and have the other rebase? |
@rifelpet you took a different tact than I did. I removed the prospector directory and moved it into the primary configuration. I think the main thing of importance is it useful to separate the prospector configuration or to just merge it into the primary configuration? If we should keep the prospector we should merge yours first and I should redo mine. Opinions? |
@sstarcher I am by no means a Filebeat expert but I think consolidating the configurations into one kubernetes resource probably makes the most sense 👍 |
@rifelpet sounds good if that's the case sounds like we should get this one merged in first. |
/assign @rifelpet |
/ok-to-test |
/lgtm |
/assign @mgoodness |
/ok-to-test |
/assign |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet, sstarcher, timstoop, unguiculus The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* upgrade filebeat to 6.2.3 to prevent k8s metadata infinite loop * fix filebeat /var/log and drop seperate prospectors configuration * fix linting
* upgrade filebeat to 6.2.3 to prevent k8s metadata infinite loop * fix filebeat /var/log and drop seperate prospectors configuration * fix linting
* upgrade filebeat to 6.2.3 to prevent k8s metadata infinite loop * fix filebeat /var/log and drop seperate prospectors configuration * fix linting Signed-off-by: voron <av@arilot.com>
Fixes - elastic/beats#6353
And fixes logs from
/var/log
Drops filebeat logs to prevent excess pressure from filebeat erroring when the output is backed up