monitoring-plugins-check-logfiles 4.1.1-3 source package in Ubuntu
Changelog
monitoring-plugins-check-logfiles (4.1.1-3) unstable; urgency=medium
[ Bas Couwenberg ]
* Team upload.
* Update control file for move to the Nagios team.
* Update copyright syntax.
* Update gbp.conf to use --source-only-changes.
* Update TODO for move to Nagios team.
* Update watch file to handle common issues.
* Bump Standards-Version to 4.6.2, no changes.
* Run test suite provided by upstream author; remove failing tests.
The issues are reported at upstream:
https://github.com/lausser/check_logfiles/issues/73
-- Hilmar Preusse <email address hidden> Fri, 20 Jan 2023 23:18:33 +0100
Upload details
- Uploaded by:
- Debian Nagios Maintainer Group
- Uploaded to:
- Sid
- Original maintainer:
- Debian Nagios Maintainer Group
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Oracular | release | universe | misc | |
| Noble | release | universe | misc | |
| Mantic | release | universe | misc | |
| Lunar | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| monitoring-plugins-check-logfiles_4.1.1-3.dsc | 2.3 KiB | 0ad0af708cc7e7894c9b76397d0cd333d4e5d34545c547de9c4a0ce977d031e0 |
| monitoring-plugins-check-logfiles_4.1.1.orig.tar.gz | 251.1 KiB | ea668c0ac007c50259f11b234fbb9db08d0b93685a0359593713634eaf28c84b |
| monitoring-plugins-check-logfiles_4.1.1-3.debian.tar.xz | 4.0 KiB | 7c324c482471b56e0f4d4b42533fa590297dff9e003575c124bccebae1414479 |
Available diffs
- diff from 4.1.1-2 to 4.1.1-3 (2.7 KiB)
No changes file available.
Binary packages built by this source
- monitoring-plugins-check-logfiles: Nagios plugin check_logfiles
check_logfiles: Plugin for Nagios which scans log files for specific patterns.
Features:
- Detection of rotations - usually nightly logfiles are rotated and
compressed. Each operating system or company has it’s own naming
scheme. If this rotation is done between two runs of check_logfiles
also the rotated archive has to be scanned to avoid gaps. The most
common rotation schemes are predefined but you can describe any
strategy (shortly: where and under which name is a logfile
archived).
- More than one pattern can be defined which again can be classified
as warning patterns and critical patterns.
- Triggered actions - Usually nagios plugins return just an exit code
and a line of text, describing the result of the check. Sometimes,
however, you want to run some code during the scan every time you
got a hit. Check_logfiles lets you call scripts either after every
hit or at the beginning or the end of it’s runtime.
- Exceptions - If a pattern matches, the matched line could be a very
special case which should not be counted as an error. You can
define exception patterns which are more specific versions of your
critical/warning patterns. Such a match would then cancel an alert.
- Thresholds - You can define the number of matching lines which are
necessary to activate an alert.
- Protocol - The matching lines can be written to a protocol file the
name of which will be included in the plugin’s output.
- Macros - Pattern definitions and logfile names may contain macros,
which are resolved at runtime.
- Performance data - The number of lines scanned and the number of
warnings/criticals is output.
- Windows - The plugin works with Unix as well as with Windows
(e.g. with ActiveState Perl).
