Acknowledging and Snoozing Incidents
Stop repeat notifications by acknowledging an incident from the dashboard, the alert email, Slack or Microsoft Teams, or snooze it for up to 168 hours.
Guides, tutorials, and answers to help you get the most out of Xitoring.
131 articles found
Stop repeat notifications by acknowledging an incident from the dashboard, the alert email, Slack or Microsoft Teams, or snooze it for up to 168 hours.
Track domain registrations with Xitoring: warnings 30, 14, 7 and 1 day before the renewal date, and an alert if a domain lapses or is no longer registered.
Build rotations with layers, overrides, cover requests and holidays, send incidents to whoever is on call, and subscribe to your shifts with an iCal feed.
Send Xitoring incident alerts to Jira Service Management Operations: alerts open when a check goes down and close when it recovers. The way to move off Opsgenie before it shuts down on 5 April 2027.
"Back up my GPG key" sounds like one command, but a working restore actually needs four pieces — the public key, the secret key, the ownertrust database, and a revocation certificate. Miss any one and you end up on a new box with keys that exist but don't decrypt, don't sign, or are flagged "unknown trust." This guide walks the full backup-and-restore loop on Linux, with the exact gpg invocations, the right import order, a worked end-to-end example, and the failure modes that surprise people the first time.
When something goes wrong on a Linux box — a disk drops, a service gets killed, the network card resets, a process segfaults — the kernel almost always wrote the reason into the ring buffer before anything else noticed. `dmesg` is how you read that buffer. This guide covers how to read it well: the right filters, the right time format, what each common message class actually means (OOM killer, block-layer errors, MCEs, USB resets, segfaults), and the workflow for going from "the box is misbehaving" to "this specific line in dmesg is the root cause."
Every Ubuntu Server question that starts with "why is the box slow?" or "what's listening on that port?" ends in the same place — looking at the process table. This guide covers `ps`, `top`, `htop`, `pgrep`, `systemctl`, the `/proc` filesystem, and how to map a noisy process back to the port, file, or service that owns it, with the commands and flags that actually earn their keep on a production server.
Most "the database is slow" problems are not the database — they're a missing index, an N+1 from the ORM, a buffer pool sized for last year's data, or a disk that quietly degraded. This guide walks the layers in the order they actually matter: measure first, fix queries and schema, then configuration, then hardware, then architecture.
CentOS 8 ships chrony as the only NTP daemon in the base repos — the classic `ntp` package is gone. This guide walks through installing chrony, configuring it as a time server for your network, opening firewalld and SELinux correctly, verifying sync, and monitoring drift on CentOS 8, CentOS Stream 8, RHEL 8, Rocky Linux 8, and AlmaLinux 8.
A focused guide to installing `tcpdump` on CentOS 7 and CentOS 8, including the repository fixes both distros now need (CentOS 8 is EOL and points at vault.centos.org; CentOS 7 reached EOL in June 2024), SELinux and firewalld notes, and a smoke-test capture to confirm it actually works.