Re: Kibana: Mark warnings as solved

solve my use case? I guess I am missing something. Regards, Thomas Güttler Am Mittwoch, 8. April 2015 11:02:35 UTC+2 schrieb James Green: Couldn't you update the document with a flag on a field? On 8 April 2015 at 09:43, Thomas Güttler h...@tbz-pariv.de javascript: wrote: We

Kibana: Mark warnings as solved

We are evaluating if ELK is the right tool for our logs and event messages. We need a way to mark warnings as done. All warnings of this type should be invisible in the future. Use case: There was a bug in our code and the dev team has created a fix. Continuous Integration is running, and

ELK for logfiles

Hi, I am planing to use ELK for our log files. I read docs about logstash, elasticsearch and kibana. Still the whole picture is not solid. Especially the reporting area is something I can't understand up to now. Kibana seems to be a great tool to do the visualization. But can I get the

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

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

Easy ELK Stack setup

will come in only from localhost. The systems will run isolated. I see these solutions: - take a docker container - do it by hand (RPM install) - use Chef/Puppet. But up to now we don't use any of those tools. - any other idea? What do you think? Regards, Thomas Güttler -- You received