A recent change was made pertaining to the display/digestion of error logs specifically with EVLV: https://wpengine.atlassian.net/browse/ELEC-1995
While this change seems to have been made for possible aesthetic purposes (hiding an empty column), it doesn't hit on the issue of this providing a worse experience trying to troubleshoot an EVLV site on the admin's end. In the example given on the image via these new logs, the actual error in the backend would read:
PHP Fatal error: Uncaught TypeError: Unsupported operand types: string * int in /nas/content/live/nuwestgroup/wp-includes/functions.php:75
The info given to the customer is now essentially "something happened on this file at this line" and completely strips the actual error that was thrown.
I don't believe taking features away should constitute as a fix in this scenario, and that further efforts should be made to either bring back that functionality (if this is going to be the future of our platform) or providing a suitable and just-as-accessible alternative.