Folks – I’ve seen this come up before but I don’t see a complete answer anywhere.
What is the ideal architecture going forward? Is it a stand-alone Check_MK installation, or OMD? I’ve noticed that the RPMs and setups install to OMD paths by default.
I had to search around a bit to figure out how to install the Check_MK agent on its own, and it was sufficiently buried within the tar file.
I have an old RedHat 5.5 host with Check_MK and Nagios installed independently. This works great and has tons of data history but is very old. I’d like to upgrade
to a newer RedHat version but it’s not clear to me what I should be doing with my monitoring – should I be moving to OMD? Can I take all of my existing configuration (main.mk, etc.) and move it into OMD somehow? Is there a migration path?
If you don’t want the bleeding edge version of check_mk, i would
say go with OMD.
The rpms make it super easy to install and upgrade check_mk.
···
�s 16:50 de 06-04-2017, Asher Danburg
escreveu:
Folks
� I�ve seen this come up before but I don�t see a complete
answer anywhere.
�
What
is the ideal architecture going forward? Is it a stand-alone
Check_MK installation, or OMD? I�ve noticed that the RPMs
and setups install to OMD paths by default. I had to search
around a bit to figure out how to install the Check_MK agent
on its own, and it was sufficiently buried within the tar
file.
�
I
have an old RedHat 5.5 host with Check_MK and Nagios
installed independently. This works great and has tons of
data history but is very old. I�d like to upgrade to a newer
RedHat version but it�s not clear to me what I should be
doing with my monitoring � should I be moving to OMD? Can I
take all of my existing configuration (main.mk, etc.) and
move it into OMD somehow? Is there a migration path?
�
Thanks,
�
-
Asher
�
_______________________________________________
checkmk-en mailing list
Folks – I’ve seen this come up before but I don’t see a complete answer anywhere.
What is the ideal architecture going forward? Is it a stand-alone Check_MK installation, or OMD? I’ve noticed that the RPMs and setups install to OMD paths by default.
I had to search around a bit to figure out how to install the Check_MK agent on its own, and it was sufficiently buried within the tar file.
I have an old RedHat 5.5 host with Check_MK and Nagios installed independently. This works great and has tons of data history but is very old. I’d like to upgrade
to a newer RedHat version but it’s not clear to me what I should be doing with my monitoring – should I be moving to OMD? Can I take all of my existing configuration (main.mk, etc.) and move it into OMD somehow? Is there a migration path?
Yes and even if; I'm working with OMD AND are installing RPMs from Check_MKs site to keep it fresh. Just download the RPM from their site, install ist locally (with yum I'd say) and do an "omd update" for the site(s)...that's it...
Regards, Maik
···
Am 06.04.2017 um 22:31 schrieb Bruno Miguel Queiros:
If you don't want the bleeding edge version of check_mk, i would say go with OMD.
The rpms make it super easy to install and upgrade check_mk.
Às 16:50 de 06-04-2017, Asher Danburg escreveu:
Folks – I’ve seen this come up before but I don’t see a complete answer anywhere.
What is the ideal architecture going forward? Is it a stand-alone Check_MK installation, or OMD? I’ve noticed that the RPMs and setups install to OMD paths by default. I had to search around a bit to figure out how to install the Check_MK agent on its own, and it was sufficiently buried within the tar file.
I have an old RedHat 5.5 host with Check_MK and Nagios installed independently. This works great and has tons of data history but is very old. I’d like to upgrade to a newer RedHat version but it’s not clear to me what I should be doing with my monitoring – should I be moving to OMD? Can I take all of my existing configuration (main.mk, etc.) and move it into OMD somehow? Is there a migration path?
I had installed OMD Labs edition with prometheus. (with Icinga as core). I thought the metrics from check_mk+icinga would be available in prometheus, but it is not happening. Is there anything special I need to be doing ?
Folks – I’ve seen this come up before but I don’t see a complete answer anywhere.
What is the ideal architecture going forward? Is it a stand-alone Check_MK installation, or OMD? I’ve noticed that the RPMs and setups install to OMD paths by default.
I had to search around a bit to figure out how to install the Check_MK agent on its own, and it was sufficiently buried within the tar file.
I have an old RedHat 5.5 host with Check_MK and Nagios installed independently. This works great and has tons of data history but is very old. I’d like to upgrade
to a newer RedHat version but it’s not clear to me what I should be doing with my monitoring – should I be moving to OMD? Can I take all of my existing configuration (main.mk, etc.) and move it into OMD somehow? Is there a migration path?
Folks – I’ve seen this come up before but I don’t see a complete answer anywhere.
What is the ideal architecture going forward? Is it a stand-alone Check_MK installation, or OMD? I’ve noticed that the RPMs and setups install to OMD paths by default.
I had to search around a bit to figure out how to install the Check_MK agent on its own, and it was sufficiently buried within the tar file.
I have an old RedHat 5.5 host with Check_MK and Nagios installed independently. This works great and has tons of data history but is very old. I’d like to upgrade
to a newer RedHat version but it’s not clear to me what I should be doing with my monitoring – should I be moving to OMD? Can I take all of my existing configuration (main.mk, etc.) and move it into OMD somehow? Is there a migration path?
