ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Traffic Management: Filter unwanted bot traffic
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the repository's ALB and deployment configuration, then determine how unwanted or bot traffic is identified and restricted before reaching application instances. Done means the ALB filters the targeted traffic and false-positive downtime alerts no longer result from it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100