Contact us
Email hello@ooz.ch with any question about
Content Caching Monitor — a problem, a feature request, or help getting set up.
We aim to reply within two business days.
Reporting a problem
The more of this you can include, the faster we can help:
What you were doing, and what you expected instead.
The macOS version of the Mac running the app, and of the caching server involved.
Whether the server has ever reported successfully, or has never appeared at all.
Whether the collector is running — the first card in the sidebar says so.
Requirements
The monitoring app needs macOS 26 Tahoe or later.
Each caching server needs macOS 27 Golden Gate or later, with Content Caching
switched on. Scheduled status reporting is what the app reads, and it does not exist in
earlier versions of macOS.
The Mac running the app and the caching servers must be able to reach each other on the
local network.
Common questions
A caching server is not showing up
Work down this list — it is almost always one of these:
Is the collector running? The first card in the sidebar shows its state.
It is a small background helper that receives reports on TCP port 17440; it has
to be started once, with your consent.
Is the server on macOS 27, with Content Caching on? Earlier versions cannot
send scheduled reports at all.
Has the server been pointed at this Mac?Add Server… on a
site’s card shows the exact commands to run on the caching server. The app never runs
anything on the server itself.
Can the two Macs reach each other? A firewall or a separate VLAN between
them will stop reports arriving, with nothing to see at either end.
The server appeared, but its numbers are not counted
A server that reports for the first time arrives as a request, with Approve and
Reject. Its data counts only once you approve it. This is deliberate: nothing joins
your fleet without you saying so.
Reports are missing for a time the monitoring Mac was asleep
A caching server sends each report once and does not retry, so a report sent while the Mac
running the app is asleep, switched off or not running the collector is lost. To keep them, install
ccm-agent on the caching server — a small helper, signed with our Developer ID
and notarised, available from this site. It holds each report until the collector has it. It is
entirely optional, and the app neither downloads nor installs it.
How many servers can I add?
Up to ten approved servers in this edition. Servers you have rejected do not count, and can be
reviewed in Settings.
Does any of this leave my network?
No. There is no account, no cloud service and no server of ours. Reports travel from your caching
Macs to the Mac running the app, over your own local network, and stay there. See the
Privacy Policy, and
how the data is collected for the detail.
Can I feed this into the monitoring I already run?
Yes. Settings has optional endpoints for
Prometheus and Nagios. Both are off until you
turn them on.
How do I stop the collector?
It is registered as a login item, so System Settings › General › Login Items &
Extensions will stop it. Nothing is received while it is not running, and servers without
ccm-agent lose what they send in that time.