# Creative solution to hiding already seen logs

**URL:** <https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785>\
**Category:** Kibana\
**Created:** [November 21, 2016, 8:59pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785 "2016-11-21T20:59:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\
**Post date:** [November 21, 2016, 8:59pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/1 "2016-11-21T20:59:21Z")

</div>

I'm not sure if this is a Kibana or ES question, but I'm trying to figure out a way to hide all logs on Kibana that have already been seen and have already been started to be worked on.

For example, if there is a certain bug that creates an error log every 5 mins but it is being worked on, I don't want to see it appear on my visualizations so that I can focus on the other errors that are being produced.

I was thinking of maybe tagging them through the ES API or adding a new field called "TrackingBug" to the seen logs and then filtering my visualizations to hide those logs tagged "TrackingBug", but that may only work for tagging already parsed error logs and not ones that will be sent in the future.

Can anyone help me think of a creative solution to this?

---

<div class="post-metadata">

**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\
**Post date:** [November 22, 2016, 5:57pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/2 "2016-11-22T17:57:00Z")

</div>

Please help!!

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [November 22, 2016, 11:13pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/3 "2016-11-22T23:13:10Z")

</div>

What's the criteria for the error entries you are dealing with? Can you maybe just add a filter for a certain type or by some field unique to that error while it's being addressed?

---

<div class="post-metadata">

**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\
**Post date:** [November 22, 2016, 11:49pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/4 "2016-11-22T23:49:28Z")

</div>

The errors that I'm dealing with are constantly changing.

My system is running and when I make backend changes, all kinds of errors get spit out and every week they are different. When I make a ticket to deal with one of those errors, I don't necessarily want to see it on a visualization because it is being dealt with and not relevant for me to see anymore (As I am concerned with other error messages that haven't been seen by me). In a sense, I'd like to track logs that have tickets issued to them versus ones that don't. However, logs of that error type may shoot out for the next day or so while the fixes are being made and I'd prefer not to see those either.

Does that make more sense?

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [November 28, 2016, 7:17pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/5 "2016-11-28T19:17:58Z")

</div>

I think so. It's not a use case that Kibana is really well suited for, but it does sound like you could manage what you see by adding and removing filters.

That is, when you start exploring certain types of errors, you can create a filter in Kibana that will exclude those from the output until you're done. And when you are done, you can remove that filter, so that if it pops up again in the future, you will see it again.

I can't really think of a better way to do what you need in Kibana.

---

<div class="post-metadata">

**Author:** ![seanziee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/seanziee/32/45151_2.png) [@seanziee](https://discuss.elastic.co/u/seanziee)\
**Post date:** [November 28, 2016, 7:44pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/6 "2016-11-28T19:44:20Z")

</div>

Ok, thanks for your help and time!

---

<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:** [December 26, 2016, 7:44pm UTC](https://discuss.elastic.co/t/creative-solution-to-hiding-already-seen-logs/66785/7 "2016-12-26T19:44:20Z")

</div>

Closed on December 26, 2016, 7:44pm UTC

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