Skip to content
TarleyNode
How it worksFeaturesSecurityLicensingDownload
Request a demo

Founding testers wanted. TarleyNode is new, and I’m looking for 20 IT and network admins to try it and tell me what’s broken or missing. In return you get a full licence free for 12 months. Become a founding tester →

TarleyNode 0.4.1

Released 10 November 2026

Added

  • Settings › Monitoring › Company limits: one limit for Disk (the fullest disk), Memory, CPU and Swap on every device, with a severity, raising one incident per device and limit through the usual notifications. All four start off. A device can set its own value or turn a limit off on its page; every change is in the audit trail. A rule someone saved on a check watching the same reading takes over for that device. The starting rules a device template gives its checks, including the built-in Linux server (SNMP) template, do not until someone saves one, and a device over both a limit and such a rule gets one incident and one alert, the limit's. See docs/configuration.md.
  • Devices › Rescan all shown, or tick devices › Rescan for changes, reads the interfaces and sensors of many devices again at once and sums up what changed as the sites report: how many are done, which have changes and which could not be read and why, each linked to its device. Devices without an SNMP login, or already being rescanned, are left out and named, and so, for Rescan all shown, are devices on a disconnected site or one whose network ranges are changing. Operators and administrators can, as with one device; one audit entry records the counts. A site is handed rescans 20 at a time, the five minutes before a device counts as not answered run from the site's last progress through the batch, and one waiting its turn on an online site waits up to 30 minutes. A device page follows such a rescan to the end.
  • Devices › tick devices › Assign login gives them all one saved login, such as the SNMP login they share, as assigning it on each device page does. The review says how many switch to it, how many get its first check, and which are left out and why (it does not fit, no address, or a database or VMware login whose first check needs details). Only administrators can; the login's secret never reaches the browser, and one audit entry records the counts and the login's name.
  • Settings › Mobile devices shows when each phone's pairing expires, and says when one has expired and how to renew it. A pairing lasts 90 days from its person's last console sign-in; using the phone does not renew it. The phone app shows a banner in the last 14 days, and the phone gets a notification 7 days and 1 day before, saying how long is left.
  • The Audit trail shows each event's details, such as a site's SNMP port, under the action and in a Details column of the CSV, leaving out details with no value.

Fixed

  • Operators in an access group can now rescan the devices they see, as the 0.3.7 notes said they could, from a device page, and they can use the new Rescan all shown, which reaches only their own devices. Before, every rescan was refused. A device outside their group is treated as not found.
  • The GPS map shows OpenStreetMap tiles again. For map tiles only, the tile server now receives the console's address, never the page's path, which OpenStreetMap needs to serve them.
  • Audit trail search also finds an action typed as it is stored, with dots and underscores.
  • Sensor graphs, including a database sensor's Lines view, stay inside their card at every width when the readings table is open, so the end of the time axis and the CSV, PNG and range buttons are no longer cut off.
  • Long device, host, service and connected-site names break onto a new line instead of pushing pages sideways or past the page actions. The incident page, top bar, device page actions, guide chapters, map site filter, Overview health figures, service figures, snooze list and the wall screen also fit narrow and mid-size screens, and the exporter list shows each address first.

Security

  • Phones and TarleyNode Desktop pair only to people who sign in with two-step. Settings › Mobile devices offers Set up two-step instead of Pair a phone, and the phone app shows a Turn on two-step sign-in screen. A phone already paired to someone without two-step keeps getting alerts, but can only be unpaired or have its notifications turned off until they turn two-step on. Someone who signs in only through a directory (LDAP) needs a TarleyNode password with two-step to pair a phone; organisation sign-in counts its own two-step. An administrator's two-step reset also removes the person's phones.
  • A phone whose pairing has expired no longer gets alert notifications.

All releases · Plain text

TarleyNode Self-hosted network monitoring.

Sales: sales@tarleynode.com. Support: support@tarleynode.com

How it worksFeaturesSecurityLicensingDownloadAboutComparisonsGuidesReleasesSupportContactPrivacyCookiesTermsRefunds
YouTubeGitHubXBlueskyFacebookInstagramThreads