Skip to content

Admin web server log view overflowed with ContestWebServer warnings #1601

@PPakalns

Description

@PPakalns

Description: ContestWebServer warnings are triggered by simple conditions and hides important warnings in AdminWebServer Logs view.

Steps to reproduce:

  1. One such case:
    If contestant doesn't do correct logout, contestant device will keep sending notification requests in one minute interval.
    Their authentication expires and warnings will be raised forever.
12:10:27	WARNING	ContestWebServer,1		
403 GET /contest/notifications?last_notification=1764777422.659463 (***.***.***.***) 6.96ms
12:09:27	WARNING	ContestWebServer,1		
403 GET /contest/notifications?last_notification=1764777422.659463 (***.***.***.***) 6.96ms

This error and similar 403 status code errors can be easily triggered by contestant. These will hide all other important errors from other services in AdminWebServer. Very important for long running contests.

Would be nice if such warnings could be filtered out from log view. Maybe log view could add filtering by service.

System Information

CMS version: main
How was CMS installed: virtualenv

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions