Bugs happen.
Every developer knows it. The problem is that, when something breaks, you often end up digging through
hundreds of log lines written in formats that are anything but human‑friendly.
Why LogHappens
LogHappens watches your logs in real time, parses entries into a readable format, highlights
errors and exceptions, and helps you focus on what matters—fast.
Yes. Different systems log in different ways. LogHappens ships with ready‑to‑use parsers and
makes it easy to add your own. Start with the provided examples and tailor them to your needs.
What does it look like?
Here is the default UI. You can customize the look with any Bootstrap/Bootswatch theme.
How do I add a log to track?
Add a new record to your config.json and set the values you need. For example:
{
"apache": {
"icon": "logos:apache",
"color": "#104B73",
"title": "Apache error",
"file": "/var/log/apache2/error.log",
"parser": "apache24"
}
}
Can I track a remote log (URL)?
If exposing an error log publicly is acceptable in your environment, yes—just set the URL in the configuration.
{
"myExampleSite": {
"icon": "wpf-online",
"color": "#104B73",
"title": "My ExampleSite Errors",
"file": "https://example.com/logs/error.log",
"parser": "cakephp3"
}
}
Can I capture browser JavaScript errors too?
Yes. While it’s not a LogHappens‑specific feature, you can use
a snippet like this
to capture client‑side JavaScript errors.
How does parsing work?
It’s simple. Check the files in the parsers directory to see how formats are read.
If you need to support another format, the examples are great “hello world” templates to start from.