NAP WAF: Missing Brute Force log variables in docs
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 94
- Forks
- 174
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 66
Description
Describe the bug
When the Brute Force feature was released in NAP WAF 4.13, some log variables essential to this feature were missed from the documentation.
In summary, the $username and $login_result variables (and their descriptions) are missing from the Available Security Log Attributes section on the v4 security log and v5 security log pages.
To reproduce
N/A
Expected behavior
A clear and concise description of what you expected to happen.
Your environment
- Version/release of this project or specific commit
- Target deployment platform
Additional context
Add any other context about the problem here.
Sensitive Information
Remember to redact any sensitive information such as authentication credentials or license keys.
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
Open content/nap-waf/v4/logging-overview/security-log.md and content/nap-waf/v5/logging-overview/security-log.md, then review their Available Security Log Attributes sections. Add the $username and $login_result variables with their descriptions to both pages; done means the Brute Force log variables are documented consistently in v4 and v5.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100