-
Notifications
You must be signed in to change notification settings - Fork 489
[Faitour] Initial Push of Beta Integration #13304
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
Conversation
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
This is still relevant, and I would like to see it merged. Is there anything else needed on my end to get this approved? |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
packages/faitour/data_stream/honeypot/_dev/test/pipeline/test-events.log
Show resolved
Hide resolved
packages/faitour/data_stream/honeypot/_dev/test/pipeline/test-common-config.yml
Outdated
Show resolved
Hide resolved
packages/faitour/data_stream/honeypot/_dev/test/pipeline/test-common-config.yml
Outdated
Show resolved
Hide resolved
packages/faitour/data_stream/honeypot/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/faitour/data_stream/honeypot/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there supposed to be an ingest pipeline and tests associated with this data stream?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took this idea from a different integration that did the same (I forget which). Since I am using two different datasets for the application logs and the honeypot events, the integration tests fail if there is not also a second dataset defined. The one ingest pipeline under honeypot
handles all the events.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you confirmed that this works in a real set-up?
/test |
Forgot to mention; this will need to have a line added to |
Commit suggested changes to README.md from code review. Co-authored-by: Dan Kortschak <[email protected]>
Commit suggested change to changelog.yml from code review. Co-authored-by: Dan Kortschak <[email protected]>
Co-authored-by: Dan Kortschak <[email protected]>
Co-authored-by: Dan Kortschak <[email protected]>
…common-config.yml Co-authored-by: Dan Kortschak <[email protected]>
…common-config.yml Co-authored-by: Dan Kortschak <[email protected]>
All suggested changes have been made. |
/test |
packages/faitour/data_stream/honeypot/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/faitour/data_stream/honeypot/_dev/test/pipeline/test-events.log-expected.json
Outdated
Show resolved
Hide resolved
packages/faitour/data_stream/honeypot/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
You will need to re-run |
/test |
🚀 Benchmarks reportTo see the full report comment with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Test coverage improvements only, then LGTM
packages/faitour/data_stream/honeypot/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
############################## | ||
## Handle ECS Server Fields ## | ||
############################## | ||
- rename: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add a test sample event to test this processor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I could have sworn the pipeline tests passed before with both the faitour.honeypot
and faitour.application
datastreams when I had too many test events, but now that I am trying to add a test event that would be in the faitour.application
datastream for this, the pipeline tests are failing with:
FAILURE DETAILS:
faitour/honeypot test-events.log:
[0] field "event.dataset" should have value in ["faitour.honeypot"], it has "faitour.application"
[1] parsing field value failed: field "event.dataset"'s value "faitour.application" does not match the declared constant_keyword value "faitour.honeypot"
I don't want two separate logs in my application, but I do want events related to the application distinguishable from activity against the honeypot in Elastic. I tried removing the event.dataset
field declaration from base-fields.yml
, and that handled the error [1]
, but it still gives the same error [0]
.
How can I add an event for data_stream.dataset: faitour.application
into the test events and get around this? The events do get parsed properly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can I add an event for
data_stream.dataset: faitour.application
into the test events and get around this?
If you want to do something like this you will need to route one of them to a different data stream. I'm not sure that this feels like it is worth it; testing in this case is harder (read, "not actually possible at the moment").
Can you tolerate a softer separation between the two types of data?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will tolerate whatever it takes to not have to completely rewrite my logging, hahaha!
packages/faitour/data_stream/honeypot/elasticsearch/ingest_pipeline/default.yml
Show resolved
Hide resolved
/test |
💚 Build Succeeded
History
|
|
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as |
Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution! |
Type of change
Proposed commit message
This is an initial push for a new Integration
Faitour
: MakoWish/FaitourChecklist
changelog.yml
file.Author's Checklist