Alerts, SIEM and export¶
ReD-Pot Community Edition sends nothing out of your network. There is no Telegram, webhook or e-mail alerting.
Alerts stay on the manager: in the console, in the database, and in alerts.json, from where your log shipper takes
them.
Enterprise feature: available in ReD-Pot Enterprise
Outbound alert channels and alert rules.
- Channels: Telegram, e-mail through your own SMTP server, and webhook (with a signing secret).
- Alert rules: a rule builder (by level, decoy, event type or honeytoken), recipient groups, message templates per channel, automatic retry of failed deliveries, a delivery history per alert, a test alert button, and a repeat frequency for conditions that keep firing.
About ReD-Pot Enterprise · Compare editions · Contact us for a licence
alerts.json¶
Every alert (an incident reaching alerts.min_level or above, default L3, or rising to a higher level) is written to
/opt/redpot/manager/logs/alerts.json as JSON Lines: one object per line, like Suricata eve.json. Point Wazuh,
Filebeat, Splunk Universal Forwarder or any log shipper at it.
The file rotates daily, or at logs.max_mb, into alerts-YYYY-MM-DD.json.gz; logs.keep archives are kept.
{"timestamp":"2026-11-09T18:00:10Z","product":"ReD-Pot","company":"Redsidesecurity",
"src_ip":"172.30.50.50","dest_ip":"172.30.50.22","dest_port":80,"proto":"http","level":5,
"alert":{"incident_id":32,"level":5,"level_name":"honeytoken",
"summary":"172.30.50.50 → RS-WEB-01: Honeytoken used on RS-WEB-01/http: web portal admin …",
"path":["RS-FS-01","RS-WEB-01","RS-DC-01"]},
"source":{"ip":"172.30.50.50","label":"172.30.50.50 ACC-PC-07 (REDSIDESECURITY\\anna.k)","internal":true},
"target":{"sensor":"RS-WEB-01","role":"linux-web-hosting","ip":"172.30.50.22","port":80}}
(The example is wrapped for reading; in the file each record is one line.)
Alert records are also stored in the database as the source for export, whether or not alerts.json is enabled.
events.json¶
events.json (off by default) uses the same format for every event, including L1 and L2. Enable it in
rpot.json:
Then run sudo systemctl restart redpot. With "min_level": 4, alerts.json records only compromises and
honeytokens.
Tamper and health alerts¶
- A decoy that stops reporting for more than 2 minutes raises an L4 "sensor offline - possible tampering" alert and
incident (source
decoy <NAME>). The console shows a red banner on every tab until it reports again. - A decoy service that goes down, or a decoy whose connection limits are hit, raises an L4 "possible DoS" alert.
Export¶
Incidents and alert records for a date range, as one JSON file.
Incidents → From / To → Export JSON. Dates are whole UTC days, To included, at most 366 days. Admin sessions only (not wall screens).
sudo ./install.sh export --from 2026-11-01 --to 2026-11-13 # ./redpot-export-2026-11-01_2026-11-13.json
sudo ./install.sh export --from 2026-11-01 --to 2026-11-13 -o /root/nov.json # choose the file
sudo ./install.sh export --from 2026-11-01 --to 2026-11-13 -o /root/nov.json --force # replace an existing file
The file is created with mode 0600 and never overwrites an existing file unless you pass --force; even then only a
regular file is replaced (never a symlink, device or FIFO). Bad dates are refused before anything runs.
The file looks like this:
{"meta": {"product": "ReD-Pot", "edition": "community", "version": "1.0.1", "generated": "…",
"range": {"from": "2026-11-01", "to": "2026-11-13", "start": "…", "end": "…"},
"counts": {"incidents": 31, "alerts": 54}},
"incidents": [{"id": 32, "kind": "attacker", "src_ip": "172.30.50.50", "subject": …, "first_ts": "…", "last_ts": "…",
"level": 5, "level_name": "honeytoken", "title": "…", "status": "open",
"sensors": ["RS-FS-01", "RS-WEB-01"], "count": 41, "note": …}],
"alerts": [{"id": 54, "ts": "…", "incident_id": 32, "level": 5, "record": { …the alerts.json object… }}],
"complete": true}
- The last key,
"complete": true, tells you the file was written to the end. - Incidents are included when they overlap the range. Decoy-health incidents have
"kind": "sensor". - An export larger than 200 MB is refused with the counts; narrow the date range. Only one export runs at a time, and at most 10 per 10 minutes from one address.
Keep exports private
The file contains bait user names and the passwords attackers tried. Treat it like rpot.json.