goauthentik / goauthentik/authentik
Events logs should be more descriptive
Open
enhancement/confirmed
- Dominant language
- Python
- Stars
- 25.6k
- Forks
- 2k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 659
Description
- The event log for a failed login should specify why it failed to make troubleshooting and reporting easier.
- Model created, updated, and deleted events should specify which kind of model (user, group, application, provider, source etc) was created, updated, and deleted.
Contributor guide
Research direction
No files or tests are named. Start by locating the failed-login event handling and the model lifecycle event generation, then inspect existing event log tests and conventions. Done means failed-login events explain the failure and create, update, and delete events identify the model kind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100