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
Which variant of the Monitoring Plugins do you use?
.rpm/.deb package from repo.linuxfabrik.ch
Compiled for Linux (.tar/.zip from download.linuxfabrik.ch)
Compiled for Windows (from download.linuxfabrik.ch)
Source Code from GitHub
Bug description
The logfile plugin (latest version) uses the filename as a key when checking previous occurrences, however this invalidates the check if for example I need to check two seperate conditions for two seperate instances in time using the same filename.
The ideal solution would be to include the condition or a hash of each condition so that it tracks multiple bookmarks for each condition.
This issue respects the following points:
Which variant of the Monitoring Plugins do you use?
Bug description
The logfile plugin (latest version) uses the filename as a key when checking previous occurrences, however this invalidates the check if for example I need to check two seperate conditions for two seperate instances in time using the same filename.
The ideal solution would be to include the condition or a hash of each condition so that it tracks multiple bookmarks for each condition.
Steps to reproduce - Plugin call
.\logfile.exe --alarm-duration 120 --critical 1 --critical-regex '^(?:(?!Inizio del Processing).)*$' --filename 'C:\Users\test\Desktop\NEW_TEST\pluto.log'
Steps to reproduce - Data
Environment
currently working on windows server 2019 but os is irrelevant.
Plugin Version
logfile: v2023051201 by Linuxfabrik GmbH, Zurich/Switzerland
Python version
No response
List of Python modules
Additional Information
The text was updated successfully, but these errors were encountered: