Logs¶
Manager¶
| Log | Where | Contents |
|---|---|---|
| Alert log | /opt/redpot/manager/logs/alerts.json |
one JSON line per alert (incident at alerts.min_level or higher); for your SIEM |
| Event log (optional) | /opt/redpot/manager/logs/events.json |
one JSON line per event; enable with logs.events |
| Archives | /opt/redpot/manager/logs/alerts-YYYY-MM-DD.json.gz |
rotated daily or at logs.max_mb; the newest logs.keep are kept |
| Console output | sudo docker logs redpot-console-1 |
manager messages: sensor clock skew, wall link use, invalid configuration entries, clock jumps |
| Decoy output | sudo docker logs redpot-<name>-1 |
one container per decoy, lower-case host name (for example redpot-fs01-1) |
| Service | journalctl -u redpot |
start, stop and firewall apply of the redpot unit |
See Alerts, SIEM and export for the record format.
Remote sensor¶
| Log | Where |
|---|---|
| Service | systemctl status redpot-sensor, journalctl -u redpot-sensor |
| Containers | sudo docker ps, then sudo docker logs <container> for the decoy and the relay |
| Undelivered events | /opt/redpot/sensor/data/undelivered-<NAME>.jsonl (written only while the manager is unreachable; never sent later) |
While the manager is unreachable, the relay logs one line at most once a minute per kind of error instead of full tracebacks.
Shipping alerts.json¶
Any file-based shipper works. Point it at /opt/redpot/manager/logs/alerts.json, read it as JSON Lines, and let it
follow rotation. Examples: a Wazuh agent localfile entry with log_format json, a Filebeat filestream input with
the NDJSON parser, or a Splunk Universal Forwarder monitor with a JSON source type.
Enterprise feature: available in ReD-Pot Enterprise
Audit log. Enterprise records every action in the console, through the API and with the installer (who, what, when, from where) and can export it.
About ReD-Pot Enterprise · Compare editions · Contact us for a licence