Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I am dealing with tens of phsb feeds.
And the dblog is filled up with feeds' messages.
I think it's good to have an option to only display the warning messages.
Comments
Comment #1
alex_b CreditAttribution: alex_b commentedThe severity filters of the log ui should be fine, we should use the debug or info flag for watchdog messages better. Would that work?
Comment #2
meatbag CreditAttribution: meatbag commentedWhen you deal with a large number of feeds, the default 1000 log entries will be easily filled up in no time.
So i think it's good to have an option to suppress some of them.
Comment #3
Dane Powell CreditAttribution: Dane Powell commented+1 for suppressing non-critical messages completely, especially considering that the number of messages grows proportionately with how frequently feeds are updated and how many feeds are enabled
Comment #4
alex_b CreditAttribution: alex_b commented#2: good point. I wonder whether we should switch to our own, separate logging stack. This would also allow us to create a better UI to filter on messages and to see some of the messages as aggregate (e. g. a graphs of how many feeds an hour have been processed, how much memory has been used etc.).
Related: #606612: More detailed log.
Comment #5
alex_b CreditAttribution: alex_b commentedSorry, that change in title was not intended.
Comment #6
buddaIf the logs do switch, it might be good to list the log entries related to the feed actually on the feed node?
Comment #7
alex_b CreditAttribution: alex_b commentedbudda - that's a good call: #870540-3: Option to suppress watchdog message
Comment #8
buddaDo any other modules out there store log data away from Watchdog that we could draw ideas from?
Comment #9
Hanno CreditAttribution: Hanno commentedwe can also take advantage of the future improvements of dblog, like #582622: provide hook for dblog_filters
Comment #10
alex_b CreditAttribution: alex_b commentedSorry, #7 was the wrong link: #606612-3: More detailed log
Comment #11
kenorb CreditAttribution: kenorb commentedClosed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.