Monitor any command-line script without modifying code
SEER CLI is a command-line tool that wraps your existing scripts and automatically sends execution data to SEER for monitoring. No code changes required - just prefix your commands with seer run.
curl -fsSL https://seer.ansrstudio.com/install.sh | sh
Prefer manual installation? Download binaries directly
Download the latest binary for your platform:
seer --version
SEER CLI needs two environment variables to communicate with SEER:
export SEER_API_KEY="your-api-key-here"
Get your API key from your SEER dashboard settings.
Add these to your ~/.bashrc or ~/.zshrc for persistence:
# Add to ~/.bashrc or ~/.zshrc export SEER_API_KEY="your-api-key-here"
Wrap any command with seer run to monitor it:
seer run "Daily Report" python daily_report.py
seer run "Data Sync" node sync-data.js
seer run "Backup Database" ./backup.sh
seer run "Docker Cleanup" docker system prune -af
Attach custom metadata to your runs for better tracking:
seer run "ETL Pipeline" --metadata '{"environment":"production","version":"2.1.0"}'
python etl.pySEER automatically captures stdout and stderr. Logs are visible in your dashboard.
If SEER API is unreachable, the CLI stores failed reports locally and automatically retries when back online:
# Run even if API is down seer run "Critical Job" python script.py # Later, retry failed reports seer replay-failed
Execute and monitor a command
seer run [OPTIONS] COMMAND [ARGS...] Options: --metadata JSON Add custom metadata --capture-logs BOOLEAN Capture logs from job run --help Show help message
Retry previously failed API reports
seer replay-failed
Show CLI version
seer --version
Monitor scheduled tasks:
# Crontab entry 0 2 * * * /usr/local/bin/seer run "Nightly Backup" /path/to/backup.sh
Track deployment scripts:
# GitHub Actions / GitLab CI
seer run "Deploy Production" \
--metadata '{"commit":"$GITHUB_SHA"}' \
./deploy.shMonitor ETL jobs:
seer run "Daily ETL" \
--metadata '{"source":"warehouse"}' \
python process_data.pyTrack maintenance scripts:
seer run "Log Rotation" \ logrotate /etc/logrotate.conf
If seer command is not found after installation:
# Check if binary is in PATH which seer # Add to PATH if needed export PATH="$HOME/.local/bin:$PATH"
If you see authentication errors:
If reports fail to send:
# Check stored failed reports ls ~/.seer/failed_reports/ # Retry all failed reports seer replay-failed
On Linux/macOS, ensure the binary is executable:
chmod +x /usr/local/bin/seer