Capture messages without timestamps in the title

[HJGreen]

Allows the Sentry UI to properly group related issues. The formatted property includes a timestamp, which causes Sentry to log them as separate issues.

See the attached screenshot for an example. There are two missing CSS files which Silverstripe is trying to link into the page. The first four entries show the current behaviour where each time the page is loaded, a new Issue is logged in Sentry due to the timestamp.

The bottom two rows are with the PR applied - similar events are grouped with the original.

[dcentrica]

If I invoke manual logging - there is no "message" key in the "context" array:

        $logger = Injector::inst()->createWithArgs(Logger::class, ['error-log'])
            ->pushHandler(SentryHandler::create('DEBUG')); // Send errors >= DEBUG
        $logger->info('This is a test');

[Notice] Undefined index: message

It would be good to see exactly how you triggered the error (i.e. is bundle.css being called in a template context or via the Requirements API?)

The following might work better:

$record['context']['message'] ?? $record['formatted']

[HJGreen]

In this case the CSS files were being included via the Requirements API:

    protected function init()
    {
        parent::init();
        Requirements::css('themes/base/build/bundle-index.css');
        Requirements::css('themes/base/build/bundle-print.css', 'print');
    }

There is a $record['message'] property too - which contains the following:
E_USER_NOTICE: File themes/base/build/bundle-index.css does not exist

So perhaps?
$record['context']['message'] ?? $record['message']

[phptek]

@HJGreen thanks for this - using "message" actually sorts the problem. In the process of looking at this, I realised that exceptions were also logging twice for each message. I have fixed this too - currently in master.

[phptek]

@HJGreen FYI, you can use tag 4.0.5 which incorporates this fix.