- All
- Case Studies
- ChromeOS Monitoring
- Dashboard
- Linux Client
- Mac Client
- News
- Release Notes
- Success Stories
- Windows Client
- All
- Case Studies
- ChromeOS Monitoring
- Dashboard
- Linux Client
- Mac Client
- News
- Release Notes
- Success Stories
- Windows Client
An Infrastructure Update, This Morning’s Outage, and What’s Next
As we’ve shared previously, we’ve spent the last several months on a major upgrade to the infrastructure that runs Watchman Monitoring. This is a big investment in the future of the platform: it lets us ship updates, new features, and bug fixes far faster than before. As with any migration of this size, it also comes with the occasional bump along the way, and we want to be transparent about one we hit this week. What happened We completed the migration to the new infrastructure at the beginning of this week. Shortly after, we noticed a handful of customers reporting that their Mac clients weren’t updating to the latest version. While our team was investigating and triaging that issue, a change made during troubleshooting inadvertently left the application in a state that would fail the next time it restarted. Overnight, the application went through a minor, routine restart, and because of that lingering change, it came back up incorrectly and was effectively down. As soon as a team member was available to see the downtime, we triaged it and brought everything back online. We understand exactly why it happened and have already put a process in place so it doesn’t ...
Read More →
Introducing the New Watchman Monitoring Linux Agent (4.0.2)
We are pleased to announce a major milestone for Linux monitoring: a complete rewrite of the Watchman Monitoring Linux agent. Version 4.0.2 replaces the legacy Python 2 agent, which is retired and will no longer be receiving updates. The new agent is available now to all subscribers. Install it from your dashboard under Installers → Linux. Overview The new Linux agent is a single compiled Go binary (monitoringclient). It does not depend on Python or a runtime interpreter on the host. Checks run on an hourly schedule via systemd, with a long-running beacon service for uptime reporting when enabled for your account. This release is the foundation for modern Linux monitoring at Watchman Monitoring. The same architecture may inform future Mac and Windows agent work if we choose to pursue that path. Features Modern platform support Tested on: Ubuntu 22.04, Ubuntu 24.04, Debian 12, Rocky Linux 9, Fedora 40, Amazon Linux 2023 Compatible with: other RHEL 9-family distros (AlmaLinux, RHEL) and recent glibc-based Linux with systemd Architectures: amd64 and arm64 The agent ships with built-in checks for common Linux server monitoring, including: Root volume capacity Installed RAM Operating system version Last reboot time Failed SSH login attempts Fail2ban status Apache web server (systemd service status) MySQL/MariaDB (systemd service status) Primary internal IPv4 address Mounted volume status Network interface status ...
Read More →
Mac Client 7.1.7.712 — CrashPlan and P5 reliability fixes
Watchman Monitoring is happy to announce the release of agent 7.1.7.712 for macOS. It will automatically roll out to all Computers next Tuesday, June 2 2026. Bug Fixes CrashPlan: more reliable destination discovery For years, the CrashPlan plugin has discovered configured destinations by parsing the DESTINATIONS section of CrashPlan’s app.log. That format has shifted repeatedly across CrashPlan 8.2, 11.0, 11.5, and 11.6, and routine log rotation can strip the header the parser needs. The visible symptom has been machines reporting “No CrashPlan Destinations reported” while backups were actually running normally. This release adds a filesystem fallback: when app.log yields zero destinations, the plugin scans CrashPlan’s cache directory for GUID-named subdirectories with a cp.properties file — the same authoritative records the plugin already uses for per-destination data. The fallback only activates when the log-based lookup comes up empty, so installs whose app.log still parses cleanly behave exactly as before. If your CrashPlan destinations have been silently dropping out of the report, this should bring them back. P5 plugins: no more spurious tracebacks The check_p5_devices and check_p5_jobs plugins could crash on otherwise-healthy machines when nsdchat returned empty output — common on hosts where P5 is installed but not yet configured, or during ...
Read More →
Mac Client 7.1.706. – Munki v7 Support
Watchman Monitoring is happy to announce the release of agent 7.1.7.706 for macOS. Munki Improvements Munki v7 Support – The Munki plugin now supports Munki v7 and will properly display it in the Dashboard. Bug Fix – Munki plugin no longer crashes when ManagedInstallReport.plist records EndTime as a date. Affected hosted could go silent on Munki reporting. This new version will roll out to everyone on Tuesday May 12 2026. If you’d like to receive this version before then, please let us know and we’re happy to help. What’s Next More bug fixes for various plugins A brand new MDM plugin Better duplicate Computer detection Revamped Webhook integration
Read More →
Zendesk Integration Update: Migrate to Oauth and fix two way integration
We are happy to announce that we have upgraded our Zendesk integration. We have added support for Oauth client based authentication and behind-the-scene changes to how tickets are updated. If you use Watchman Monitoring’s Zendesk integration , here’s what’s changing and what you should do about it. Connect with with OAuth The biggest change is that can connect to Zendesk using OAuth instead of the legacy permanent API token. When you open the Zendesk integration settings, you’ll see a new Authentication Method toggle with two options. The new (recommended) one, OAuth, lets you connect by entering an OAuth Client ID and Secret from your Zendesk account and clicking Connect with OAuth. You’ll be bounced over to Zendesk to authorize, then dropped back into Watchman Monitoring once you approve. The existing API Token flow (admin email plus token) is still available for backward compatibility. Once OAuth is connected, you’ll see an OAuth Connected indicator along with the token’s expiration date. You don’t need to do anything when that date arrives. Watchman Monitoring refreshes the token automatically before it expires. Why does this matter? Zendesk is steadily pushing its platform toward OAuth as the modern, secure authentication standard. As of February 2, ...
Read More →
Windows Client 1.6.2.4 – Volumes and BitLocker Plugin fixes, Cisco MAC addresses, and more
Rolling out to all subscribers starting Tuesday, May 5, 2026 (1400 UTC / 9:00 AM Central) Auto-update connectivity fix Earlier this year our load balancer infrastructure dropped support for TLS 1.0 and 1.1 in line with current security standards. The Monitoring Client’s auto-updater (a third-party component compiled against .NET 4.0) defaulted to those older protocols and could no longer download update manifests on systems without certain Windows registry hardening applied. 1.6.2.4 ships an update.exe.config and self-healing logic in the agent so the updater always negotiates TLS 1.2. After this release lands, future updates will go through cleanly even if your endpoints don’t have SchUseStrongCrypto set in the registry. Improved network adapter detection The MAC blocklist used by the agent to identify physical vs. virtual/ephemeral adapters has been expanded to include: Cisco AnyConnect VPN virtual adapters Cisco Network Software virtual adapters If you’ve seen flaky beacon/IP-address reports on machines that frequently connect through Cisco VPN, those should stabilize. Volumes and BitLocker plugin crash fix Both plugins read the system’s drive list from a registry JSON blob. When that JSON ended up malformed on certain endpoints (rare but reproducible after some Windows feature updates), the plugins would crash and produce no output. The plugins ...
Read More →