Printer access
Use a machine with network access to the printers. Enable the required SNMP access on supported devices and prepare any credentials. SNMP is the protocol used for these device readings.
LOCAL COLLECTION · CONNECTED OVERVIEW
Connect your printer network.
The Feeder is the local program that connects supported printer readings to PrintMetrix. It runs on a machine with access to your printer network and sends available status, counters and supply levels to the platform.
Prepare network access and a claim code, then use the installer for your operating system. A running service, a successful association and arriving printer readings are three separate things to check.
01 · PREPARE
Before you run the installer.
Check the environment first. Device support and configuration determine which readings can be collected.
Machine permissions
Service installation needs Administrator or sudo permissions. Configuration and buffered readings need writable local storage. The Feeder also needs outbound access to its configured PrintMetrix API endpoint.
Organization access
Sign in to PrintMetrix and open Feeders → Setup → Generate claim code, as directed by the public installer. Prepare a code for the organization you intend to connect.
Keep an interactive terminal open for the code prompt. Generate the code in Feeder setup, then enter it when the installer asks. The script associates the Feeder before installing the service.
02 · INSTALL
Choose your operating system.
Use elevated permissions on a prepared machine with printer-network and outbound API access. Keep your claim code ready. Available readings depend on printer support and configuration.
- Generate the codeIn Feeders → Setup for your organization.
- Run and associateRun the command below and enter the code when the installer asks.
- Let the installer set up the serviceAfter successful association, the script installs and starts the background service.
Windows
Run PowerShell as Administrator. The script registers a Windows service.
Check printer-network and outbound API access. Have your organization’s claim code ready. Enter it when prompted; successful association comes before service installation.
irm https://printmetrix.com/download/install.ps1 | iexThe Windows script also attempts to add a Defender exclusion for its installation directory. Review the installer before running it.
Check the service
Get-Service -Name PrintMetrixFeederLook for the Running state. The installer also checks whether the service starts.
Linux
Run in an interactive terminal with sudo permissions. The installer sets up a systemd service.
Check printer-network and outbound API access. Have your organization’s claim code ready. Enter it when prompted; successful association comes before service installation.
curl -fsSL https://printmetrix.com/download/install.sh | sudo bashCheck the service
systemctl status printmetrix-feederCheck the service state. For logs, use journalctl -u printmetrix-feeder -f.
macOS
Run in an interactive terminal with sudo permissions. The installer sets up a LaunchDaemon.
Check printer-network and outbound API access. Have your organization’s claim code ready. Enter it when prompted; successful association comes before service installation.
curl -fsSL https://printmetrix.com/download/install.sh | sudo bashCheck the service
launchctl list com.printmetrix.feederInspect the service listing and /var/log/printmetrix-feeder.log. A listed service alone does not confirm printer readings.
03 · VERIFY
Installed is the start. Check the readings.
Service
Use the status command for your operating system above. If it fails to start, inspect the service logs. This check concerns the local process, not the completeness of your printer data.
Association
Check that the installer completed its association step without a claim error and that the Feeder is listed in the intended organization. Service status alone does not prove the organization is correct.
Printer readings
Review the printers and available readings in PrintMetrix. If values are missing, check device reachability, SNMP configuration and Feeder logs. Polling intervals and connectivity affect freshness; not every device exposes every metric.
WHEN A STEP NEEDS ATTENTION
Find the next check.
The claim code is rejected
The public installer stops before service installation when association fails. Verify the code in Feeders setup and retry using the installer.
The service does not start
Check that the installer ran with Administrator or sudo permissions, then inspect the service status. Windows installation errors can be inspected in the Event Viewer Application log; Linux logs are available with journalctl -u printmetrix-feeder -f; macOS logs are in /var/log/printmetrix-feeder.log.
A printer or its readings are missing
Check network reachability from the Feeder machine and SNMP access, including the configured credentials. Inspect Feeder logs for per-printer errors such as unreachable devices. A connected Feeder does not establish that each printer can be polled.
Counters arrive, but some supply levels do not
Device support determines which consumables expose readings. Check the printer’s available SNMP data and configuration before treating a missing supply value as an empty cartridge. There is no universal metric set for every printer.
How are updates checked?
The Feeder updater compares a downloaded binary’s SHA-256 checksum with the value in its update metadata. This check is not a public-key signature on a release.
DATA & NEXT STEPS
Understand what is sent. Know where to ask.
Monitoring and printing are different
Monitoring collects available counters, supply levels, device status and printer metadata. Print tracking can include job metadata, while document-submission workflows can process document content.
Read the Privacy Policy ↗If an upload cannot complete
The Feeder can buffer readings in local JSON files and retry uploads. Disk space, retention and upload errors affect recovery. This mechanism is not a guarantee against data loss.
Get help with the next check
Contact support with your operating system, the step that failed and the relevant error message. Remove claim codes, keys, passwords and customer information from anything you share.
[email protected] ↗