File monitoring-plugins-tomcat.spec of Package monitoring-plugins-tomcat

Overview Repositories Revisions Requests Users Attributes Meta

File monitoring-plugins-tomcat.spec of Package monitoring-plugins-tomcat

#
# spec file for package monitoring-plugins-tomcat
#
# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#

Name:           monitoring-plugins-tomcat
Version:        1.4
Release:        100
License:        GPL-3.0+
Summary:        Analyse the Tomcat status page
Url:            https://www.monitoringexchange.org/inventory/Check-Plugins/Software/Java/check_tomcat-pl
Group:          Server/Monitoring
Source:         13-03-15_12-09-48_check_tomcat.pl
Source1:        gpl-3.0.txt
Requires:       perl(LWP)
Requires:       perl(LWP::UserAgent)
Requires:       perl(Getopt::Std)
Requires:       perl(XML::XPath)
BuildArch:      noarch
BuildRequires:  nagios-rpm-macros
Provides:       nagios-plugins-tomcat = %{version}-%{release}
Obsoletes:      nagios-plugins-tomcat < %{version}-%{release}
BuildRoot:      %{_tmppath}/%{name}-%{version}-build

%description
This plugin does a HTTP GET of the tomcat status page:

/manager/status?XML=true

It checks the resulting XML for:

* Low free memory
   * Excessive thread usage

Note that although this sounds quite useful, the nature of garbage collection
in Java means that this plugin is prone to 'false positives' when reporting
memory usage. IE: it will complain about low memory, which may be fixed by the
next garbage collection.

I suggest setting the critical threshold for memory quite low - 50 Mbytes or
less.

It is also useful to set the 'max_check_attempts' higher than usual to give
garbage collection time to kick in.

This plugin has proved useful in debugging, by picking up when a problem
started, as distinct from when the tomcat actually failed.

%prep
%setup -q -T -c %{name}
install -m644 %{SOURCE1} LICENSE

%build
#
%install
%{__mkdir} -p %{buildroot}%{nagios_plugindir}
%{__install} -D -m755 %{SOURCE0} %{buildroot}%{nagios_plugindir}/check_tomcat.pl

%files
%defattr(-,root,root)
%doc LICENSE
%dir %{nagios_libdir}
%{nagios_plugindir}/

%changelog

Places

File monitoring-plugins-tomcat.spec of Package monitoring-plugins-tomcat

Places