Skip to main content

Install Alerts: New, Stale, and Back Online

How to configure alerts for install lifecycle events: a new install registering, an install going stale, and a stale install coming back online. Includes why the back-online alert matters most.

Written by Joshua Kern

Install alerts track lifecycle events for your data collection agents rather than conditions on individual devices. They tell you when a new install registers to your account, when an install stops checking in, and when one that had gone quiet returns.

These are the alerts that let you manage fleet health proactively instead of discovering a three-week collection gap at billing time.

Where They Are Configured

Install alerts sit under Install alerts, separate from the device alerts group:

  1. Navigate to the entity you want.

  2. Using the sidebar, click Admin, then Manage entity, then the Settings tab, then Install alerts.

Like all settings, these inherit down the hierarchy, so setting them once at your top-level entity covers everything beneath it. See Settings Inheritance: How Entity and Device Settings Work.

New Install Alert

Fires whenever a new install registers to your entity. Useful for confirming a technician's deployment actually landed, and for noticing installs you were not expecting.

Configuring a new install alert
  1. Navigate to the entity.

  2. Click Admin, then Manage entity, then Settings, then Install alerts.

  3. Enable the New install alerts toggle.

  4. Enter the recipient email addresses.

  5. Click Save settings.

Stale Install Alert

Fires when an install fails to check in for a number of days you define. Installs normally check in every 30 minutes, so a multi-day silence is meaningful.

Configuring a stale install alert
  1. Navigate to the entity.

  2. Click Admin, then Manage entity, then Settings, then Install alerts.

  3. Enable the Stale install toggle.

  4. Enter the recipient email addresses.

  5. In the Stale days field, enter how many days an install may fail to check in before it is considered stale.

  6. Click Save settings.

Choose Stale days deliberately. Too low and you will get alerts every time a host PC is off for a long weekend; too high and you lose a fortnight of meter data before anyone hears about it.

When one arrives, see DCA Offline or Checking In Late.

Stale Install Back Online Alert

Fires when an install that had gone stale starts checking in again. This is the most easily overlooked of the three and arguably the most important.

While an install is offline it misses events rather than queuing them. Supply replacements, low supply alerts, and service conditions that occurred during the gap are simply absent. So when an install returns, its devices need a manual review to catch anything that happened in the dark. This alert is what prompts that review.

Configuring a stale install back online alert
  1. Navigate to the entity.

  2. Click Admin, then Manage entity, then Settings, then Install alerts.

  3. Enable the Stale install back online toggle.

  4. Enter the recipient email addresses.

  5. Confirm the Stale days value, which determines how long an install must have been silent to count as stale for this alert.

  6. Click Save settings.

What to Review After an Install Returns

When you get a back-online alert, check the devices behind that install for:

  • Supply replacements that were missed. If a cartridge was changed during the gap, Print Tracker may not have registered the replacement, which suppresses the next low supply alert. See Missed Low Supply Alert.

  • Meter gaps that affect the billing period. See Meter Reads: How Print Tracker Collects and Displays Meters.

  • Devices that did not come back with the install, which usually means an IP change during the outage. See Device IP Address Changed.

Related Articles

  • DCA Offline or Checking In Late

  • Setting Up Device Alerts (Supply, Service, and Volume)

  • Settings Inheritance: How Entity and Device Settings Work

  • Installing and Managing Agents

Did this answer your question?