# Log file configuration document source
**URL:** https://discuss.elastic.co/t/log-file-configuration-document-source/13144
**Category:** Elasticsearch
**Created:** [August 9, 2013, 7:35am UTC](https://discuss.elastic.co/t/log-file-configuration-document-source/13144 "2013-08-09T07:35:38Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Sagar\_Mehta](https://discuss.elastic.co/u/Sagar_Mehta)
#### Post date: [August 9, 2013, 7:35am UTC](https://discuss.elastic.co/t/log-file-configuration-document-source/13144/1 "2013-08-09T07:35:38Z")
I am indexing full text documents using the mapper attachments plugin.
Sometimes, documents can't be parsed... but my log files get polluted with
the entire base64 encoded source of the document which makes them hard to
look through. The exception in question is:
org.elasticsearch.index.mapper.MapperParsingException
I do want to know when things fail indexing, but I don't want to see the
entire source, instead the \_id is probably sufficient... is there a way to
configure the logging to do this or is basically all or none with this type
of exception?
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 2:21am UTC](https://discuss.elastic.co/t/log-file-configuration-document-source/13144/2 "2017-07-06T02:21:52Z")