---
title: "Comment by StackShortlist on \"Introducing CyberKit Log Analyzer — A Free Browser-Based Log Analysis Tool\" | Hashnode"
description: "Keeping the analysis in the browser is a real selling point for logs, since they often contain IPs, emails and session ids people should not paste into a random"
url: "https://hashnode.com/posts/introducing-cyberkit-log-analyzer/6ad2a3e963ec362f1d8a7051/comment/6ad2ab71a305ffe669180bdb"
---

[Discussion](https://hashnode.com/posts/introducing-cyberkit-log-analyzer/6ad2a3e963ec362f1d8a7051)

Comment [Introducing CyberKit Log Analyzer — A Free Browser-Based Log Analysis Tool](https://hashnode.com/posts/introducing-cyberkit-log-analyzer/6ad2a3e963ec362f1d8a7051)

[StackShortlist](https://hashnode.com/@veristria)

[Oct 16](https://hashnode.com/posts/introducing-cyberkit-log-analyzer/6ad2a3e963ec362f1d8a7051/comment/6ad2ab71a305ffe669180bdb)

Keeping the analysis in the browser is a real selling point for logs, since they often contain IPs, emails and session ids people should not paste into a random server. It would be great to see grouping by normalized message, where numbers and ids are replaced with placeholders, because that usually surfaces the one error pattern hiding among thousands of lines. Support for large files through streaming parsing would also make it handy for real production logs.