Record signatures origin in the signature processor

[turmelclem]

Content

We want to record the number of incoming signatures coming from the DMQ network. Once the DMQ is delivering enough signatures to reach the quorum, we will be able to sunset signature publication to the aggregator REST API.

• Extend the SignatureConsumer trait to expose the origin metric of the consumer
• increment the get_signature_registration_total_received_since_startup metric with the origin for every signature processed
• Modify usage of metric signature_registration_total_received_since_startup incremented in HTTP server when calling register-signatures with HTTP value instead of origin_tag
• remove usage of origin_tag header in register-signatures endpoint

Pre-submit checklist

• Branch
  • Tests are provided (if possible)
  • Crates versions are updated (if relevant)
  • CHANGELOG file is updated (if relevant)
  • Commit sequence broadly makes sense
  • Key commits have useful messages
• PR
  • All check jobs of the CI have succeeded
  • Self-reviewed the diff
  • Useful pull request description
  • Reviewer requested
• Documentation
  • Update README file (if relevant)
  • Update documentation website (if relevant)
  • Add dev blog post (if relevant)
  • Add ADR blog post or Dev ADR entry (if relevant)
  • No new TODOs introduced

Closes #2478

[github-actions]

Test Results

    3 files  ±0     77 suites  ±0   14m 41s ⏱️ -15s
1 913 tests ±0  1 913 ✅ ±0  0 💤 ±0  0 ❌ ±0 
3 225 runs  ±0  3 225 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 1d4de25. ± Comparison against base commit 090b7dc.

♻️ This comment has been updated with latest results.

[Copilot]

Pull Request Overview

This PR adds tracking of signature origins by injecting a MetricsService into the signature processor and labeling metrics with the consumer’s origin.

• Inject MetricsService into SequentialSignatureProcessor and increment a labeled counter per processed signature
• Extend SignatureConsumer with get_origin_network, update noop/fake implementations
• Update metrics definitions to use specific origin label constants and adjust HTTP routes/tests to use a fixed "HTTP" origin

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/services/signature_processor.rs	Inject and store metrics_service, record origin‐labeled metrics
src/services/signature_consumer/interface.rs	Add get_origin_network() to trait
src/services/signature_consumer/noop.rs	Implement get_origin_network() returning "NOOP"
src/services/signature_consumer/fake.rs	Implement get_origin_network() returning "FAKE"
src/metrics/service.rs	Define distinct origin label constants and update metric builders
src/http_server/routes/signatures_routes.rs	Remove dynamic origin header, hard-code "HTTP" for metrics
src/dependency_injection/builder/enablers/misc.rs	Pass metrics_service into SequentialSignatureProcessor::new

[dlachaume]

LGTM 👍

[jpraynaud]

LGTM 👍

[Alenar]

LGTM