nDPId/schema
Toni Uhlig aef9d629f0
bump libnDPI to 92507c014626bc542f2ab11c729742802c0bc345
Signed-off-by: Toni Uhlig <matzeton@googlemail.com>
2024-09-09 09:29:08 +02:00
..
daemon_event_schema.json Add PF_RING support. (#38) 2024-08-19 18:33:18 +02:00
error_event_schema.json Moved datalink json key/value from error to packet events and renamed it to pkt_datalink. 2023-04-21 16:48:40 +02:00
flow_event_schema.json bump libnDPI to 92507c014626bc542f2ab11c729742802c0bc345 2024-09-09 09:29:08 +02:00
flow_events_diagram.drawio Improve README 2022-09-19 17:23:11 +02:00
flow_events_diagram.png Improve README 2022-09-19 17:23:11 +02:00
packet_event_schema.json Moved datalink json key/value from error to packet events and renamed it to pkt_datalink. 2023-04-21 16:48:40 +02:00
README.md Replaced ambiguous naming of "JSON string" to more accurate "JSON message". 2023-12-04 13:01:27 +01:00

schema

All schema's placed in here are nDPId exclusive, meaning that they are not necessarily representing a "real-world" JSON message received by e.g. ./example/py-json-stdout. This is due to the fact that libnDPI itself add's some JSON information to the serializer of which we have no control over. IMHO it makes no sense to include stuff here that is part of libnDPI.