# Using ELK to analyze log warnings and exceptions - and mark them as "solved"

**URL:** <https://discuss.elastic.co/t/using-elk-to-analyze-log-warnings-and-exceptions-and-mark-them-as-solved/22654>\
**Category:** Elasticsearch\
**Created:** [March 13, 2015, 11:50am UTC](https://discuss.elastic.co/t/using-elk-to-analyze-log-warnings-and-exceptions-and-mark-them-as-solved/22654 "2015-03-13T11:50:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thomas\_Guttler](https://avatars.discourse-cdn.com/v4/letter/t/9f8e36/32.png) [@Thomas\_Guttler](https://discuss.elastic.co/u/Thomas_Guttler)\
**Post date:** [March 13, 2015, 11:50am UTC](https://discuss.elastic.co/t/using-elk-to-analyze-log-warnings-and-exceptions-and-mark-them-as-solved/22654/1 "2015-03-13T11:50:34Z")

</div>

We run several servers running our code.

Of course there are bugs which cause exceptions and warnings since  
something unusual occurs.

I want to analyze our logs to find unhandled warnings.

I am unsure if ELK can help us.

There need to be some way to aggregate warnings to a warning of type X (to  
remove duplicates).

If a warning was handled and solved, we need a way to mark the warnings of  
type X as solved.

The flag should only be set for a limited period of time (example 48  
hours). During this  
time the new code should be deployed and the error should nor occur again.

If it sill occurs after N hours the warning should be visible again.

Can you understand what I want?

Can this be done with ELK, or I am on the wrong track?

Regards,  
Thomas Güttler

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d67d74ca-ab6a-4739-b119-63f52bbb7231%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d67d74ca-ab6a-4739-b119-63f52bbb7231%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 12:27am UTC](https://discuss.elastic.co/t/using-elk-to-analyze-log-warnings-and-exceptions-and-mark-them-as-solved/22654/2 "2017-07-06T00:27:03Z")

</div>