log4j-finder
log4j-finder copied to clipboard
feature: Added text, csv, json_event, json output capability
Added output formats:
- text
- json
- csv
- json_even
this will implementing the script into some monitoring platform (mostly based on powershell) a whole lot easier.
I like adding csv and json support. However this change doesn’t output the results as they are found anymore, so you have to wait until it finishes the scan.
I know streaming json output could be difficult unless it’s jsonlines. Would powershell support that or does that prefer a single json output?
so you have to wait until it finishes the scan. This is OK to me, having csv output is useful and need comprise. this new enhancement should have its own argument.
I like adding csv and json support. However this change doesn’t output the results as they are found anymore, so you have to wait until it finishes the scan.
I know streaming json output could be difficult unless it’s jsonlines. Would powershell support that or does that prefer a single json output?
In case of JSON events your system should be capable to process SerDe(https://docs.aws.amazon.com/athena/latest/ug/json-serde.html). I think that's a good idea to stream JSON events(SerDe), CSV and text. Regular JSON probably requires a scan process to finish first.
I like adding csv and json support. However this change doesn’t output the results as they are found anymore, so you have to wait until it finishes the scan.
I know streaming json output could be difficult unless it’s jsonlines. Would powershell support that or does that prefer a single json output?
I added sync output for text, csv and json_event(SerDe). JSON output returns in the end of scan. It should at any environment(linux, windows, mac) because it doesn't have any specific execution aspects.
@yunzheng did you have a chance to review this?