DOCSLIB.ORG

Josh Malone Systems Administrator National Radio Astronomy Observatory Charlottesville, VA

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Josh Malone Systems Administrator National Radio Astronomy Observatory Charlottesville, VA heck What the #%!@ is wrong ^ with my server?!? Josh Malone Systems Administrator National Radio Astronomy Observatory Charlottesville, VA 1 Agenda • Intro to Monitoring • Internet protocols 101 • • Nagios SMTP • IMAP • Install/Config • HTTP • Usage • Custom plugins • Packet sniffing for dummies • Intro to Troubleshooting • Tools • telnet, openssl • grep, sed • ps, lsof, netstat 2 MONITORING 3 Automated Monitoring Workflow 4 Monitoring Packages: Open Source • • Pandora FMS • Opsview Core • Naemon • • • • • • Captialware ServerStatus • Core • Sensu All Trademarks and Logos are property of their respective trademark or copyright holders and are used by permission or fair use for education. Neither the presenter nor the conference organizers are affiliated in any way with any companies mentioned here. 5 Monitoring Packages: Commercial • Nagios XI • Groundwork • PRTG network monitor • CopperEgg • WhatsUp Gold • PRTG network monitor • op5 (Naemon) All Trademarks and Logos are property of their respective trademark or copyright holders and are used by permission or fair use for education. Neither the presenter nor the conference organizers are affiliated in any way with any companies mentioned here. 6 Why Automatic Service Monitoring? • Spot small problems before they become big ones • Learn about outages before your users do • Checklist when restoring from a power outage • Gives you better problem reports than users • Problems you might never spot otherwise • Failed HDDs in RAIDs • Full /var partitions • Logs not rotating • System temperature rising 7 Why Automatic Service Monitoring? • Capacity planning • Performance data can generate graphs of utilization • RAM, Disk, etc. • Availability reports - CAUTION • Easy to generate -- even easier to generate wrong • Make sure your configurations actually catch problems • Will also include problems with Nagios itself :( • If you’re going to quote your availability numbers (SLAs, etc.) make sure you understand what you’re actually monitoring. 8 Without Monitoring With Monitoring ! • dhcp out of leases “The Internet’s down - • dhcp server down fix it!!!” • dns server not responding • ethernet switch down • ISP link down / saturated 9 Without Monitoring With Monitoring ! • connectivity issues “ZOMG! Our web site • web server down is down! O Noes!!!” • apache not running • web server disk full • server load too high 10 Nagios • Open source host / service monitoring package • “Nagios Ain't Gonna Insist On Sainthood” • Originally released in 1999 as “NetSaint” • Available in 2 versions: Core and XI • Nagios Core: Open-source, freely available • Nagios XI: Commercial • Free license for up to 7 hosts • Available as source installer or VMware appliance 11 Terminology • Host - A logical (physical / virtual) machine running an OS • Service - A resource available on a host • Network service (www, dns, imap) • Local resource (free RAM, disk space, system load) • Plugin - An executable that checks something • Add-on - An extension to Nagios that adds functionality • Graphing, Trending, SNMP trap reporting, etc. 12 What’s a plugin? • Plugins actually run the service or host checks. • Each plugin monitors a different type of service • Data from plugin is communicated to Nagios using a (very) simple API • Plugins can also report “Performance Data” (perfdata) to be graphed or tracked • Requires a perfdata add-on (or Nagios XI) • Plugins can be written in any language • Perl plugins can run using Nagios’s embedded perl interpreter for increased performance 13 INSTALLING NAGIOS 14 A word of caution... Installing Nagios on Linux is much easier than Mac. While most Linux distros are still shipping Nagios 3.5.x, they usually come with all the pre-requisite packages available via their native package managers. This makes it much easier to build 4.x from source. Small to medium environments don’t require much of a server to run Nagios. Mac installations will require you to install numerous pre- requisites, especially for the plug-ins. Many of the pre-reqs can be installed using MacPorts, Homebrew and cpan. If you can run on Linux, do it. 15 About Nagios Replacements When Nagios went commercial, the “open-source community” decided that it needed not one, not two, but three replacements for Nagios: Icinga and Naemon (forks of Nagios) and Shinken (a drop-in replacement). Most linux distros are now shipping one or more of these compatible replacements rather than the official Nagios Core. Not a single distro I checked is shipping Nagios 4. Either Shinken, Naemon or Icinga should work fine using the material covered in the tutorial, but I have only briefly tested Icinga and have not tested Shinken or Naemon at all. 16 About Nagios Plugins source • On January 15, 2014, Nagios Enterprises “forked” the original code from the “Nagios plugins” project, effectively creating two sources for the Nagios plugins. • The original maintainers of the plugins package renamed it to “monitoring plugins” and now host their distribution at monitoring-plugins.org • Nagios Enterprises appears to be actively maintaining the nagios-plugins package, including security fixes • This tutorial will use the official Nagios plugins package 17 Requirements • C compiler (Xcode + cmdline tools) • Perl 5.8+ (for many plugins) • Web server (for web interface) • PHP 5.3 • gd (for statusmap and trends CGIs) • rrdtool, perl-RRD, php-GD (for PNP4Nagios) 18 Nagios 4 - brew or build from source • Latest MacPorts version of nagios is 3.5.0 - boo :( • Uses old worker code and not as efficient as 4.x • Latest Homebrew version is 4.0.6 - yay! • brew install nagios! • We want Nagios 4.0.6 at least • fixes lots of bugs and is much faster 19 Create the user and group • Nagios needs a user / group to run as • Create user ‘nagios’ with group ‘nagios’ • Can use System Preferences -- no need to resort to command line 20 Create group ‘nagios’ • Go to Users and Groups, click the + • Change “New Account:” selector to “Group” • Set name to ‘nagios’ 21 Create user nagios • Click + again • Create a “Standard” account • Account name: ‘nagios’ • Set a password for security 22 Create user nagios • Right-click the new ‘nagios’ account and select • Change group to ‘nagios’ • Set shell to /usr/bin/false 23 Download • Nagios Core • http://prdownloads.sourceforge.net/sourceforge/nagios/nagios-4.0.7.tar.gz • Nagios plugins package • http://nagios-plugins.org/downloads/ • PNP4Nagios • http://docs.pnp4nagios.org/pnp-0.6/dwnld 24 Installing Nagios on OSX • Install Xcode and command line tools • Install gd library using MacPorts (or homebrew) • port install gd2! • brew install gd! • cpan! • install Net::SNMP! • Extract the tarball • Configure and install nagios ./configure --with-gd-inc=/opt/local/include \ --with-gd-lib=/opt/local/lib \ --with-httpd-conf=/etc/apache2/other! 25 Compile problems: • ld: archive has no table of contents for architecture x86_64 • Probably a makefile bug • Solution: run ranlib lib/libnagios.a 26 Installation from source sudo -s! make install! make install-config! make install-webconf install-exfoliation! make install-commandmode! install -m 755 -o root -g wheel daemon-init \! /usr/local/nagios/nagios.init! htpasswd -c /usr/local/nagios/etc/htpasswd.users nagios 27 Build and Install Plugins • The plugins have LOTS of prerequisites • LDAP libs • SNMP utils • samba client • openssl libs • Installed most prerequisites via MacPorts • Homebrew should work as well ! ./configure --prefix=/usr/local/nagios \! --enable-perl-modules \! --with-mysql=/opt/local/lib/mysql5 \! --with-openssl=/opt/local/ 28 Install pnp4nagios • Pre-reqs: rrdtool, perl RRD modules, php-GD ! ./configure --with-nagios-user=nagios \! —with-nagios-group=nagios! ! make! # Install without npcd (bulk mode)! make install-config install-processperfdata \! install-html install-plugins 29 Configure pnp4nagios cp /usr/local/pnp4nagios/etc/nagios.cfg-sample \! /usr/local/nagios/etc/pnp4nagios.cfg! cp /usr/local/pnp4nagios/etc/misccommands.cfg-sample \ ! /usr/local/nagios/etc/objects/misccommands.cfg 30 Create LaunchDaemon <?xml version="1.0" encoding="UTF-8"?>! <!DOCTYPE plist PUBLIC -//Apple Computer//DTD PLIST 1.0//EN! http://www.apple.com/DTDs/PropertyList-1.0.dtd >! <plist version="1.0">! <dict>! <key>Label</key>! <string>org.nagios.nagios</string>! <key>ProgramArguments</key>! <array>! <string>/usr/local/nagios/bin/nagios</string>! <string>-d</string>! <string>/usr/local/nagios/etc/nagios.cfg</string>! </array>! <key>KeepAlive</key>! <true/>! </dict>! </plist> 31 Web server / PHP • Enable OSX web server • Set PHP timezone to avoid a warning echo "date.timezone = 'America/New_York'" >>/etc/php.ini 32 CONFIGURING NAGIOS 33 Configuration • Nagios has 2 parts to configure: the daemon and the cgi’s • Configure the CGIs to define access levels (authorization) • Configure the daemon • Commands • Check commands • Misc commands (how to notify, event handlers) • Services • Contacts • Monitoring and alerting policies 34 cgi.conf • Enable authentication in the CGIs • use_authentication=1! • Expects your web server to authenticate users • Only allow admin users to issue commands and view config details • authorized_for_system_information=...! • authorized_for_configuration_information=...! • authorized_for_system_commands=...! • authorized_for_all_service_commands=...! • authorized_for_all_host_commands=...! • Allow any authenticated user to view Nagios status • authorized_for_all_services=*! • authorized_for_all_hosts=* 35 nagios.cfg • Main configuration file • Typically includes additional cfg files for commands, services, etc.
Load more

Recommended publications
  • Naemonbox Manual Documentation Release 0.0.7
    NaemonBox Manual Documentation Release 0.0.7 NaemonBox Team September 16, 2016 Contents 1 Introduction 3 1.1 Target audience..............................................3 1.2 Prerequisite................................................3 2 About Naemonbox 5 2.1 Project..................................................5 2.2 Features..................................................6 3 Installation Guide 7 3.1 System requirements...........................................7 3.2 Recommended system requirements...................................7 3.3 Client Operating Systems........................................7 3.4 Openvz VPS installation.........................................8 3.5 GNU/Linux Debian 7 (or later) Installation...............................8 3.6 Installing Naemonbox..........................................8 4 Getting Started 9 4.1 Step one.................................................9 4.2 Step two................................................. 10 4.3 Step three................................................. 10 4.4 Step four................................................. 10 5 Configuring Naemon 11 5.1 Introduction............................................... 11 5.2 Actions.................................................. 11 5.3 Hosts Definition............................................. 12 5.4 Services.................................................. 13 5.5 Commands................................................ 14 5.6 Time periods............................................... 15 5.7 Contacts................................................
    [Show full text]
  • Monitoring Bareos with Icinga 2 Version: 1.0
    Monitoring Bareos with Icinga 2 Version: 1.0 We love Open Source 1 © NETWAYS Table of Contents 1 Environment 2 Introduction 3 Host 4 Active Checks 5 Passive Events 6 Graphite 2 © NETWAYS 1 Environment 3 © NETWAYS Pre-installed Software Bareos Bareos Database (PostgreSQL) Bareos WebUI Icinga 2 IDO (MariaDB) Icinga Web 2 Graphite 4 © NETWAYS 2 Introduction 5 © NETWAYS 2.1 Bareos 6 © NETWAYS What is Bareos? Backup Archiving Recovery Open Sourced Backup, archiving and recovery of current operating systems Open Source Fork of Bacula (http://bacula.org) Forked 2010 (http://bareos.org) AGPL v3 License (https://github.com/bareos/bareos) A lot of new features: LTO Hardware encryption Bandwidth limitation Cloud storage connection New console commands Many more 7 © NETWAYS Bareos Structure 8 © NETWAYS 2.2 Icinga 2 9 © NETWAYS Icinga - Open Source Enterprise Monitoring Icinga is a scalable and extensible monitoring system which checks the availability of your resources, notifies users of outages and provides extensive BI data. International community project Everything developed by the Icinga Project is Open Source Originally forked from Nagios in 2009 Independent version Icinga 2 since 2014 10 © NETWAYS Icinga - Availability Monitoring Monitors everything Gathering status Collect performance data Notifies using any channel Considers dependencies Handles events Checks and forwards logs Deals with performance data Provides SLA data 11 © NETWAYS What is Icinga 2? Core based on C++ and Boost Supports all major *NIX and Windows platforms Powerful configuration
    [Show full text]
  • Pynag Documentation Release 0.9.0
    pynag Documentation Release 0.9.0 Pall Sigurdsson and Tomas Edwardsson July 23, 2014 Contents 1 Introduction 3 1.1 About pynag...............................................3 2 The pynag module 5 2.1 pynag Package.............................................5 2.2 Subpackages...............................................5 3 The pynag command line 85 3.1 NAME.................................................. 85 Python Module Index 89 i ii pynag Documentation, Release 0.9.0 Release 0.9.0 Date July 23, 2014 This document is under a Creative Commons Attribution - Non-Commercial - Share Alike 2.5 license. Contents 1 pynag Documentation, Release 0.9.0 2 Contents CHAPTER 1 Introduction 1.1 About pynag Pynag is a all around python interface to Nagios and bretheren (Icinga, Naemon and Shinken) as well as providing a command line interface to them for managing them. 3 pynag Documentation, Release 0.9.0 4 Chapter 1. Introduction CHAPTER 2 The pynag module 2.1 pynag Package 2.2 Subpackages 2.2.1 Control Package Control Package The Control module includes classes to control the Nagios service and the Command submodule wraps Nagios com- mands. class pynag.Control.daemon(nagios_bin=’/usr/bin/nagios’, nagios_cfg=’/etc/nagios/nagios.cfg’, na- gios_init=None, sudo=True, shell=None, service_name=’nagios’, na- gios_config=None) Bases: object Control the nagios daemon through python >>> from pynag.Control import daemon >>> >>> d= daemon() >>> d.restart() SYSTEMD = 3 SYSV_INIT_SCRIPT = 1 SYSV_INIT_SERVICE = 2 reload() Reloads Nagios. Returns Return code of the reload command ran by pynag.Utils.runCommand() Return type int restart() Restarts Nagios via it’s init script. Returns Return code of the restart command ran by pynag.Utils.runCommand() Return type int 5 pynag Documentation, Release 0.9.0 running() Checks if the daemon is running Returns Whether or not the daemon is running Return type bool start() Start the Nagios service.
    [Show full text]
  • Azure Icinga 2.5 - Client Connection Guide Scope
    Azure Icinga 2.5 - Client Connection Guide Scope The purpose of this document is to provide the steps necessary for connecting a client instance of Icinga 2, version 2.5 or later, to a master node. The steps contained within are sourced from the official Icinga 2 documentation in Section 6, "Distributed Monitoring with Master, Satellites, and Clients" This version of the documentation has been adapted to match the necessary upgrade steps for an instance of the Shadow-Soft Marketplace VHD image. Distributed Monitoring Your Shadow-Soft Marketplace VHD image for Icinga 2 is already configured with a "Master" node. If you have a second Icinga 2 node that you would like to have as a part of your monitoring environment, you can connect the two Icinga 2 daemons together securely using the included icinga2 node wizard commands. This creates an SSL-authenticated tunnel between the daemons over port 5665. This connection will allow configuration to be distributed outward to the satellite, and allow local checks on the satellite node to be executed, then communicated upstream to the master. A master node has no parent node A master node is where you usually install Icinga Web 2. A master node can combine executed checks from child nodes into backends and notifications. A satellite node has a parent node, and may have a child node. A satellite node may execute checks on its own or delegate check execution to child nodes. A satellite node can receive configuration for hosts/services, etc. from the parent node. A satellite node continues to run even if the master node is temporarily unavailable.
    [Show full text]
  • Supervision Utilisation De Check-MK
    Supervision Utilisation de Check-MK Réseau Min2Rien Journée Thématique « retour d’expériences » - 13/02/2014 NICOLAS JAMIN – Administrateur Système – DSI de l’Académie de LILLE Supervision: Utilisation de Check-MK Plan . Présentation . Fonctionnement / Configuration . Création de scripts (Présentation et exemple) . Utilisation / Capture d’écran . Livestatus / Multisite Nicolas JAMIN – DSI de l’Académie de LILLE 14/02/2014 2 Supervision: Utilisation de Check-MK Presentation . Check-MK : add-on de supervision écrit en python . Nagios utilise des plugins de type actif 1 plugin = 1 service Exécution côté Nagios • Exemple: check_disk = test de l’espace disque . Check-MK utilise des plugins de type passif 1 plugin ~ 30 tests de base Exécution côté Client • Exemple: check_mk = check_disk + check_mem + check_ps + … . Forte baisse du taux d’utilisation des CPUs sur Nagios grâce à Check-MK . Remplace les plugins de type NRPE, NSCLIENT ++ Nicolas JAMIN – DSI de l’Académie de LILLE 14/02/2014 3 Supervision: Utilisation de Check-MK Fonctionnement Nicolas JAMIN – DSI de l’Académie de LILLE 14/02/2014 4 Supervision: Utilisation de Check-MK Configuration (sur le serveur NAGIOS) . Fichier main.mk Contient la configuration générale (seuil d’alerte, exclusions des services …) • Inventory_df_exclude_mountpoints = [‘/dev’,’/mnt/vzsnap0’] • Filesystem_default_level[‘levels’] = (90.0, 95.0) . Fichier tcp_hosts.mk Contient les hosts et hostgroups des serveurs auxquels ils appartiennent. • template124.expr.in.ac-lille.fr|linux|apt|openvz|ubuntu12 . Fichier hostgroups.mk Contient la définition des hostgroups. • (‘Serveurs Ubuntu 12.04’, [ ‘ubuntu12’ ], ALL_HOSTS), Nicolas JAMIN – DSI de l’Académie de LILLE 14/02/2014 5 Supervision: Utilisation de Check-MK Configuration (sur le serveur NAGIOS) . Plus aucune configuration côté Nagios Core • /etc/nagios/host.cfg, /etc/nagios/hostgroup.cfg … .
    [Show full text]
  • Network Monitoring Using Nagios and Autoconfiguration for Cyber Defense Competitions
    NETWORK MONITORING USING NAGIOS AND AUTOCONFIGURATION FOR CYBER DEFENSE COMPETITIONS Jaipaul Vasireddy B.Tech, A.I.E.T, Jawaharlal Nehru Technological University, India, 2006 PROJECT Submitted in partial satisfaction of the requirements for the degree of MASTER OF SCIENCE in COMPUTER SCIENCE at CALIFORNIA STATE UNIVERSITY, SACRAMENTO FALL 2009 NETWORK MONITORING USING NAGIOS AND AUTOCONFIGURATION FOR CYBER DEFENSE COMPETITIONS A Project by Jaipaul Vasireddy Approved by: __________________________________, Committee Chair Dr. Isaac Ghansah __________________________________, Second Reader Prof. Richard Smith __________________________ Date ii Student: Jaipaul Vasireddy I certify that this student has met the requirements for format contained in the University format manual, and that this Project is suitable for shelving in the Library and credit is to be awarded for the Project. __________________________, Graduate Coordinator ________________ Dr. Cui Zhang Date Department of Computer Science iii Abstract of NETWORK MONITORING USING NAGIOS AND AUTOCONFIGURATION FOR CYBER DEFENSE COMPETITIONS by Jaipaul Vasireddy The goal of the project is to monitor the services running on the CCDC (College Cyber Defense Competition) network, using Nagios which uses plugins to monitor the services running on a network. Nagios is configured by building configuration files for each machine which is usually done to monitor small number of systems. The configuration of Nagios can also be automated by using shell scripting which is generally done in an industry, where the numbers of systems to be monitored are large. Both the above methods of configuration have been implemented in this project. The project has been successfully used to know the status of each service running on the defending team’s network.
    [Show full text]
  • Performance Monitoring Using Nagios Core Hpc4e-Comcidis Vin´Icius P
    Performance Monitoring Using Nagios Core HPC4e-ComCiDis Vin´ıcius P. Kl^oh Mariza Ferro Gabrieli D. Silva Bruno Schulze LNCC { Petr´opolis,RJ Abstract The High Performance Computing for Energy (HPC4e) project aims to apply\new exascale HPC techniques to energy industry simulations, customizing them if necessary, and going beyond the state-of-the-art in the required HPC exascale simulations for different energy sources that are the present and the future of energy like, wind energy production and design, efficient combustion systems for biomass-derived fuels (biogas), and exploration geophysics for hydrocarbon reservoirs". Beyond the general objective, there are specific technical objectives that will be developed to enhance the final results. Our objective is study the mapping and optimization of the codes proposed for simulations in energy domain (atmosphere, biomass and geophysics for energy), analysing all the aspects related with the performance of these simulations' codes. Trying to meet all these objectives, we are investigating performance tools that would help our research. We investigated at first tools that enable online measurement of performance (online approaches are without code instrumentation). More specifically, in this work we present our initial work with Nagios and the hard begin to put this performance tool on work. In this work we present the steps and instructions, on how to install and configure Nagios Core to enhance it monitoring your local and remote host. July 2016 Contents 1 Introduction 2 2 Nagios Core 3 3 Install and Configure Nagios Core and Basic Plugins 4 4 Plugins 6 4.1 Install and Configure NRPE (Nagios Remote Plugin Executor) .
    [Show full text]
  • Pandora FMS: User Administration Guide
    Pandora FMS 1.3.1 User Guide to Pandora FMS Administration Pandora FMS 1.3.1 User documentation April, 2008 Page 1 of 135 Pandora FMS 1.3.1 User Guide to Pandora FMS Administration Index 1 . Introduction to Pandora FMS ..................................................................................... 6 1.1. What is Pandora FMS? .............................................................................................. 6 1.2. What else can Pandora FMS do? ............................................................................... 6 1.2.1. Using agents ......................................................................................................7 1.3. Pandora FMS Architecture ........................................................................................ 9 1.4. Pandora FMS Agents................................................................................................ 10 1.4.1. Satellite Agents ............................................................................................... 12 1.4.2. XML data file ..................................................................................................12 1.5. Pandora FMS Servers............................................................................................... 14 1.6. Pandora FMS console...............................................................................................15 1.7. Database....................................................................................................................15 1.7.1. Compacting data ...........................................................................................
    [Show full text]
  • 1.3 SNMP Traps
    PANDORA FMS NETWORK DEVICE MONITORING NETWORK DEVICE MONITORING PANDORA FMS pag. 2 INTRODUCTION 1. SNMP This document aims to explain how Pandora FMS is When we talk about SNMP Monitoring, the most able to monitor all network devices available on the important thing is to separate two concepts: Tests marke such as Routers, Switches, Modems, Access (polling) and Traps. points, etc. SNMP testing involves ordering Pandora FMS to execute a snmpget command to the SNMP device Pandora FMS can measure your network bandwidth such as a router or a switch or even a computer by consulting your router/switch through SNMP or with a SNMP agent installed. This is a synchronous by processing the network statistics sent by your operation (every X seconds). routers. Getting the correct information about the bandwidth and the consumption of the network In the opposite, receiving a SNMP trap is an asyn- devices is crucial to achieve a better network ma- chronous operation, that could happen or not, nagement. usually applied to get alerts coming from the device like, for example, when your switch drops a connec- These are some of the main things that Pandora tion with a port, or when your device gets too hot. FMS can do with your network: * Avoid bottlenecks in the network bandwidth and Pandora FMS works with SNMP using individual the server. OID’s. To Pandora FMS, each OID is a network mo- * Localize what applications and which servers are dule. So, if you want to monitor a 24 port Cisco Ca- consuming your bandwidth. talyst Switch, and be aware of the operative status * Provide better quality services to the users by of each port as well as the incoming and outgoing being proactive.
    [Show full text]
  • Peter Helin, ABB Crane Systems Stefan Löfgren, Mälardalen
    Fredrik Linder [email protected] Thesis for the Degree of Bachelor of Science in Engineering - Computer Network Engineering 15.0 hp IDT (academy for Innovation, Design and Technology) Mälardalen University Västerås, Sweden 2015-11-15 Supervisors: Peter Helin, ABB crane systems Stefan Löfgren, Mälardalen University Examinator: Mats Björkman, Mälardalen University | Network monitoring of automated harbor terminals | | Linder | ABSTRACT Nowadays, more information and services are migrated into computers using a network as the carrier for data communication. One example of this is the migration from PROFIBUS to PROFINET. The big problem is that there are no network monitoring solution implemented, despite the significance of the network. The drawback of not having a network monitor solution are many. This includes areas within security, availability, control and troubleshooting. The goal is to find a solution to this problem with providing a complete network monitor solution in ABB’s existing environment. The work was divided in four different parts, research, design, implementation and verification. Information from the World Wide Web (WWW) pointed towards that CentOS (operating system) together with OMD (network monitor software) would be the best choice for this task. The design phase described how all devices should be able to communicate with each other. The implementation part mostly were configuration of devices, such as servers, monitor software, switches and security. The configuration were made by using the built in user interface in each device. The verification part proved that all functions worked as expected, such as security and notifications. Rest of the verification could be seen in the web interface. The result is a complete solution demonstrated in ABB crane system’s lab, which includes a complete set of network devices that exist on sites all around the world.
    [Show full text]
  • Red Hat Ceph Storage 4 Monitoring Ceph with Nagios Guide
    Red Hat Ceph Storage 4 Monitoring Ceph with Nagios Guide Monitoring Ceph with Nagios Core. Last Updated: 2021-09-14 Red Hat Ceph Storage 4 Monitoring Ceph with Nagios Guide Monitoring Ceph with Nagios Core. Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
    [Show full text]
  • Ausreißer Check Mk
    05/2014 Check_mk als Nagios-Alternative Titelthema Ausreißer Check_mk 34 Check_mk hat zurzeit Rückenwind: Es gilt nicht mehr als schnödes Nagios-Plugin und seine Oberfläche Multi- site lässt die Konkurrenz alt aussehen. Doch wird Check_mk diesem Ruf in der Praxis gerecht? Holger Gantikow www.linux-magazin.de wachen will und wie er alle Ergebnisse in einem Rutsch zurück. dies möglichst optimal Das erfordert nur eine einzige Verbin- mittels Hostgruppen und dung (Abbildung 1, rechts). Templates abbildet, da- Auch Nagios wertet anders aus: Mit dem mit seine Konfiguration Nagios Remote Plugin Executor (NRPE) wartbar bleibt. Zugleich stupst es in der Regel ein Plugin auf dem wächst aber die Last auf Host an, das etwa die RAM-Auslastung dem Nagios-Server mit je- misst. Das Plugin erhält einige Schwel- der Erweiterung: Je mehr lenwerte und liefert einen Status zurück Dienste und Hosts dieser (»OK«, »Warning«, »Critical«). überwacht, desto mehr Check_mk bewertet die Ergebnisse hin- wird die Serverhardware gegen erst auf dem Server. Dies hat den zum Engpass. Die Anzahl positiven Nebeneffekt, dass die Agents der „aktiven Checks“ pro auf den zu überwachenden Hosts keine Prüfintervall bestimmt, weitere Konfiguration benötigen. Der wie leistungsfähig der Check_mk-Server filtert die von den Server sein muss (Abbil- Agenten gelieferten Daten mit Hilfe der © Ljupco Smokovski, 123RF Smokovski, © Ljupco dung 1, links). Konfigurationsparameter und Schwellen- werte, die der Admin festgelegt hat, und Wer den Zustand von mehr als einer Check_mk am Start schickt die Ergebnisse an Nagios weiter. Handvoll Systeme im Blick behalten möchte, muss auf handgestrickte Shell- Speziell gegen diese beiden Probleme, Testlauf skripte oder gelegentliche Kontrollen gegen die komplexe Konfiguration und verzichten und braucht ein vollwertiges die hohe Serverlast, möchte Check_mk Ob Check_mk hält, was es verspricht, Monitoring.
    [Show full text]