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

Warning Log for Threshold size in winevtlog input plugin #8783

Closed
Meetp369 opened this issue May 2, 2024 · 2 comments
Closed

Warning Log for Threshold size in winevtlog input plugin #8783

Meetp369 opened this issue May 2, 2024 · 2 comments

Comments

@Meetp369
Copy link
Contributor

Meetp369 commented May 2, 2024

Bug Report

Describe the bug
Even if the highest allowed value (1843200) is set for the read_limit_per_cycle parameter in the configuration file, an unnecessary warning (read limit per cycle cannot exceed) message is still shown without exceeding the maximum threshold size.

To Reproduce

  • Example log :
[2024/04/23 19:33:02] [ warn] [input:winevtlog:winevtlog.0] read limit per cycle cannot exceed 1.8M. Set up to 1.8M
  • Steps to reproduce the problem:
  1. use wnevtlog input plugin
  2. set read_limit_per_cycle parameter value as 1843200
  3. use any output plugin

Expected behavior

  • when the read_limit_per_cycle parameter value set as maximum value(1843200) , the warning log should be skipped.
@Meetp369 Meetp369 changed the title ff Warning Log for Maximum Value for threshold in winevtlog input plugin May 2, 2024
@Meetp369 Meetp369 changed the title Warning Log for Maximum Value for threshold in winevtlog input plugin Warning Log appear even if the highest value is set for the read_limit_per_cycle parameter in winevtlog input plugin. May 2, 2024
@Meetp369 Meetp369 changed the title Warning Log appear even if the highest value is set for the read_limit_per_cycle parameter in winevtlog input plugin. Warning Log for Threshold size in winevtlog input plugin May 2, 2024
Copy link
Contributor

github-actions bot commented Aug 1, 2024

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

@github-actions github-actions bot added the Stale label Aug 1, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 5 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant