Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
In our company we chose both approaches:
- Some data is collected from the server itself (disk, memory usage, hardware, routing)
- Some data is collected from a monitoring server (availability)
- Some data from the surrounding (hypervisors)
- All of it sends it back to the centrals monitoring receiver.
As we - unfortunately for you - wrote our own monitoring software, I cannot give you the software and my knowledge of "available" monitoring software you could use is limited. Thus, I cannot give you more. -
That's what I lack in most monitoribg solutions I come across lately.
In my last workplace we were using Nimbus as a monitoring agent/engine and some IBM event viewer [forgot its title]. The awesome thing in there was heartbeat monitoring. The monitoring server issues a heartbeat request to all the agents and waits for a response. If response is not retrieved witjin preconfigured amount of time - a heartbeat timeout alert is raised in the IBM viewer.
That's what I call a decent, active monitoring. -
Check out Observium, Nagios and Icinga; we use all three to monitor a network of around 7000 devices, few hundred access points, around 150 switches and around 40 servers
(the numbers are not too accurate, I do not have high enough access privileges to our information system to give you exact figures) -
@bytecode Icinga is pretty though.. :)
-
@badcopnodonuts I have no idea why we have all three because I am not the network or server manager... (my guess would be because someone at some time decided to use one and then the person that replaced them liked the second tool more... and so on...) But I do know that the access points and switches are monitored via Nagios, servers are monitored via Icinga and the network as a whole + logs are monitored via Observium... probably
Another dev on my team just got a new machine. Before he came in today I made two separate USB installers and ...
From now on I am administrating multiple servers in our company and monitoring is one thing our infrastucture lacks...almost completely. At least, useful monitoring.
Installing netdata or Grafana and integrate it with chat is definitely a solution, but what happens if the whole server just shuts down (very stupid scenario I know)? Well, it is easy, there will be no alert about the failure.
So, that's where I was wondering if there is a tool or even better plugin for netdata or Grafana, that enables remote monitoring from another server? I surely can write a simple script to check the server availability but having the whole monitoring tool on a single server instead of 5+ would be also easier to maintain and setup.
question
remote
monitoring
netdata
linux
grafana