UptimeLogger

Installing UptimeLogger

Version 0.1 is not code-signed. Both operating systems warn about software from a developer they cannot verify. The steps below are the standard way to accept it, and each is needed once.

macOS (11 Big Sur or newer)

  1. Open the DMG and drag UptimeLogger.app onto the Applications shortcut beside it.
  2. On first launch macOS says the developer cannot be verified. Open System Settings → Privacy & Security (macOS 13 Ventura and newer) or System Preferences → Security & Privacy (macOS 11 and 12), scroll to the message about UptimeLogger and choose Open Anyway.
  3. The icon appears in the menu bar. Choose Open Dashboard to see your data.

The application has no Dock icon and no entry in the app switcher on purpose — it is a background monitor.

Wi-Fi network names

Recent macOS versions only reveal the Wi-Fi name to applications that have location permission. UptimeLogger works fully without it; the Network column then simply shows the interface on its own, for example en0. Turn on Look up the Wi-Fi name in the settings if you want the name, and grant the permission macOS asks for.

Windows (10 or newer)

  1. Run the installer. It installs for the current user and needs no administrator rights. Start UptimeLogger automatically when I log in is ticked by default; untick it if you would rather start the program yourself.
  2. SmartScreen warns about an unknown publisher. Choose More info → Run anyway.
  3. The icon appears in the notification area.
The installer's Additional Tasks page with the autostart checkbox ticked
The autostart is a checkbox in the installer, ticked by default. The install is per-user and asks for no administrator rights.

Starting automatically

The switch is Settings → Start automatically when I log in and works the same on both systems. The Windows installer offers the same thing as a checkbox, and both write the same entry, so the two can never disagree.

Neither entry needs administrator rights, and both apply to your user account only.

Where the data lives

Deleting that folder removes every recorded event and every setting. A small log file of recent unexpected errors, uptimelogger.log, lives next to the database.

Uninstalling

Quit UptimeLogger from the tray menu first on either platform, so it is not running while you remove it.

Troubleshooting

A saved link to the dashboard does not load, but the application is running

If port 17641 was already taken when UptimeLogger started, it binds the next free port instead. Always use Open Dashboard from the tray menu — it opens whatever port the application is actually using.

A short outage right after waking from sleep is missing from the log

After a gap, UptimeLogger waits out the Wait after waking from sleep setting before it starts recording again, so a wobbly reconnect is not logged as an outage. Lower the setting (down to 0) if you would rather see every short outage at the cost of the occasional false one.

Something else looks wrong

The first place to look is the log file next to the database. It is a small, capped file of the application's own error messages — including database and bind failures — and is almost always more specific than anything visible in the dashboard.

If it helped

UptimeLogger is free and stays free. If it saved you an argument with your provider, you can buy me a coffee.