Optional: Monitoring

[khaledhikmat]

• Provide the technical team a way to monitor the system:
  • Perhaps we can build a an Azure Dashboard of resources and app insights (including analytics queries and charts)
• Provide the management team a way to monitor the running business:
  • A PowerBI report against the newly added TripFact table can be built and perhaps embedded into the site and made available to signed-in execs
  • A PowerBI feed to show in real-time incoming triple s. This is really useful at product launch.

Please note that to do item #2 above we need a trial PowerBI account.

[khaledhikmat]

In code, I added 3 telemetry events in the Orchestrators function app:

• Trip created
• Trip monitored
• Trip aborted
• Trip completed

I also added 1 telemetry metric in the Trips function app:

• Active trips

These can be used in Application Insights to provide really useful insight into the application performance.

[khaledhikmat]

Does it make sense to have a single app insights for the entire solution regardless of the Microservice? It could either way. Need to decide on that soon. Right now, each has its own. While probably this is complaint with Microservices, it does add a complexity in querying the different resources.

[khaledhikmat]

Yes...made all function apps use the same app insights resource

[joelhulen]

Absolutely the right choice to only have one App Insights for monitoring. Thanks!