I as a developer should be able to see what actions the fault injectors have taken and correlate it with telemetry

[KevinDMack]

Right now the Fault injectors record their actions within the output log of the azure function they are running in. The actions of the fault injector should be written out to an external data store where they can be viewed with other application telemetry (such as Application Insights)

[daweins]

Since the Fault Injector is a Function, I'm leaning towards 2 directions

1. We have code already built in to emit telemetry to a Kusto DB. This is great for internal MSFT work, as we can correlate w/ backend Kusto sources, but it's really heavy for community usage
2. If we use a Linux host, we can try the (preview?) Function -> Log Analytics pipeline. We'll just want to add a naming/structure to events as opposed to Informational messages so they can be filtered

Other possibilities:
3) Allow for logging to Event Hub/SQL
4) Leave w/ just AppInsights (great for debugging, poor for integration/graphing)