Alternative to nagios / local monitoring for linux server and windows
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Alternative to nagios / local monitoring for linux server and windows
Hi,
I have 2 nagios server :
- one on network A
- one on the network I
and I monitore some servers (linux and windows server) running on network A from nagios on network I.
For political reason, I must shutdown the nagios server running on network A :-(
I also want to stop the monitoring of servers running on network A from nagios on network I, but I want to keep an monitoring (disk, services/process, cpu, ...) so I'm looking for a tools running on console (no web interface) where I can setup monitoring and alertes (email) on each server. A free tools, of course.
Explain please the "political reason".
If the "political reason" is an objection to the monitoring or network traffic to accomplish monitoring an alternate solution of the same time will not suffice. IF it is a rejection of NAGIOS on that network, why not just install ZABBIX on that server and retire NAGIOS there?
IF you just want general suggestions, and search at swisscows, duckduckgo, google, or bing will return MANY articles about NAGIOS alternatives!
I have 2 nagios server :
- one on network A
- one on the network I
and I monitore some servers (linux and windows server) running on network A from nagios on network I. For political reason, I must shutdown the nagios server running on network A :-(
I also want to stop the monitoring of servers running on network A from nagios on network I, but I want to keep an monitoring (disk, services/process, cpu, ...) so I'm looking for a tools running on console (no web interface) where I can setup monitoring and alertes (email) on each server. A free tools, of course.
The best suggestion would be to tell whoever is making this 'political reason' surface to explain it to you, and get THEM to tell you what to use. You can't both have monitoring and NOT have monitoring at the same time.
If you're in charge of the servers, then you choose the tools. If you have SNMP on the servers, write a script to poll various things...that's free, and can do whatever alerting you want.
I'm not the manager of the network A, my company is member of a group that you Centreon for monitoring server on all subsidary.
The local manager of my company prefer the groups's monitoring system than my nagios monitoring but in my point of view, the time reaction (from the group) and the information circuit as not the same. With nagios I can pilote alerte system, not with Centreon.
Last edited by cormanstnl; 11-26-2023 at 01:07 PM.
The nagios on network A monitoring some AP and some other devices, my nagios on network I monitoring switch and servers on network I and some servers (production server) on network A.
I just want to discretly continue to monitoring them and in same time close nagios/cacti traffic between both network by modify the firewall between networks
In fact, I want something like a standalone NCPA, a local service who make some check (cpu, memory, process) and send alertes if neede, no web GUI, a CLI is OK.
For my servers on network A, nagios keep running on network I
Knowing the better answer is one thing. Deciding it is worth risking your companies reputation AND YOUR JOB to keep using the solution the client objects to is a whole 'nother thing!
The ethical thing is to give the good advice, and DOCUMENT that you gave the good advice (so the results of doing something different does not come back to get dropped on you!) and then do it the way the client demands. IT is not your network!
The client is not only not always right, they are OFTEN wrong. IT IS our business to correct and advise, but NOT our business to make their decisions for them.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.