RunReveal
SourcesReveald

Troubleshooting

Common issues

Checklist:

  1. Verify your webhook URL is correct and includes the full path
  2. Confirm log files exist and are readable by the reveald process
  3. Check that file extensions match the extension config
  4. Verify no firewall is blocking outbound HTTPS (port 443)
  5. Check reveald logs for errors

Debug steps:

# Enable debug logging
RUNREVEAL_DEBUG=1 reveald run --config config.json
 
# Test with the printer destination to confirm events are being collected

Replace your RunReveal destination with a printer destination to confirm the source is working. If events appear on stdout, the issue is with the destination configuration.

Graceful shutdown

Reveald handles SIGINT and SIGTERM signals gracefully. When stopped, it:

  1. Stops reading from all sources
  2. Flushes remaining buffered events to destinations
  3. Waits up to 30 seconds for the flush to complete
  4. Exits

If you're running reveald under systemd, the default TimeoutStopSec=90s gives plenty of time for graceful shutdown. Avoid setting it below 30 seconds.

Resetting state

To reprocess logs from the beginning, stop reveald and delete the high-watermark files:

rm ~/.config/reveald/watcher-hwm.json    # file source
rm ~/.config/reveald/cri-hwm.json        # CRI source
rm ~/.config/reveald/kawad-journald-hwm  # journald source

Getting help

Previous

Kubernetes

Next

AWS S3 Bucket

On this page