briandiamond
Neophyte
NeophyteRHEL 6
Has anyone successfully set up a collector and monitored RHEL6? RHEL7 and above work without fail, but 6 does not have all the command sets. Other monitoring products can integrate with 6, but I don...
Forum Discussion
briandiamondNeophyte
NeophyteTrying to monitor, I’m told I don’t have access to old agents to deploy on this platform
Joe_Williams
Professor
ProfessorIf you are simply trying to monitor the server, vs installing a collector on it, I would suggest looking into SNMP monitoring. That standard won't change as much if at all compared to SSH based monitoring for Linux.
robert_porebaYup, that would be best in my view too, just use SNMP
- briandiamond
My team states that monitoring with snmp does not give access to process or thread states on rhel6 like it does on rhel7, this is the issue, I need to be able to see Java memory or capacity issues and then restart the process if necessary
- Joe_Williams
Technically, you could get that with SNMP, but I would assume this is beyond your teams skill level currently.
You would need to do SSH based monitoring then. You can add the server into monitoring and provide ssh.user and ssh.pass onto the device without adding it as a collector, you need to pick a collector that can ssh into that specific device.
There might be issues with untrusted cypher suites so you will probably have to open a support ticket on that.
- briandiamond
OK, I checked with the team, the issue is that SNMP, Allows for monitoring RHEL6.. Caveat being when a server is rebooted (or Service is restarted) a New PID is in play and monitoring has to be re-defined. This has been tested and confirmed.
and the SSH option is that the commands are different on 6 for example RHEL6 uses the service command to deal with services, start,stop,restart,status where 7-8-9 uses systemctlexample: service stop snmpd vs systemctl snmpd stop
