Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
Training 2022 Linux team/
(section)
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Training session on Nagios Training Service team part2 03 March 2024 - Tetra Support Staff - Biswajit Banerjee== {{#ev:youtube|AWJ7wjTe2k4|640}} '''Video summary:''' [PARTIAL TRANSCRIPT QUALITY - frequent dropped words/audio glitches throughout, likely a mic/connection issue on the presenter's end; summary reflects the identifiable topic flow] "Nagios Training Service team part2" -- continues directly from a prior Nagios session (recapping NRPE, NSClient, NCPA, and SNMP as the device-onboarding mechanisms already covered). Goes deeper into application-level and platform-level monitoring: using Nagios's built-in Oracle and MySQL database plugins directly rather than building custom checks; monitoring VMware at both the host and guest VM level. Introduces SNMP traps as a concept distinct from the polling-based checks used so far -- a trap is the monitored device proactively pushing an alert (e.g. "I've crossed 80% utilization") to Nagios rather than Nagios polling for it -- but explicitly recommends against using traps in most environments in favor of standard polling, flagging it mainly as something worth understanding conceptually since it may come up in questions. Walks through Nagios's config file structure directly on the server under `/usr/local`: `commands.cfg` for check-command definitions, and separate host/service definition files, with an explicit warning not to hand-edit certain auto-generated config files. Mentions a config/CRM-style ID system used to identify/relate hosts to specific customers. Given the significant transcript quality issues throughout this recording, finer procedural detail beyond this topic outline could not be reliably captured.
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)