Support JSON output

[moshekaplan]

Support generating JSON output, instead of only text-based.
JSON should (ideally) include:

• Configuration file version
• Date of execution
• Runtime
• Output from each analyzer

[Nawtest]

It would be interesting to add the quantity of analyzed elements to create custom KPIs. Did you have any specific method in mind to accomplish this?

[moshekaplan]

It would be interesting to add the quantity of analyzed elements to create custom KPIs. Did you have any specific method in mind to accomplish this?

Nope, although if I'm understanding correctly, it would seem that those sorts of aggregate queries would best be moved into a separate 'reporting' module, so that reporting (and each report) would be independent of everything else.

[Nawtest]

No, what I want is to extract the totals from the analyzed information so that every person using the tool can utilize them to implement the necessary KPIs. Not calculate the KPIs within the tool itself.

[moshekaplan]

Could you give any examples of what totals you'd want to extract?

[Nawtest]

I was thinking of something like this:

[Nawtest]

And in txt file:

[Nawtest]

I have been modifying the JSON output to be able to exploit the data a bit more, I'll show you an image.

The idea is to add another parameter "--detail" to break down the text info.

[moshekaplan]

Apologies for the delayed response.

I like the idea, but my only concern is that it's not immediately clear what the fractions represent. Especially as some policies or objects are complex enough that a single object could have multiple failures. (e.g., a rule with a non-resolving FQDN can have entries in the source, destination, or both)

[Nawtest]

Don't worry, yes, I understand your concern. For now, I'm handling the simple ones. When I get to those types of rules, I guess I'll have to restructure the detail output. Let's see how it goes...