At this moment. json means a pcap2json output from tshark. For qlog, it needs to have the .qlog extension, for netlog, it has to be .netlog.
Ideally, we'd just ingest a .json and heuristically try to determine what it is (before sending it to the right json parser even)
This kind of thing will be needed either way once we start with qlog's streaming format, so make it a more general approach overall.
At this moment. json means a pcap2json output from tshark. For qlog, it needs to have the .qlog extension, for netlog, it has to be .netlog.
Ideally, we'd just ingest a .json and heuristically try to determine what it is (before sending it to the right json parser even) This kind of thing will be needed either way once we start with qlog's streaming format, so make it a more general approach overall.