Howler

Howler is a simple, self-hosted log monitoring tool that sends Discord, Gotify, or Slack notifications when specified events appear in log files.

  • Communication
  • Monitoring & Logging
  • Other
  • Tools & Utilities
Howler is a simple, self-hosted log monitoring tool that sends Discord, Gotify, or Slack notifications when specified events appear in log files.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

16/100 Low

Maintained
0last commit 1144 days ago
Popular
2211 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
201 serious finding, 17 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 28 days ago

GitHub stars
11
Open issues
0
Last commit
2023-10-04
Latest release
2.0.2
Activity
stale

Checked 9 days ago - source: GitHub (Zggis/howler)

Resources & Compatibility

Minimum requirements: 102 MB disk. ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Add the howler.js file first Load howler.js in your page before any sound code, for example with a script tag or import. If you skip this, the page won't know what Howl is and your sound code will fail. source
  • Point it at your audio files Create a Howl with the paths to your sound files, like sound.webm and sound.mp3. Without valid file paths or a format your browser can play, nothing will sound. source
  • Load sounds before playing if delayed If you set preload to false, call sound.load() before you try to play. Otherwise the sound may not be ready yet and playback can silently do nothing. source
  • Installing Install on Unraid through Community Applications and map log file paths, or run Docker with a /config volume and bind mounts for log directories on port 8080. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I point Howler at logs from multiple applications?

Map each application’s log directory to a container path you remember, then create a data source in the Howler UI for that path.

Where should Howler’s database be stored?

Map the CONFIG directory to a persistent location, because that is where Howler saves its database file.

What port do I need to expose for the Howler WebGUI?

Expose container port 8080 to a host port and use that host port to reach the WebGUI.

Which log file types does Howler monitor by default, and how do I add others?

Howler monitors .txt and .log files by default. Set the FILETYPES variable to watch other extensions.

Can I create more than one alert for the same log data source?

Yes, you can create multiple alerts for each data source. They can target different events such as error or completion events.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads