Implement log shipping to Graylog via GELF #786
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bnazare
force-pushed
the
feature/log-shipping
branch
from
c74db80
to
ea44d04
Compare
bnazare
force-pushed
the
feature/log-shipping
branch
from
ea44d04
to
a29589a
Compare
|
This PR is a counterpart to OpenCTI-Platform/opencti#8410. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Related issues
There are no related issues but this subject has been previously discussed with Linkare within the scope of the OpenCTI implementation for the Centre for Cybersecurity Belgium (https://ccb.belgium.be/).
Checklist
Further comments
We enabled the new functionality in the configuration of some of the existing test cases. However, there are currently no new assertions being made as that would require the set-up of an entire Graylog infrastructure during tests, which is a much more involved task. Effectively, this means that the new code is being exercised but all log shipping is being shipped to a closed port and any network errors are silently ignored.