logs sniff¶

SSH into a production server and tail a log file in real time.

Usage¶

subscribed logs sniff

Select a server from the list
The CLI fetches available log files from that server's system/logs/ directory
Select a log file
Logs stream live via tail -f
Press Ctrl+C to stop streaming and return to the menu

Servers¶

Key	Site	Bedrock path
`bkse-cloud`	Barberklingen SE	`/home/barberklingen/barberklingen-se-bedrock`
`kddk-cloud`	Kaffedrengen DK	`/home/kaffedrengen/kaffedrengen-dk-bedrock`
`bkdk-cloud`	Barberklingen DK	`/home/barberklingen/barberklingen-dk-bedrock`
`bknl-cloud`	Barberklingen NL	`/home/barberklingen/barberklingen-nl-bedrock`
`elcom-cloud`	Elome DK	`/home/elome/elome-dk-bedrock`

Log files are read from {bedrock-path}/system/logs/.

SSH setup¶

The server keys above are SSH host aliases. They must be configured in your ~/.ssh/config before logs sniff will work.

Example ~/.ssh/config entries:

Host bkse-cloud
  HostName <server-ip-or-hostname>
  User barberklingen
  IdentityFile ~/.ssh/id_ed25519

Host bkdk-cloud
  HostName <server-ip-or-hostname>
  User barberklingen
  IdentityFile ~/.ssh/id_ed25519

Host bknl-cloud
  HostName <server-ip-or-hostname>
  User barberklingen
  IdentityFile ~/.ssh/id_ed25519

Host kddk-cloud
  HostName <server-ip-or-hostname>
  User kaffedrengen
  IdentityFile ~/.ssh/id_ed25519

Host elcom-cloud
  HostName <server-ip-or-hostname>
  User elome
  IdentityFile ~/.ssh/id_ed25519

Verify your SSH access before using the CLI:

ssh bkse-cloud "echo ok"

Troubleshooting¶

No log files found — Your SSH key may lack read access to the system/logs/ directory, or the directory is empty. Verify with ssh <server-key> "ls /path/to/system/logs".

Connection refused / timeout — Check that your SSH config has the correct hostname and that you're on the right network/VPN.