Downloads and verification
Choose the correct download and check its authenticity before running it.
On this page
What you need
Know your operating system and CPU architecture. The setup guide helps you select a package.
How to do it
- Choose the installer or binary offered in the agent guide or setup flow.
- Use the installer checks. For manual downloads, verify the signed manifest and its file hashes with the published verification key.
- Replace demo IDs and settings in examples, then keep keys in separate private files.
Good to know
Useful files: OpenAPI, CLI manifest, manifest signature, verification key and Linux user installer. The German API file is OpenAPI DE.
The signing key's published SHA-256 fingerprint is 2663962bf6e52d694d2e9130e2b96ae1dec0d27bcd2d5811c116dfb79a4655b5. A checksum alone does not prove where a file came from.
Linux, macOS 14+, Windows 11 or Server 2022+, x64 and ARM64. npm requires Node.js 22+.
Loading agent downloads…
If something goes wrong
Do not run a download after a failed verification or for the wrong architecture. Select another available package instead of bypassing the check.
Related guides
- Install the CLI
Install MetriBeacon's command-line tool in your user account.
- Agent installation options
Choose a download or package manager and connect the agent step by step.
- Send your own monitoring data
Send your own readings over HTTPS using the IDs and keys of your monitor.