Skip to content
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

fix: Error handling in AWS Security Lake #390

Merged
merged 1 commit into from
Feb 10, 2023

Conversation

embano1
Copy link
Contributor

@embano1 embano1 commented Jan 15, 2023

Closes: #389
Signed-off-by: Michael Gasch 15986659+embano1@users.noreply.github.com

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:

Improves error handling in AWS Security Lake output.

Which issue(s) this PR fixes:

Fixes #389

Special notes for your reviewer:

I could not test the PR as I am not very familiar with the project (I'm the maintainer of memlog which is used here). Would be great to get some discussion on the PR as my understanding of the Falco agent behavior is limited.

cc/ @Issif

@poiana
Copy link

poiana commented Jan 15, 2023

Welcome @embano1! It looks like this is your first PR to falcosecurity/falcosidekick 🎉

outputs/awssecuritylake.go Outdated Show resolved Hide resolved
outputs/awssecuritylake.go Outdated Show resolved Hide resolved
outputs/awssecuritylake.go Outdated Show resolved Hide resolved
@Issif Issif self-assigned this Jan 17, 2023
@Issif
Copy link
Member

Issif commented Jan 30, 2023

@embano1 Can you take a look at my answers to your comments please

@embano1
Copy link
Contributor Author

embano1 commented Jan 30, 2023

@Issif sorry for my delayed response! Will hopefully get back to this until the EOW. Any deadline you have in mind/blocking you?

@Issif
Copy link
Member

Issif commented Jan 30, 2023

No deadline, take your time, I just wanted to be sure you still follow. Thanks

Closes: falcosecurity#389
Signed-off-by: Michael Gasch <15986659+embano1@users.noreply.github.com>
@embano1
Copy link
Contributor Author

embano1 commented Feb 2, 2023

@Issif made a couple more changes to catch edge cases. Please take a critical look :) Still not quite happy with the code as we ignore context errors, no proper shutdown logic and coarse error handling. But that's out of scope for this PR.

@Issif
Copy link
Member

Issif commented Feb 10, 2023

@Issif made a couple more changes to catch edge cases. Please take a critical look :) Still not quite happy with the code as we ignore context errors, no proper shutdown logic and coarse error handling. But that's out of scope for this PR.

The lack on contexts is something I know, for now, it's doesn't create any issue as far I know, but I'll change that in future v3. Like you said, it's way over the scope of this PR.

Thanks for your help.

@poiana poiana added the lgtm label Feb 10, 2023
@poiana
Copy link

poiana commented Feb 10, 2023

LGTM label has been added.

Git tree hash: 6fd404421199917b1f1159882038ccaa94e7b8e7

@poiana
Copy link

poiana commented Feb 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: embano1, Issif

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@poiana poiana merged commit 34059c2 into falcosecurity:master Feb 10, 2023
@embano1 embano1 deleted the issue-389 branch February 11, 2023 07:06
@Issif Issif added this to the 2.28.0 milestone Jul 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Fix error handling AWS Security Lake with memlog usage
3 participants