Process Viewer

A sysops toolkit for scanning, monitoring, and managing system processes. Record observations, track alerts, run benchmarks, and generate reports — all from the command line with persistent local storage.

Quick Start

CODEBLOCK0

Commands

Core Operations

• - scan <input> — Record a process scan entry (without args: show recent scans)
• INLINECODE1 — Log a monitoring observation (without args: show recent entries)
• INLINECODE2 — Create a report entry (without args: show recent reports)
• INLINECODE3 — Log an alert or warning (without args: show recent alerts)
• INLINECODE4 — Record top-process data (without args: show recent entries)
• INLINECODE5 — Track resource usage (without args: show recent entries)
• INLINECODE6 — Run or log a health check (without args: show recent checks)
• INLINECODE7 — Document a fix applied (without args: show recent fixes)

Maintenance

• - cleanup <input> — Record a cleanup action (without args: show recent cleanups)
• INLINECODE9 — Log a backup operation (without args: show recent backups)
• INLINECODE10 — Log a restore operation (without args: show recent restores)
• INLINECODE11 — Add a general log entry (without args: show recent logs)

Analysis

• - benchmark <input> — Record benchmark results (without args: show recent benchmarks)
• INLINECODE13 — Log comparison data (without args: show recent comparisons)

Utilities

• - stats — Show summary statistics across all entry types
• INLINECODE15 — Export all data (formats: json, csv, txt)
• INLINECODE19 — Search across all log files for a keyword
• INLINECODE20 — Show the 20 most recent activity log entries
• INLINECODE21 — Display health check: version, data dir, entry count, disk usage
• INLINECODE22 — Show available commands
• INLINECODE23 — Print version (v2.0.0)

Each command accepts free-text input. When called without arguments, it displays the most recent 20 entries for that category.

Data Storage

All data is stored as plain-text log files in:

CODEBLOCK1

Each entry is stored as YYYY-MM-DD HH:MM|<input> — one line per record. The history.log file tracks all commands chronologically.

Requirements

• - Bash 4.0+ with INLINECODE26
• Standard Unix utilities: date, wc, du, tail, grep, sed, cat, INLINECODE34
• No external dependencies, no network access required
• Write access to INLINECODE35

When to Use

1. 1. Tracking system processes over time — Use scan and monitor to build a log of process observations for later review or trend analysis
2. Incident response documentation — Use alert to log warnings, fix to document remediation steps, and report to create post-incident summaries
3. Performance benchmarking — Use benchmark and compare to record and contrast performance measurements across different configurations or time periods
4. Backup and recovery auditing — Use backup and restore to maintain an audit trail of data protection operations
5. Periodic system health reviews — Use status for a quick health check, stats for an overview, and export json to archive data for external analysis

Examples

CODEBLOCK2

Configuration

Set PROCESS_VIEWER_DIR environment variable to override the default data directory. Default: INLINECODE49

Output

All commands output to stdout. Redirect to a file with process-viewer <command> > output.txt. Export formats (json, csv, txt) write to the data directory and report the output path and file size.