How jordanbean-msft/az-event-hub-function-logging works
Main Components
a) Azure Services Components:
• Azure Event Hub
• Azure Functions
• Application Insights
• Log Analytics Workspace
• Storage Account
• Managed Identity
b) Infrastructure Management:
• Terraform Configuration Layer
• Azure Policy Management
• RBAC/Security Components
Client/Input Layer
• Event Sources (show incoming data flow)
• Event Hub (primary ingestion point)
Processing Layer
• Azure Functions (Python-based SIEM logging function)
• Connection to fields_to_keep.json configuration
Storage & Monitoring Layer
• Storage Account
• Application Insights
• Log Analytics Workspace
Security & Identity Layer
• Managed Identity
• Policy Enforcement Points
b) Connection Types to Show:
Specific Implementation Details
• Purple hexagons for Event Hub components
• Blue rectangles for Azure Functions
• Orange diamonds for security components
• Yellow rectangles for monitoring components
Important Relationships to Highlight
• Event Hub → Azure Function: Primary data ingestion path
• Azure Function → Storage Account: Data persistence
• Managed Identity → All Components: Authentication flow
• Application Insights → Azure Function: Monitoring
• Policy → All Components: Governance enforcement
Create clear sections for:
a) Infrastructure as Code (Terraform)
b) Runtime Components
c) Monitoring & Logging
d) Security & Compliance
Additional Elements
• Version information for key components
• Environment boundaries (dev/prod if applicable)
• Scaling components