Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
P
picomon
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Service Desk
Milestones
Merge Requests
0
Merge Requests
0
Operations
Operations
Incidents
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
glucas
picomon
Commits
e361b01e
Commit
e361b01e
authored
May 11, 2014
by
Jonathan Michalon
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Added some documentation in README
parent
0b6a3cff
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
16 additions
and
1 deletion
+16
-1
README.md
README.md
+16
-1
No files found.
README.md
View file @
e361b01e
...
...
@@ -11,6 +11,12 @@ Written in Python, it needs at least python 3.2 for the ThreadPools.
On Debian Wheezy the package is
`python3`
.
Some checks are implemented using Nagios' checks,
available under Debian in package
`nagios-plugins-basic`
.
The DNS zone check calls
[
Bortzmeyer's
](
https://github.com/bortzmeyer/check_dns_soa
)
(introduced
[
here
](
http://www.bortzmeyer.org/go-dns-icinga.html
)
).
Usage
-----
...
...
@@ -25,13 +31,22 @@ Usage
Configuration
-------------
Everything can be configured from config.py: base tick, hosts and checks.
Everything can be configured from config.py:
notified email(s),
base tick, hosts and checks.
The
`base_tick`
option defines the base granularity (in seconds) for polling.
`Host`
s are shorthands to avoid repeating addresses within checks.
Checks are then defined as a list of
`Check`
-derived class instances that
implement every single check (see lib/checks.py).
Each check may be initialised with some options:
*
`every`
: run every
`every`
×
`base_tick`
seconds;
*
`retry`
: number of retries before considering a failure (so failure is after
`every`
× (
`retry`
+1) ×
`base_tick`
seconds;
*
`timeout`
: subcommand timeout, to avoid stalling checks (defaults to 2 seconds);
*
`target_name`
: human-readable name of the target of the check (automatically set by the
`name`
option if using
`Host`
instances).
In addition some checks have specific options, see lib/checks.py for examples.
Current state output
--------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment