Add unaggregated verbose output of image derivative creation sensor

In my words... ;-)

Yeah, the unaggregated result (if any) should be pretty near to the original watchdog records. Things might be highly repetitive and the timestamp is possibly most important.
I asked to once try enabling typical verbose_fields and stick with typical Watchdog output...

The whole debate we entered about usage, ... is a completely different aspect:
It is more subject for a second verbose table that shows the aggregated results with counts and possibly other data... Because every URL only appears once.
(And also don't forget here to display the max(timestamp)..)

Looks pretty good.

I agree adding the grouped thing into a followup.
However then please don't drop the (already available) verbose usage export that is more related to the aggregated output than the unaggregated one.
So i think resultVerbose should stay mostly unchanged.

Please create the followup and provide a link.

+++ b/modules/demo/monitoring_demo.install
@@ -86,6 +86,30 @@ function monitoring_demo_install() {
+  \Drupal::service('logger.dblog')->log(LOG_NOTICE,
+    'Source image at %source_image_path not found while trying to generate derivative image at %derivative_path.', [
...
+  \Drupal::logger('image')->notice('Source image at %source_image_path not found while trying to generate derivative image at %derivative_path.', [

Why writing the same record type in two different ways?

Please add a comment to explain this where you write it. ;-)

Committed. :-)