You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
use wnevtlog input plugin
set read_limit_per_cycle parameter value as 1843200
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.
The text was updated successfully, but these errors were encountered:
Meetp369
changed the title
ff
Warning Log for Maximum Value for threshold in winevtlog input plugin
May 2, 2024
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
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
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.
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
Expected behavior
The text was updated successfully, but these errors were encountered: