Skip to main content

Signals

A signal is proof that an application is still alive, even when nothing fails. Collector keeps, per environment, when each project's servers and browsers were last heard from, with their latest release and SDK. It shows above the Issues list.

Where they come from​

  • Heartbeats: the server SDKs send one when they start and one every hour; the browser's, one a day per release and environment, a few seconds after it starts.
  • Events: every error that arrives counts as a signal too, so an application that sends no heartbeats still shows up.

The browser's heartbeat carries nothing about whoever visits the page; see Security and privacy. Each SDK lets you turn it off with its heartbeat option.

The statuses​

Per environment, servers and browsers separately:

  • Servers reporting / Browsers reporting: there was a recent signal. For servers, in the last 3 hours; for browsers, in the last 24.
  • Servers silent / Browsers silent: that long went by with no signal.
  • Servers stopped reporting: the servers of an environment that alerts went quiet. It's the only status that sends email.

If the project never received anything, the line says No signal yet: nothing has reported to this project and offers How to set it up.

The alerts​

When a project's servers go 3 hours without a signal, Collector emails the same people who get the project's issues (the whole organization, except whoever muted it), once per silence. When they're back, it sends another.

To avoid false alarms:

  • Only servers alert, never browsers: nobody visiting your site at night isn't an outage.
  • The dev, development, local and test environments don't alert, nor do events with no environment.
  • Only a server that stayed up for about 50 minutes alerts: a start that falls over right away doesn't count as silence.

From the terminal​

collector signals