This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/etc/sv/kibana/log/main
is a very odd place to write logs. Although the runit manual mentions./main
as an example, the runit cookbook uses/var/log/<service>
if you enable the default logger. The log template in this cookbook is otherwise identical to the default so we may as well remove it.We were spammed with email and Jabber messages every time someone clicked something in Kibana after turning our OSSEC syscheck on. We will have to ignore
/etc/sv
anyway because of other runit files but logs really shouldn't go here.