Skip to content

feat: Support custom regex parsing s3 logfile #84

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

aduncan314
Copy link

Which problem is this PR solving?

Short description of the changes

Injects REGEX_PATTERN into lambda environment to be used by https://github.com/honeycombio/agentless-integrations-for-aws

Another PR (#74), seems to have covered this, but added other features as well. Hopefully, keeping this simple will smooth things out.

How to verify that this has the expected result

I am not completely sure how the terraform testing works in the repository. I am happy to write a test with a little direction from a maintainer.

note:
This change was inspired by the desire to have more vpc flowlog fields. It's probably a good idea to add default regex in the agentless-integrations-for-aws project. I started doing that, but decided it would be nice to have this feature anyway since custom output is allowed.

@aduncan314 aduncan314 requested a review from a team as a code owner March 5, 2025 20:13
@TylerHelmuth TylerHelmuth added the status: oncall Flagged for awareness from Honeycomb Telemetry Oncall label Mar 5, 2025
@kentquirk kentquirk removed the status: oncall Flagged for awareness from Honeycomb Telemetry Oncall label Jul 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow specifying a custom regex pattern for the s3-logfile module s3-logfile: support providing a custom regex for log parsing
3 participants