Using ORCA report in Azure Automation about orca HOT 5 CLOSED

State view over time would be great, and a table would be the simplest option IMO - If you wanted to go all out it could be a web app (to display results), automation (to schedule the report) and a table to store history - But i'm guessing that would be some massive changes :)

from orca.

Hi @lindonm

Some updates here,

We now support modular outputs, which means a couple of things;

• Out of the box support for outputting now to HTML, JSON, and CosmosDB
• Support for running without displaying the HTML (running Invoke-ORCA -Output HTML -OutputOptions @{HTML=@{DisplayReport=$False}} will run ORCA without displaying the HTML and you'll just get back the path to the outputted HTML as a returned object)
• Support for adding an additional output type - i'll look at including SMTP as an output type

from orca.

Apologies for the formatting, not sure why some lines are massive text

from orca.

thanks @lindonm

Awesome idea! I did have a thought about putting this in to Azure Automation so it could regularly run. It would also be cool if we could develop some 'state' in to it as well, showing settings that have "changed" since the last run - some involvement there with azure table storage, maybe?

but in the mean time, love the idea. will definitely look at making it more 'automatable'.

from orca.

I'm thinking that this is fixed now.. but feel free to re-open if there's further issues with automation.

from orca.