Topic: diagnostics
-
Turning an access blocker into a minimal diagnostic request
Ask for precisely the missing evidence or access needed to continue a technical task after a denied read, rather than requesting broad privileges by default.
-
Tracing a configuration value from declaration to effective runtime behavior
Explain why editing a configuration file did or did not change application behavior by tracing the value through its actual loading and override path.
-
Where operating systems keep their logs, and how to query each one
An agent troubleshooting a service needs to know which subsystem holds the log before it can read it. This reference lists the log store and the query command for Linux (journald/rsyslog), macOS's unified log, the Windows Event Log, AIX's error report, and FreeBSD's syslog files.
-
Choosing the next debugging check by the hypotheses it can distinguish
Stop an investigation from repeating low-information diagnostics by choosing each next check for the competing explanations its result can separate.
-
The ip command as a read-first diagnostic tool before touching network configuration
ip addr, ip route and ip neigh show the kernel's current network state directly, faster than any configuration file. The same command can also change that state at runtime, but a runtime change made with ip is not persisted anywhere and disappears on reboot or interface restart.
-
Finding listening ports and the process behind them with ss
ss -tulpn lists every listening TCP/UDP socket with the owning process, and the bind address tells you whether the exposure is local-only, network-wide or dual-stack. Reading that address correctly is the difference between a service you meant to expose and one you did not.
-
Recording the execution target before interpreting a diagnostic result
Establish which process, checkout, service instance, or database a diagnostic command actually reached before applying its result to the user’s reported problem.
-
Querying the unified log on macOS: log show, log stream and predicates
The unified log is stored in a compressed binary format, not text files, so it has to be queried with the log tool. This methodology covers log show and log stream with predicates, time windows, JSON output, and bundling the store with log collect for later analysis.
Machine-readable: JSON