How docouto/azure-firewall-mon works
Project type and purpose
• This is a single‐page application (SPA) written in Angular that provides a live, “Sysinternals‐Procmon”-style view of Azure Firewall logs without requiring Kusto queries.
• It also includes a Bicep template that provisions the Azure resources needed: Event Hub, Azure Map account, Azure OpenAI service, Application Insights, etc.
File structure
• Top level
– bicep/… .bicep & .json – Infrastructure-as-Code for deploying Azure resources
– firewall-mon-app/… – Angular SPA source code
• firewall-mon-app/src/app/
– Components: login, main-page, yesno-dialog
– Services:
· event-hub-source.service.ts (real-time log ingestion)
· search-field.service.ts & model.service.ts (text filter & ChatGPT mode via Azure OpenAI)
· encryption.service.ts, logging.service.ts, flags.service.ts (misc utilities)
• firewall-mon-app/src/environments – environment.ts for Azure connection strings, keys, endpoints
Extract README insights
• Architecture overview (images/architecture.png) shows:
Azure Firewall → Diagnostic Settings → Event Hub → Angular SPA → Browser
• Steps to provision: Event Hub Namespace/Hub, Azure Map, Azure OpenAI (GPT-4), Diagnostic Settings.
• SPA hosted (e.g.) as an Azure Static Web App or any static host; integrates with Application Insights.