Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New report for Failed Authentication and menu organization #223

Open
toddocon opened this issue Dec 17, 2020 · 2 comments
Open

New report for Failed Authentication and menu organization #223

toddocon opened this issue Dec 17, 2020 · 2 comments

Comments

@toddocon
Copy link
Contributor

I have a new report for 'Failed Authentication' similar to 'Failed Webhooks'. Looking at failed authentication attempts across the system is helpful in spotting misconfigured systems that may be tying up authentication workers. I often see this issue when someone changes their credentials but neglects to update stored credentials in their CI/CD systems which in turn causes lots of failed authentication attempts.

The number of reports on HOUSEKEEPING is getting larger. Before I create a PR for my change, should we consider making a submenu under HOUSEKEEPING for Failures and put both 'Failed Webhooks' and my new 'Failed Authentication' under this submenu (for organizational purposes)?

@larsxschneider
Copy link
Collaborator

That sounds like a great report, Todd! What do you think about a new main section called "Failure" or something?

@toddocon
Copy link
Contributor Author

Hi Lars. I left a very lengthy comment and now it's gone. Hmm.

Anyways, what I had said was this is a great idea for a new main section.

Where would we like its position and what about the submenus?

Something like:

HOUSEKEEPING FAILURES RECOMMENDATIONS

Then the submenus I suggest that we don't need the text 'Failed' as in:

FAILURES
'Authentication' 'Webhooks'

vs

FAILURES
'Failed Authentication' 'Failed Webhooks'

We're already on the FAILURES section so the additional "Failed" menu text is redundant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants