Is your feature request related to a problem?
Currently, bot or unwanted traffic hitting the application can trigger false-positive downtime alerts, even when the application is healthy. This leads to unnecessary alerts and confusion.
Describe the solution you'd like
- Handle and restrict unwanted/bot traffic at the ALB layer instead of the application layer.
- Ensure the ALB identifies and filters bot or unwanted traffic before it reaches application instances.
Original issue
Problem
Currently, when a bot or unwanted traffic hits the application, it can trigger application downtime alerts even though the application itself is healthy and available.
This creates false-positive downtime alerts because the traffic is reaching the application layer instead of being handled before it reaches the application.
Proposed Solution
Handle and restrict unwanted/bot traffic at the ALB layer rather than inside the application.
The ALB should identify and filter/restrict bot or unwanted traffic before it reaches the application instances.
Is your feature request related to a problem?
Currently, bot or unwanted traffic hitting the application can trigger false-positive downtime alerts, even when the application is healthy. This leads to unnecessary alerts and confusion.
Describe the solution you'd like
Original issue
Problem
Currently, when a bot or unwanted traffic hits the application, it can trigger application downtime alerts even though the application itself is healthy and available.
This creates false-positive downtime alerts because the traffic is reaching the application layer instead of being handled before it reaches the application.
Proposed Solution
Handle and restrict unwanted/bot traffic at the ALB layer rather than inside the application.
The ALB should identify and filter/restrict bot or unwanted traffic before it reaches the application instances.