tree ce1a0012aec431710fda60e6875a9858584177a3
parent 29e874a7719ce4e835e64092348c1fd6a08025cb
author Luca Milanesio <luca.milanesio@gmail.com> 1696968232 +0100
committer Luca Milanesio <luca.milanesio@gmail.com> 1697048433 +0000

Cover the replication failure scenario and fix the metrics

The failed replication fetch was silently dropping the event
without any possibility to detect the failure. Cover the missing
use-case and generate the task/failed metric whenever the
replication does not succeed.

Also consider a success when the replication event does not
result in any ref-specs, which isn't a failure but simply a NOOP.

Change-Id: I9bc6127d4f9e237772a43d787f8b862319e8d84c