The nice thing about using Kibana for your logs is that you get nice custom filtering. Thus it’s very easy for others to only view errors they feel that are relevant to them.
If you have a many systems (gui’s, services, etc) where you pipe a lot of log data into the same log database, then it can be beneficial to to filter out systems that you’re not coding anything in.
The downside of having easy filters is that it’s really easy to ignore errors. A screen with the graph of all errors could perhaps mitigate that.
It would be nice to have Elmah like formatting of stacktraces. Perhaps a chrome plugin could fix that. Perhaps port the stacktrace parsing from ElasticElmah to js.
The nice thing about having your logs in elastic is that you don’t need to just use kibana to query your logs. It’s really easy to use Nest to do queries. Unless you have huge amount of logs you can do groupings in memory.
Do you want to send a comment or give me a hint about any issues with a blog post: Open up an issue on GitHub.
Do you want to fix an error or add a comment published on the blog? You can do a fork of this post and do a pull request on github.
Comments