We sometimes get the following message:

20 Aug 2018 11:16:16.408
 Indexing failed (1 indexing errors), attempt 3 out of 3: SerializationException: failed to serialize item #0
20 Aug 2018 11:16:14.083
 Indexing failed (1 indexing errors), attempt 2 out of 3: SerializationException: failed to serialize item #0
20 Aug 2018 11:16:12.434
 Indexing failed (1 indexing errors), attempt 1 out of 3: SerializationException: failed to serialize item #0
20 Aug 2018 11:16:09.523
 Indexing failed (1 indexing errors), attempt 1 out of 3: SerializationException: failed to serialize item #11
20 Aug 2018 11:16:05.893
 Indexing failed (1 indexing errors), attempt 2 out of 3: SerializationException: failed to serialize item #22
20 Aug 2018 11:16:03.292
 Indexing failed (1 indexing errors), attempt 1 out of 3: SerializationException: failed to serialize item #22
20 Aug 2018 11:15:57.640
 Indexing failed (1 indexing errors), attempt 2 out of 3: SerializationException: failed to serialize item #45
20 Aug 2018 11:15:53.616
 Indexing failed (1 indexing errors), attempt 1 out of 3: SerializationException: failed to serialize item #45

These errors also result in the following message as mentioned in support ticket 139325:

Deletion of non-occurrences skipped due to indexing errors.

I would like to get a more clear description as to what class/property caused this exception and perhaps even with what data.
Perhaps enhance this message with a classname and propertyname or add an error log of the cluster side errors in the index overview panel at find.episerver.com.