redacted and full telemetry servers

[liamaharon]

• Creates a new module server inside live_builder
  • Server exposes a single fn start, which starts an actix server on the given port
  • Initial server implementation just exposes one route /health that responds 200
• Adds new base config item live_builder_server_port
• Server is spawned when running the live_builder cli

Background

• TDX builders cannot expose the existing telemetry server port, due to concerns about sensitive operational information leakage. This information may require a time-delay or additional sanitisation before being exposed outside of the secure machine.
• TDX builders require some other means to know if the builder is healthy or not.

Solution

• Separated the telemetry server into two servers: full and redacted.
  • full: what we have now, exposes all operational data without regard for whether it is sensitive
  • redacted: new server that initially only exposes a healthcheck endpoint (can be extended later). This server is safe to always be exposed by tdx builders.

[github-actions]

Benchmark results for 46c3067

Report: https://flashbots-rbuilder-ci-stats.s3.us-east-2.amazonaws.com/benchmark/46c3067-ccf4677/report/index.html

Date (UTC)	2024-09-10T17:58:25+00:00
Commit	46c3067084f337085df042b5ef87b4ab1d52c429
Base SHA	ccf4677ba3aa8cc1b50e14b6bda4947322ee48a2

Significant changes

Benchmark	Mean	Status
MEV-Boost SubmitBlock serialization/JSON encoding	64.95%	Performance has degraded.

[dvush]

We already have server that you can hook on that serves telemetry + other debug endpoints we can add health endpoint there too. What is the justification for not using it and for adding additional server instead?

[ZanCorDX]

The names opaque_server/debug_server tells me nothing. I liked more "telemetry".
Maybe full_telemetry and health_check (or redacted_telemetry)?