PingMyThing for Admins
Script, job and scheduled task results without another agent
Use a visible starter check, or send your own result from PowerShell, Bash, cron, Task Scheduler, a backup job, service check or application. PMT receives the selected outcome and makes the received state available centrally without installing an endpoint agent, collecting inventory or running remote commands
Token → deploy or send → see
- Get a scoped token
- Deploy a BAT/PS1 starter check or send GET/POST
- The station and signal appear automatically
- View received states in the PMT webapp on desktop, mobile or an operations screen. Use API/CLI readback when stored signal data needs to feed another tool.
Start with one system and one useful condition.
Two ways to start
PMT does not require you to build a monitoring platform before seeing value.
Use starter checks
Deploy transparent predefined checks for common Windows conditions. Each check creates its own scheduled task and can be inspected, adapted, disabled or removed.
- BAT/PS1 deployment
- Group Policy rollout where appropriate
- Heartbeat, disk, reboot and update conditions
Use your own checks
Your PowerShell script, scheduled task, cron job, service, application or external check decides the result locally. PMT receives the chosen outcome and makes it visible.
- PowerShell, Bash, cron and scheduled tasks
- Backup jobs, services, websites and devices
- GET or POST from anything that can send HTTP
Why this helps admins
PMT is deliberately small. It gives selected checks somewhere central to report without taking control of the system.
No platform to model first
A valid first signal can create the station and signal. You do not need to define the system estate before proving the path.
Transparent scheduled tasks
Starter checks are visible scripts and scheduled tasks, not opaque agents. Admins can see what runs, when it runs and what it sends.
Local logic stays local
The script or check decides whether the condition is OK, needs attention, is unknown or has failed. PMT centralises the received result.
Mixed systems
Use the same signal model across Windows, Linux, macOS, servers, virtual machines, appliances, scripts and hosted services.
Browser and API access
Use the webapp on desktop or mobile, leave it visible as a lightweight operations screen, or read data through API/CLI access.
Cadence and absence
Repeated signals create an expected rhythm. If a scheduled signal stops arriving, the absence becomes visible too.
The checks admins already write
PowerShell scheduled task
Backup script result
Cron or batch job
Disk or reboot condition
Service or website check
Application health result
Less noise by design
Admin tools often drift toward broader collection: more logs, more metrics, more dashboards, and then another layer to explain the noise.
PMT takes a narrower route. Use it for selected system signals where the received result, or absence of an expected result, would change what you do.
Spear, not telemetry net
A net catches everything and leaves an admin to sort through it. PMT is closer to a spear: one chosen signal aimed at one system condition that matters.
Chosen system signals, not broad collection
PMT does not discover systems, collect logs, or gather every metric.
Outcomes before explanation
The script, scheduled task, service, or check decides the result. PMT makes the received state visible.
Absence without false reassurance
If an expected system signal stops arriving, that absence can be visible. PMT does not infer that everything else is healthy.
Before you add signals
PMT works best when the question is clear and the result would change what an admin does next.
PMT may fit if
- a predefined starter check answers a useful first question
- your scripts, tasks or services already know the result
- you want visibility without another control layer
- non-reporting is a real operational risk
- you need one simple reporting pattern across mixed systems
- you want internal and external checks visible together
PMT may not fit if
- you expect automatic discovery or full system visibility
- you want remote remediation, patching or inventory
- you want PMT to diagnose faults or explain cause
- you need a compliance archive or system of record
- you need safety-critical or life-critical control
PMT reflects selected signals. It does not interpret them.
From first check to ongoing visibility
The first signal proves the path. Repeated signals create useful rhythm.
A starter check, scheduled task, script, service or device reports its chosen result. If expected signals stop arriving, absence becomes visible too.
Use the browser webapp for day-to-day visibility, mobile checks or a lightweight operations screen. Use API/CLI access when you want the same signal data in your own tools.
Simple operating model
- check determines meaning
- PMT accepts the small result
- webapp shows received state
- cadence makes silence visible
- API/CLI lets you consume data elsewhere
Useful first admin signals
Start with conditions where the answer is simple and action follows.
Windows starter check
Heartbeat, disk space, reboot pending or update failure from a visible scheduled task.
Scheduled task or job
A task reports OK, act soon, act now or unknown after it evaluates the local result.
Backup result
A backup job or log check reports whether the latest run produced the expected result.
Service or website
An internal or external check reports whether a site, service, DNS record or email path behaved as expected.
Branch or remote system
A small outbound signal confirms that a remote system, branch device or constrained link is still reporting.
Custom application
An app or process reports a selected state or value using the same small signal model.
Choose your starting point
Starter checks
Deploy transparent Windows checks without writing a script first.
Use your own checks
Send results from PowerShell, Bash, scheduled tasks, services, apps or devices.
How it works
See the token, station, signal and value model before deploying anything serious.
Get your signal
Deploy one transparent starter check, or send one signal from something you already control.
View the result.
Confirm the path.
Replace the test with something real.