@bruno-garcia - Thanks so much for the prompt reply.
I was using raven, but am now trying to get @sentry/node to work as per your suggestion. I used npm to install the package and can see it show up properly in my package.json.
I followed the configuration steps of requiring @sentry/node and running Sentry.init with my custom dsn and have wrapped the code in a try/catch block as well.
When I go to a non-existent route, such as http://localhost:4002/test4, Express shows an error in the browser, but doesn’t show up under my Sentry account’s control panel.
The only way I’ve gotten it to report an exception is by manually calling with: Sentry.captureMessage(‘Something went wrong’);
That’s a step in the right direction, but it would be unwieldy to add those in many places in the app, so I was hoping for a more global exception handling approach.
Any further suggestions that you have would be greatly appreciated. Thanks again.