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!
==Nagios training session Dated 29 Dec 2022 - Tetra Support Staff - Varad== {{#ev:youtube|L8nq4AUFWSQ|640}} '''Video summary:''' "Nagios training session 29 12 2022" -- a dedicated dashboard-navigation training for the Nagios monitoring platform (complementing the shorter Nagios segment in "Training Session OTRS, Wiki & Nagios Monitoring"). Tours the main views: Hosts (every monitored client/server, with up/down status -- demonstrated live with an actually-down server, "IMSS Tribune"), Host Groups and Hostgroup Grid (per-client server groupings with rolled-up OK/warning/critical/pending counts), and the technical overview dashboard showing totals (~758 services monitored, at the time 1 service in a problem state). Explains what specific alerts mean and how each gets resolved: SSL certificate expiry alerts (checked by domain expiry date, e.g. flagging a domain expiring in ~66 days as not yet urgent versus one expiring next month, escalated to L2 engineers, with a reminder to update the client and remove the domain from the watch list once renewed); root-partition/disk-usage warnings (won't clear until the underlying disk space is actually freed, unlike CPU-load or memory-utilization alerts which are typically transient and self-clear); and the difference between alerts requiring action versus those that just need a 15-minute wait-and-refresh cycle to auto-clear (e.g. temporary load spikes). Demonstrates the mail-queue-clearing workflow live for two named servers -- a relay server ("Relay 2") and Hero MotoCorp's mail server -- explaining that persistent mail-queue-count alerts require logging into that specific server and running a queue-flush command (distinct commands per server/context), unlike other alert types. Also covers reading the graph view for a host (total/down/warning counts visualized over time) and reiterates the standing team norm: any alert encountered should be posted/updated in the team's alert-tracking group as part of the response, not just resolved silently.
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)