# Logging exceptions at DEBUG?

**URL:** <https://discuss.elastic.co/t/logging-exceptions-at-debug/8173>\
**Category:** Elasticsearch\
**Created:** [June 20, 2012, 4:11pm UTC](https://discuss.elastic.co/t/logging-exceptions-at-debug/8173 "2012-06-20T16:11:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [June 20, 2012, 4:11pm UTC](https://discuss.elastic.co/t/logging-exceptions-at-debug/8173/1 "2012-06-20T16:11:27Z")

</div>

Hello,

I'm trying to investigate some ES errors and when I look at the logs I see  
things like this:

[2012-06-20 12:07:53,367][DEBUG][action.search.type] [Foo search 1]  
[48639] Failed to execute fetch phase  
org.elasticsearch.transport.RemoteTransportException: [Foo search  
4][inet[/123.37.47.62:9300]][search/phase/fetch/id]  
Caused by: org.elasticsearch.search.SearchContextMissingException: No  
search context found for id [48639]

Why is this at DEBUG level and not ERROR? Shouldn't this be ERROR? I'll  
happily open an issue.

## Thanks, Otis

Search Analytics - [http://sematext.com/search-analytics/index.html](http://sematext.com/search-analytics/index.html)  
Scalable Performance Monitoring - [http://sematext.com/spm/index.html](http://sematext.com/spm/index.html)

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [June 21, 2012, 7:23am UTC](https://discuss.elastic.co/t/logging-exceptions-at-debug/8173/2 "2012-06-21T07:23:41Z")

</div>

Its by design. Action failures are propagated back to the user, so we don't  
log them as errors.

On Wed, Jun 20, 2012 at 6:11 PM, Otis Gospodnetic \<  
[otis.gospodnetic@gmail.com](mailto:otis.gospodnetic@gmail.com)\> wrote:

> Hello,
> 
> I'm trying to investigate some ES errors and when I look at the logs I see  
> things like this:
> 
> [2012-06-20 12:07:53,367][DEBUG][action.search.type] [Foo search 1]  
> [48639] Failed to execute fetch phase  
> org.elasticsearch.transport.RemoteTransportException: [Foo search  
> 4][inet[/123.37.47.62:9300]][search/phase/fetch/id]  
> Caused by: org.elasticsearch.search.SearchContextMissingException: No  
> search context found for id [48639]
> 
> Why is this at DEBUG level and not ERROR? Shouldn't this be ERROR? I'll  
> happily open an issue.
> 
> ## Thanks, Otis
> 
> Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html)  
> Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 3:23am UTC](https://discuss.elastic.co/t/logging-exceptions-at-debug/8173/3 "2017-07-06T03:23:13Z")

</div>