The signer now exposes Prometheus metrics (avalanche-remote-signer PR #17): sign counters/histograms and signer_info{backend, public_key}. Nothing in this repo scrapes it, and the failure mode proven in e2e is silent (dead or mis-keyed signer leaves the node up with a broken identity).
Needed once the signer image with metrics ships:
monitoring.yml / prometheus role: scrape job for the signer metrics port on validator hosts (loopback bind means scraping via node-local exporter relay or binding metrics to the VPC interface; decide)- the two alerts that matter: signer target down, and
signer_info{public_key} != the operator's expected registered key
- enable
metrics-port in the remote_signer role config template + defaults
Depends on the org-registry image including the metrics feature.
The signer now exposes Prometheus metrics (avalanche-remote-signer PR #17): sign counters/histograms and
signer_info{backend, public_key}. Nothing in this repo scrapes it, and the failure mode proven in e2e is silent (dead or mis-keyed signer leaves the node up with a broken identity).Needed once the signer image with metrics ships:
monitoring.yml/ prometheus role: scrape job for the signer metrics port on validator hosts (loopback bind means scraping via node-local exporter relay or binding metrics to the VPC interface; decide)signer_info{public_key}!= the operator's expected registered keymetrics-portin the remote_signer role config template + defaultsDepends on the org-registry image including the metrics feature.