Azure Log Alert

[jherrflexion]

Updated the Azure Logs Alert to include more information.

Issue

#1395

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis 🔶 1395 - Partially compliant Fully compliant requirements: Create alert in TI Not compliant requirements: Create alert in SFTP Documentation and diagrams created or updated Code refactored for clarity and no design/technical debt Load tests passed Additional e2e tests created Build process updated API(s) are versioned Feature toggles created and/or deleted

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Query Optimization The query modification in the alert configuration might need further optimization to ensure it captures all necessary error logs efficiently.

[github-actions]

Consider adding a time filter to the query to ensure it only processes recent logs, which can improve performance and relevance of the alert. [important]

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Possible bug	Ensure data types are correctly handled in the bag_unpack function to avoid runtime errors Ensure that the bag_unpack function correctly handles the data types for the level and message fields. If the types are not consistently strings in the source data, consider adding a type check or conversion to avoid runtime errors. operations/template/alert.tf [265] -| evaluate bag_unpack(JsonResult) : (level: string, message: string) +| evaluate bag_unpack(JsonResult) : (level: tostring(level), message: tostring(message)) Suggestion importance[1-10]: 7 Why: The suggestion to ensure correct data type handling in the bag_unpack function is relevant and could prevent potential runtime errors if the data types are not consistent. The suggested code modification explicitly converts the fields to strings, which aligns well with the existing code's requirements and enhances robustness.	7

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[halprin]

Approved, but I want to see this resolve.