How to use PMT
Use PMT correctly, without guessing
Practical guidance for sending signals, deploying starter checks, separating projects, handling tokens and reading signal data back into your own tools.
These pages are for people who want to understand what PMT does, what it does not do, and how to use it safely.
PMT is deliberately small. The docs help keep it that way.
Find the practical path
- Signal format and examples
- Starter checks
- Use your own checks
- API / CLI access
- Project separation
- Group Policy deployment
- Token storage and rotation
If a check cannot be explained simply, do not deploy it widely yet.
Start here
Use these pages to understand the signal model before connecting anything important.
How PMT works
The plain-language model: source decides, signal reports, PMT makes received states visible.
Signal format
The canonical reference for tkn, stn, sens, val, tag, GET and POST examples.
Trust & Security
Minimal-data signal handling, scoped access, token controls and what not to send.
Send signals
Choose the path that fits the source. Use starter checks where they fit; use your own logic where local judgement matters.
Starter checks
Deploy transparent predefined checks, inspect what runs and remove them cleanly.
Use your own checks
Send selected outcomes from scripts, jobs, apps, websites, devices or processes.
Group Policy deployment
Deploy Windows starter checks with normal admin tooling, staging, logs and rollback paths.
Project separation
Separate customers, branches, sites or use cases. Combine selected read views where access is granted.
Token storage & rotation
Where to store tokens, when to rotate or revoke them, and how expiry/TTL fits practical use.
Read signal data back
PMT is not only a browser view. Stored signal data can be queried by your own tools, reports, dashboards, notebooks or scripts.
Use read tokens for readback. Keep send and read access scoped to the project and purpose where practical.
API / CLI access
Submit GET or POST signals and read stored signal telemetry into your own tools.
Usage examples
Examples are starting points, not limits. They show where selected signals can be useful without turning PMT into a broad monitoring platform.
Monitoring without agents
Use PMT where installing an agent, opening inbound access or adding a control plane is not suitable.
Branch & remote sites
Tiny outbound signals for constrained sites, mixed ownership, limited links or remote environments.
Backup & job signals
Backup completion, scheduled jobs, missing reports and process visibility.
Keep the operating model small
The docs are not here to make PMT bigger. They are here to keep its use clear.
- send selected outcomes
- protect tokens
- separate projects
- inspect what runs
- avoid broad telemetry
What the docs do not change
- PMT does not run checks remotely
- PMT does not discover systems
- PMT does not diagnose causes
- PMT does not collect inventory
- PMT is not a compliance archive
Use the docs to send small signals correctly, not to turn PMT into another broad platform.
Start with one small signal
Understand the format. Choose a source. Send a selected outcome. Keep the meaning clear.