Hi,
Thank you all for your answers.
Le 09/04/2016 18:50, Michael Friedrich a écrit :
We discussed writing a config parser for the Icinga 1.x language, just in
Icinga 2. That was iirc in late 2012 or somewhere in 2013. We decided against
it.
Not sure to understand well. What will happen to Icinga 1 ? Will it
continue its development in parallel, or should it disappear sooner or
later ? As far as I understand, you are *now* maintaining two
configuration languages, and two full systems, with Icinga 1 and Icinga 2 !
The future in terms of configuration tools is the Icinga Director, which I have
been eagerly waiting for. If you have some sort of CMDB or $datastorage you can
import your monitoring data from, look into that. Better than any migration
script.
I had a look at it. Seems promising... But isn't this a *third*
configuration system ? ;-)
About my migration plans, I do not really need to keep monitoring
history (It's easier to keep the old Nagios running for history
purposes). What I would like to import is hosts, services, hostgroups
and service groups definitions. Those represent a huge amount of work
over the years...
Though Icinga has a vibrant community and we as developers are active in many
channels.
I know that. Reading your comments, I clearly understood the advantages
of the new structure, and the advantages of re-starting from scratch.
That's what I would do, without any hesitation, in an ideal world ;-)
But I may never have the required time to do that, and I may have to
keep my good old Nagios, which (more or less) does the job...
--
I think I'll have a try to Icinga2 + Director on a new, independant
setup I need for a non-profit (amateur radio) organization. There will
be <20 hosts, and no time/business constraints. This will be done on my
free time. Then, I'll be able to learn more deeply.
Later, I may decide if I choose it or not for migrating my business
system. If so, I think I'll be able to do some scripting for parsing my
old Nagios config files, and import them (or parts of them) in a
"clever" way into Director via the API. This would be more efficient
than using any third-party script, written by an unknown guy, in an
unknown programming language, and not capable of understanding my old
tricks, and what's really important for me.
Thank you again. Kind regards
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users
