Help
This is how you monitor servers, containers and websites with inping: the command for your system, how to check that it works, and what to do when nothing arrives.
Guides
- Monitor a Linux server Set up the agent on Debian, Ubuntu, RHEL and Alpine: one command, read-only.
- Monitor a Windows server Install the agent as a Windows service with PowerShell and check that it runs.
- Monitor Docker containers The agent in Docker Compose: every service with CPU, memory, network and state.
- Monitor a Synology NAS What works on a Synology: availability, Container Manager and the limits of DSM.
- Monitor UniFi What works with UniFi: availability of the console, the agent on a self-hosted server, and why there are no values per AP or switch.
First steps
- Create a free account and set up a project for your application.
- Enter URLs in the project. inping's runners check them from then on, with nothing for you to install.
- For servers, copy the command under Agents → Add agent and run it on the server. The agent is online within a minute.
- Create a notification rule in the project so that alerts reach you by mail or webhook.
For an overview of all the routes, see Integration: connecting servers and websites. Macs and FreeBSD servers, runners and all the details are covered in the full installation guide. What each plan includes is listed under Pricing.
Check for vulnerabilities without an account
This command checks a project's packages against OSV.dev on Linux, macOS or FreeBSD, with no installation
and no account. You also get the result as a report under an unguessable link, which disappears after 30
days unless you create a project from it; with --no-report everything stays local.
curl -fsSL https://www.inping.io/scan.sh | sh -s -- /path/to/projectFrequently asked questions
What is the difference between an agent and a runner?
An agent runs on your server and reports its CPU, memory, disks, packages and scheduled tasks. A runner checks websites from the outside: availability, page changes and new pages. inping operates its own runners; you only need your own to check from your network or from a particular location.
Which systems does the agent run on?
On Linux, Windows, macOS and FreeBSD, each on amd64 and arm64, and as a Docker image in Docker Compose. The steps for macOS and FreeBSD are in the full installation guide.
Where do I get the registration token?
In inping under Agents → Add agent. The token is shown exactly once and is valid for 24 hours. The dialog also shows the finished command for every system. For an existing agent, you create a new token on its page.
Do I have to open a port for the agent?
No. Agents and runners only make outgoing connections and nothing listens on the server: to inping over HTTPS, and for a runner also to the addresses it checks.
Can inping monitor routers or switches with SNMP or ping?
No. SNMP and ICMP ping are not part of inping. Websites and web interfaces are checked over HTTP(S), servers through the agent, which has to run on the device itself.
How do these articles relate to the full installation guide?
The technical installation guide at /docs/install is maintained together with the agent and is written in English. The articles here summarise it for the most important systems, with the same commands.