gTTA timeout may cause indefinite milestone chaining

[karimodm]

In case of gTTA timeout Compass will reference latest milestone with a warning. This will drop confirmation rate to 0% while Compass continues operations. Should this chaining be monitored / halted after a few repetitive occurrences?

[GalRogozinski]

We should add alerts whenever the chaining happens

[jakubcech]

We should build a lambda on AWS. Parse Cloudwatch entrylines for both Compass and the signature server.

We should be more descriptive in the warnings emitted by Compass and the signature server and webhook on the alerts.