Now for most of us we would not know what a Nabaztag is right? (yes!) Well a Nabaztag is a robotic rabbit that interfaces into your WiFi network and can be used for a range of clever things! to explain this rabbit better you can see the introductory clip here
Hans Moser has set up his cleaver little rabbit to announce his Icinga notifications using PHP. Here is a short clip on how he went about it and what this little rabbit is capable of…
You can find the full details on Hans’s blog post here also Hans has expanded further on this to also include Icinga status messages, the details can be viewed here
Currently the Icinga documentation is only available in English & German, we need to expand this to include many other languages. This is where you (the community) can help out! if you are already a translator for another project or would like to get involved in becoming one, then the Icinga Team welcomes you to the challenge…
The Icinga documentation is currently in XML format, a good application for editing the XML files is called XMLmind the personal edition is free to download. Next get yourself a fresh copy of the current documentation from the Icinga git repositories…
git clone git://git.icinga.org/icinga-doc.git
Once you have downloaded this, navigate your way to either the de or en directory and there you will find all the documentation XML files awaiting you!
So if this sounds like a challenge you would like to participate in, then please contact us at info@icinga.org to get your translations included into future releases of Icinga…
Well 2009 has certainly been a very exciting year for the Icinga project, from what started as an idea has become a reality! But this would not have been without your support. What has been achieved in such a short period is due to feedback from you, the user! This is what has shaped the project and made it what it is…
Behind the scenes there is a very dedicated team that has strived to achieve the impossible, and has delivered! with improvements in supporting PostgreSQL & Oracle. Also with current development to a new web UI that will both improve the look and functionality. A lot of work has been done with documentation, currently there is full docs for German & English with work being done on translation to Spanish.
So what will 2010 bring to the Icinga project?
From all of us of the Icinga Team, we wish you a safe and happy new year…
Are you a developer for PostgreSQL? Do you have spare time to dedicate to a good cause? Do you enjoy working in a team environment? Is coding your focus?
Well no, this is not a job offer! but a request for a competent developer who is familiar with the ways of PostgreSQL & C/C++ to either join or can assist with future development of PostgreSQL within Icinga. Now is that an offer you can’t refuse?
So if this looks like something that you would like to contribute to, then please contact Michael Friedrich with your interest …
Recently work has been started on setting up an installer for the new Icinga-web UI. This is currently available via the git repository located at https://git.icinga.org/index (git clone git://git.icinga.org/icinga-web.git to get a fresh branch) then simply follow the instructions in the text file /doc/install-fromscratch.txt this will talk you through the remainder of the process.
Listed below are the configure options…
./configure --help
`configure' configures this package to adapt to many kinds of systems.
Usage: ./configure [OPTION]... [VAR=VALUE]...
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
Defaults for the options are specified in brackets.
Configuration:
-h, --help display this help and exit/
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
-q, --quiet, --silent do not print `checking...' messages
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for `--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or `..']
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
[/usr/local/icinga-web]
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
[PREFIX]
By default, `make install' will install all the files in
`/usr/local/icinga-web/bin', `/usr/local/icinga-web/lib' etc. You can specify
an installation prefix other than `/usr/local/icinga-web' using `--prefix',
for instance `--prefix=$HOME'.
For better control, use the options below.
Fine tuning of the installation directories:
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
--docdir=DIR documentation root [DATAROOTDIR/doc/PACKAGE]
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--with-web-user=<user> sets user name to run icinga
--with-web-group=<group> sets group name to run icinga
--with-bin-user=<user> sets user name for common webfiles
--with-bin-group=<group> sets group for common webfiles
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
LIBS libraries to pass to the linker, e.g. -l<library>
CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
Report bugs to the package provider.
So at this stage the installer is just placing the files and setting the permissions for the Icinga-web UI it is not setting up Apache nor checking the necessary prerequisites this still needs to be done manually.
Please report any bug/issues to the Icinga development team at icinga-devel@lists.sourceforge.net
With recent correspondence from Thomas Spycher of Genotec.ch, He has informed us that they (Genotec.ch) have chosen to utilise Icinga for the monitoring (appropriately 500 hosts!) of their server equipment.
Here are some extracts from a recent Blog from Thomas with his thoughts on Icinga, and how he will be implementing it throughout Genotec.ch
… Icinga still is quite young but my first tests ran extremely stable. The text-based configuration is more complex but provides a lot of possibilities for automated solutions.
… First Tests were very successful and we are thinking about replacing the current productive monitoring system by icinga. Due to the great flexibility, extensions are set up extremely fast.
… That’s why Genotec doesn’t use just sms and e-mail for notification but also Prowl to push notifications directly to iphones. For documentation of outages, internal tracker items for the internal system are automatically generated. There are endless opportunities. It takes 5 minutes to set up notifications via twitter.
… Contact to the developers of Icinga is great! We and Icinga are looking forward to complete the go-live of our instance and to release the first Icinga stable. Furthermore we are confident about the teamwork with Icinga and we are sure Gentotec and Icinga can benefit from it.
… It looks like Gentoc is the first provider who relies on Icinga. I am confident this direction is the right one and I am looking forward to keep you informed about further steps of this project.
Also I have to add, Thomas informed us via twitter, that he had the released 1.0 RC1 up and running within 10 minutes of the release hitting SourceForge!
So thank you Thomas and Genotec.ch for both choosing Icinga for your monitoring solution & for making contact with us. Your feedback is encouraging for the hard working development team who have spent many hours to achieve (what has been a remarkable job in 5 months!) the first Release Candidate of Icinga…
idoutils: fix insert_or_update queries where update violates unique constraint
idoutils: remove and ignore oracle table_prefix (30 chars max)
idoutils: workaround to handle more than 4k Data which may exceed service outputs incl. long perf_data
core init: delete ’su’ usage since all previously su touched files were created by the icinga user
idoutils: fix unescape bug during tabstops
idoutils: fix idomod/icinga segfault while try to use ssl on unix sockets
core configure: set INIT_OPTS depending on detected host OS (no more root:root on FreeBSD?)
idoutils: fix case insensitive comparison in MySQL using BINARY
idoutils: change ido2db.cfg: ndo2db_[user|group] to ido2db_[user|group]
core web: fix missing gif icon copy
Please Note: if you are upgrading from an earlier release, you will need to update the user config in ido2db.cfg from ndo2db_[user|group] to ido2db_[user|group]
As always your feedback is welcome! if you have suggestions or improvements please communicate these via the icinga-devel
mailing list and should you have any trouble with installing/compiling then please use the icinga-users mailing list.
More details to follow soon about the new Icinga-web UI…
Documentation for both German & English is now available from the following link… Icinga-docs Or by selecting the upper menu as indicated in this image…
I always struggle when I get this type of question... "tell me a little about yourself?" I suppose I feel that I don't have a lot to say! or if I was to go into great detail on something I'm working on the person asking has no idea what I'm talking about! So I'll just be a minimalist and say that I'm Married, 33 years of age and a geek! what more do I really need to say?
