Log format corrections

[nickcj931]

Description

In an attempt to parse my logs with failed authentication events, I have noticed inconsistency with how logs spit out various messages based on the type of authentication failure. Which is inconsistent. You also get different tags come through for selected filter option, for example selecting Warning also gets you Error messages

Inconsistency label examples

1. If you attempt to login with your Jellyseerr created user credentials you get Severity="WARN"; Label="API"; Message="Failed sign-in attempt using invalid Overseerr password"
2. If you attempt to login with Emby credentials you get Severity="INFO"; Label="AUTH";Message="Failed login attempt from user with incorrect Jellyfin credentials"

It would be good if you could look for Authentication issues under the same tag to pickup any possible malicious activity much easier.

Version

1.1.1

Steps to Reproduce

1. Go to Settings
2. Logs
3. Select between different filters
4. Observe filtered out tags making it into the view and also different tags when login fail attempts are made

Screenshots

Logs

2022-09-15T12:28:43.801Z [warn][API]: Failed sign-in attempt using invalid Overseerr password{"email":"<EMAIL REMOVED>","ip":"::ffff:<IP ADDRESS REMOVED>"}

2022-09-15T12:28:31.647Z [info][Auth]: Failed login attempt from user with incorrect Jellyfin credentials{"account":{"email":"<EMAIL REMOVED>","ip":"::ffff:<IP ADDRESS REMOVED>","password":"__REDACTED__"}}

Platform

desktop

Device

Server

Operating System

Unraid

Browser

Chrome, Safari, Firefox

Additional Context

No response

Code of Conduct

• I agree to follow Overseerr's Code of Conduct

[Fallenbagel]

Is it the same on develop tag too?

[nickcj931]

Yep just done a pull on the develop tag and its exactly the same result

[Fallenbagel]

🎉 This issue has been resolved in version 1.6.0 🎉

The release is available on:

• v1.6.0
• GitHub release

Your semantic-release bot 📦🚀