---
title: "Add a signal a review proposed | Proofline Help"
description: "A review can expect a change to show up as errors, latency, lost availability or resource saturation on a service."
url: https://proofline.sh/help/deploy-signal-proposal/
---

[Help center](/help/)

# Add a signal a review proposed

A review can expect a change to show up as errors, latency, lost availability or resource saturation on a service. When the environment watches no signal of that kind for the service, the Inbox proposes one. Deploy checks read nothing for a proposal. They compare a signal only once you save it.

## Before you start

Only an administrator sees proposals in the Inbox. A proposal names a service the repository's deployment configuration lists for the environment, and the kind of signal the review expected. A signal that names no service covers its kind for every service.

## Save the proposed signal

1.  Open the **Inbox** and find the row under the environment's name that says no deploy signal watches a kind on a service.
2.  Select **Add signal**. The signal form opens on a suggested signal for that service and kind.
3.  Check the metric, its scope and the comparison. For errors or latency on Amazon ECS, enter the load balancer under **Dimensions**: the suggestion reads its Application Load Balancer, which Proofline does not know.
4.  Select **Add signal**.

The row leaves the Inbox once the environment watches a signal of that kind for the service. A signal you write yourself closes it too, when it reads one of the metrics Proofline recognizes for that kind. Later deploys compare the new signal; deploys already checked keep their recorded checks.

## Dismiss a proposal

Select **Dismiss** on the row. Proofline records who dismissed it, and later reviews do not propose the same kind for that service again.

## Related guides

-   [Read a deploy's verification](/help/read-deploy-verification/)
