Gymlog

Gymlog v2.0.0 — a sysops toolkit for logging and tracking operations from the command line.

Commands

Data Storage

All data is stored locally in ~/.local/share/gymlog/. Each command writes timestamped entries to its own .log file (e.g., scan.log, monitor.log, backup.log). A unified history.log tracks all operations for the recent command.

Log format per entry: YYYY-MM-DD HH:MM|<input>

Requirements

• Bash (with set -euo pipefail)
• No external dependencies — uses only standard coreutils (date, wc, du, tail, grep, cat, sed)

When to Use

• To log and track sysops operations over time
• To maintain a searchable history of scan/monitor/alert/check tasks
• To track backup/restore operations and cleanup tasks
• To export accumulated data in JSON, CSV, or plain text for reporting
• To get a quick health check on your gymlog data directory
• For benchmarking and comparing system performance metrics

Examples

# Log a scan entry
gymlog scan "full port scan on 192.168.1.0/24"

# Log a monitor entry
gymlog monitor "CPU usage 85% on web-server-01"

# Log an alert entry
gymlog alert "disk space below 10% on /dev/sda1"

# Log a backup entry
gymlog backup "nightly backup of /var/data completed"

# Log a benchmark entry
gymlog benchmark "disk I/O test: 450MB/s sequential read"

# View recent check entries
gymlog check

# Search all logs for a term
gymlog search "disk"

# Export everything as CSV
gymlog export csv

# View aggregate statistics
gymlog stats

# Health check
gymlog status

# Show last 20 history entries
gymlog recent

# Log a cleanup operation
gymlog cleanup "removed 2.3GB of old log files"

# Log a restore operation
gymlog restore "restored database from 2024-01-15 snapshot"

Configuration

Set the GYMLOG_DIR environment variable to override the default data directory. Default: ~/.local/share/gymlog/

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com