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

[crowdsec] lower log level to warn hub #2918

Open
LaurenceJJones opened this issue Mar 29, 2024 · 3 comments
Open

[crowdsec] lower log level to warn hub #2918

LaurenceJJones opened this issue Mar 29, 2024 · 3 comments

Comments

@LaurenceJJones
Copy link
Contributor

We now have this log line when a user supplies a custom scenario or parser, however, the level of error is quite high can we just warn instead?

time="2024-03-29T06:30:13Z" level=error msg="scenario laurencejjones/ufw-block (/etc/crowdsec/scenarios/ufw-block-trigger.yaml) couldn't be find in hub (ignore if in unit tests)"
Copy link

@LaurenceJJones: Thanks for opening an issue, it is currently awaiting triage.

In the meantime, you can:

  1. Check Crowdsec Documentation to see if your issue can be self resolved.
  2. You can also join our Discord.
  3. Check Releases to make sure your agent is on the latest version.
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

Copy link

@LaurenceJJones: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.

  • /kind feature
  • /kind enhancement
  • /kind bug
  • /kind packaging
Details

I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.

@mmetc
Copy link
Contributor

mmetc commented May 15, 2024

Should be fixed by #3010

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants