Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Problem/Motivation
The DbLog module's recent reports page can be filtered to messages from the reporting module, but shows limited info.
Pending dedicated storage for violation reports, provide a page that queries only violation reports from the dblog table if the module is enabled.
User interface changes
A new page available in the Reports section of the admin area.
| Comment | File | Size | Author |
|---|
Issue fork reporting-3549053
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
gappleType, Disposition, and Location are the properties that can be listed on any report regardless of type. Additional logic would be needed to parse out priority fields from CSP (e.g. violated directive), Permissions Policy (restricted feature), etc, to show in the list.
Since the report itself is serialized in the database field, it's not practical to add filtering options.
View can just link to the DB report page which shows the JSON in pretty-print format. A dedicated page could break out the fields from the body to display more nicely, and omit the fields which aren't helpful from the watchdog table (e.g. Watchdog's Location is always the reporting endpoint url, Severity and User are not necessary...)
Comment #5
gapple