Skip to content

Conversation

@dosmanak
Copy link
Contributor

I let Gemini to generate the rule with some help of course ;-)

@cla-bot
Copy link

cla-bot bot commented May 22, 2025

Welcome to the Problem Detection Community and thank you for your pull request!

New contributors need to sign the Contributor License Agreement. In order for us to review and merge your code, please email contributor-agreement@prequel.dev with a link to this PR to complete the CLA process.

@cla-bot
Copy link

cla-bot bot commented May 22, 2025

Welcome to the Problem Detection Community and thank you for your pull request!

New contributors need to sign the Contributor License Agreement. In order for us to review and merge your code, please email contributor-agreement@prequel.dev with a link to this PR to complete the CLA process.

@Lyndon-prequel
Copy link
Contributor

Lyndon-prequel commented May 26, 2025

thanks for your submission. the community is reviewing.

@tonymeehan
Copy link
Contributor

Thanks for your contribution @dosmanak! Can we add some test data to a test.log file? That will allow us to iterate on the regular expression. I'm wondering if there's an opportunity to make it a bit more readable.

@Lyndon-prequel
Copy link
Contributor

@dosmanak thanks again for your submission. To ensure the rules are validated, contributors either:

  1. produce redacted/anonymized log data from an actual incident
  2. reproduce the known issue on their end

The generated data (i.e. logs) is added to a test.log file. Let us know if you're up for it.

@tonymeehan tonymeehan merged commit b22fc6f into prequel-dev:main Jun 7, 2025
0 of 2 checks passed
@dosmanak
Copy link
Contributor Author

dosmanak commented Jun 8, 2025

Hi, I was sick so I didn't react. I am sorry for that. Thank you for merging it anyway.

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.

3 participants