# Processing logs based on severity

**URL:** <https://discuss.elastic.co/t/processing-logs-based-on-severity/137144>\
**Category:** Logstash\
**Created:** [June 24, 2018, 12:33pm UTC](https://discuss.elastic.co/t/processing-logs-based-on-severity/137144 "2018-06-24T12:33:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![klapuch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/klapuch/32/32620_2.png) [@klapuch](https://discuss.elastic.co/u/klapuch)\
**Post date:** [June 24, 2018, 12:33pm UTC](https://discuss.elastic.co/t/processing-logs-based-on-severity/137144/1 "2018-06-24T12:33:48Z")

</div>

Hi,  
I would like to store all application exceptions from PHP, including invalid login username or some database connection issue.

It would be fine, if I can mark some exceptions as less relevant without bother me anymore, but still, I want to log them for further statistics.

From my point of view it would be ideal:

- if some exception is thrown, it is evaluated if relevant or not
- relevance is evaluated on probability with previous marked exceptions
- fields which are compared are: message, stack trace

Goal is to view in Kibana all exceptions and have opportunity to see relevant and irrelevant one.

I am not really sure what should I use to achieve this behavior.

I appreciate any advice. Thanks in advance 🙂

---

<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 22, 2018, 12:33pm UTC](https://discuss.elastic.co/t/processing-logs-based-on-severity/137144/2 "2018-07-22T12:33:56Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.