🔍 Failed Requests - Investigate recent big spike

[jeoffreyfischer]

Description Azure Failed Requests - a spike in was found yesterday (see screenshot). The Operation Name relating to the spike is empty - which doesn't help.

Idea To investigate, use Azure | AppInsight | Failures URL: https://portal.azure.com/#@sswcom.onmicrosoft.com/resource/subscriptions/b8b18dcf-d83b-47e2-9886-00c2e983629e/resourceGroups/ssw.com.au/providers/Microsoft.Insights/components/appInsight-sswwebsite-9eb3/failures

Tasks

• [x] Investigate
• [x] Fix

Screenshot Figure: Spike in Failed Requests

[jeoffreyfischer]

Investigate - ✅ Done

The spike occurred on 6 August 2024 at 3:58pm Sydney local time. I used Azure | AppInsight | Failures and filtered around this specific time. I found the 404 are coming mainly from the following URLs:

• https://www.ssw.com.au/ssw/Standards/*
• https://www.ssw.com.au/ssw/Redirect/*
• https://www.ssw.com.au/SSW/Redirect/*

Screenshot Figure: Example of a 404 URL that happened at the exact time of the spike

[jeoffreyfischer]

Fix - 🏗️ In Progress

Looking at the details of the request - userAgent and HttpReferer - this is very likely a bot (see screenshot). We have a PBI to setup a WAF that should resolve this problem. Link to PBI: https://github.com/SSWConsulting/SSW.Website/issues/2880

Screenshot Figure: