See parent feature for details.

The parent feature provides the following criteria to implement for this epic:

• Both agent and principal expose a metrics server on a configurable TCP port
• Metrics server can be enabled or disabled, with enabled being the default
• Metrics are exported in a widely understood format such as Prometheus metric data
• Installation manifests are exposing the metrics servers using services
• Initial set of described metrics is implemented in the code
• The go profiler (pprof) can be enabled or disabled, with disabled being the default
• Documentation exist on which metrics exist and how to interpret them
• Documentation exist on how to turn on/off the Go profiler and how to access it

These all seem perfectly reasonable, and I think as a team we've put a fair bit of work into implementing them already.

The only clarification I would add, is:

• 'Documentation' should be within https://github.com/argoproj-labs/argocd-agent/tree/main/docs. That is, this epic is NOT referring to OpenShift GitOps doc pages (e.g. on docs.redhat.com)