High volume of Exceptions in Monitoring

Is there an Error guide posted somewhere on the community? This would help us to know what errors should be filed as tickets.

That would be awesome to have an official guide!

Here's what I use from your list of posted errors as a gut check:

Unknown Error - Catch all for anything the programmers didn't know about categorizing so could be small could be big, review each one for more details
(Object reference not set to an instance of an object usually means some variable wasn't initialized so it doesn't know what to do with it)

Background Job Error - Yellow Alert - Something might be up with the server that a job had an issue. Monitor for frequency and factors like configuration changes recently.

Socket Message Bus Error - Red Alert unless it's this one:  Socket Message Bus Errors in v12 because usually that means something is stopping the site from working (core functionality) correctly.

Content Fragment Rendering Error - Something in a widget is coded wrong. Likely to cause issues with that widget displaying or functioning correctly. Depending on the widget, could be due to customization, changes to widgets on upgrade, typos/accidental edits that went live. Review with devs as usually these errors point out the line in the code it's balking at and can be corrected.

SearchIndexingError - Error indexing content usually is followed by the why (no iFilter, i.e.: "I can't read this" or it exceeded the size limitations being common). If I have a lot of these for types I know I should have index or that are under my size limit, it might be time to reindex.

Thanks starksk !

Bridget L. Halstead thought this thread may interest you as well.

I just realized I accidentally posted this to the v12 community and we are on v11. Please move the thread to v11 community if needed.

Same answers in v11 minus the v12 specific error exception.

Same answers in v11 minus the v12 specific error exception.