check_redfish
check_systemd
| check_redfish | check_systemd | |
|---|---|---|
| 4 | 5 | |
| 109 | 25 | |
| - | - | |
| 6.6 | 9.0 | |
| 2 months ago | 3 days ago | |
| Python | Python | |
| MIT License | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
check_redfish
-
Got a HPE DL380 Gen9 for free - first enterprise server, what do I need to know?
Monitor it: https://github.com/bb-ricardo/check_redfish
- Recommendations on monitoring for HP servers
-
HP Proliant DL380e Gen8 - S.M.A.R.T. and other diagnostics in Proxmox or iLO
If the firmware of iLO4 is recent enough, the RedFish API is supported and you can monitor the hardware health out-of-band without installing anything extra on the operating system. I don't have a DL380e Gen8, but check_redfish works pretty well on any ProLiants with iLO4 or iLO5 I have around.
-
Ideal server rack configuration
If not low on budget, go with the iLO Advanced license (see here page 8). Beside remote power, KVM and remote media can you also perform the hardware monitoring using the RedFish API, we use check_redfish (Icinga2/Nagios compatible check) for that.
check_systemd
-
What to use for application (process) monitoring?
The best all-around check I have found is check_systemd
-
AlmaLinux 9 / network-scripts?
In that case, it may be helpful to have a reliability "spin" sinilar how there are AlmaLinux Live Media images that allow trying an AlmaLinux desktop without installing. That is not an option on the other EL8 systems despite AlmaLinux also offering 1:1 compatibility. A reliability spin might include other reliability-focused components such as monitoring-plugins and check_systemd
-
Linux is dead, long-live Docker monoculture
Fast forward 12 years and I have Icinga2 collectors in each datacenter using check_by_ssh to run check_systemd, all front-ended by Thruk. The TIG stack is something on my list of things to look into at some point, but with Dynatrace available to do all the fancy application monitoring, there's no rush.
-
Anyone using LibreNMS in production?
For alerting for Linux systems, I use Icinga with check_ssh and check_systemd (caveat: distributed primarily on PyPI) with Thruk as the single pane of glass front-end to per-datacenter installations of Icinga.
-
If you wanted to see exactly how a system was performing when a load threshold was reached, how would you do it?
check_systemd is nice to alert based on failed systemd units - https://github.com/Josef-Friedrich/check_systemd but it requires python3 to install, so there is a bit more to install onto a system.
What are some alternatives?
anaconda - System installer for Fedora, RHEL and other distributions
alerta-contrib - Contributed integrations, plugins and custom webhooks
patchman - Patchman is a Linux Patch Status Monitoring System
Zabbix - Real-time monitoring of IT components and services, such as networks, servers, VMs, applications and the cloud.
thola - Tool for monitoring network devices (mainly using SNMP) - monitoring check plugin
Thruk - Thruk is a multibackend monitoring webinterface for Naemon, Nagios, Icinga and Shinken using the Livestatus API.
wacom-gui - Python/PyQt Wacom GUI for KDE
plotly4nagios - Plotly4Nagios is a nagios plugin to display the performance data in Graph. It uses the RRD database provided by pnp4nagios and visualize it in interactive graph format using plotly javascript framework.
subscription-manager - A GUI and CLI client for Candlepin
node_exporter - Exporter for machine metrics
ilo4_unlock - A toolkit for patching HPE's iLO 4 Firmware with access to previously inaccessible utilities
librenms-mibs - A Collection of 3rd party MIBs