Coder deployments areconfigured with deployment-wide flags or environment variables (seecoder server --help). While this simplifies management, it can be difficult for new admins to see the features Coder has to offer, since they are hidden as CLI flags.

Let's add a view, only visible to admins and owners which shows various configuration options (OSS and enterprise), and whether the user has it turned on for their deployment. This can also be used as a form of a "health check."

Work has already started on this in#4138, but we can use this issue to discuss which features we should surface. We do not need to surface every CLI flag. Here are some ideas:

Deployment / Networking

Unsure if these should be separate sections

• Is the Coder tunnel enabled? What does the tunnel do?
• What is the Access URL
• maybe: Is it running on Docker, Kubernetes, system service, or other
• How many coderd replicas are running? (Enterprise)
• Is STUN enabled? What is STUN?
  • What STUN server(s) are being used
• What DERP servers are being used?
  • Internal vs external DERP servers
  • maybe: display dashboard<->DERP latency?
• Is SSH enabled? (enterprise can disable it,Enterprise feature: Ability for administrators to disable SSH for groups or site-wide #4131)

Provisioning

• How many provisioner daemons are running? What is the current queue?
• Are external provisioners connected? What are their names? (Enterprise)
  • This does not exist yet, seeAllow external provisioner daemons to register with Coder #44
• maybe: what common cloud(s) are provisionersauthenticated against?
  • e.g. Docker, AWS, Kubernetes, GCP
  • There was a concept floating around of "tags," perhaps these can be tags under the hood

Security

• Are secure-auth cookies enabled?
• What SSH keygen algorithm is used?
• maybe: Is TLS enabled? (direct vs reverse proxy on access URL)

Database status:

• Is external DB connected or is it using the built-in postgres
  • maybe: Location of built-in postgres (often `$/home/coder/.config/coderv2/postgres)
  • Probably best not to show the external db URL
• maybe: database latency?

Metrics / observability

• Is audit logging enabled? (Enterprise)
• Is Coder hooked up to Prometheus?
  • What popular data is surfaced via the Prometheus integration? Relateddocs: observability & prometheus #3520
• Is tracing enabled?
  • What kind of data is surfaced via tracing
• maybe: Is verbose logging enabled?
• Is pprof enabled?
  • What kind of data is surfaced via pprof?

Authentication

• Is username/password auth enabled
  • Can this be disabled yet?
• Is GitHub auth enabled?
  • Which GitHub URL (github.com or GitHub-enterprise.example.com)
  • Which GitHub organization(s) can access Coder?
  • Which GitHub teams(s) can access Coder?
• Is OIDC enabled?
  • Which OIDC provider(s) are added? (I believe we will be adding support for multiple inMultiple OAuth Git provider support #3078)
  • What scopes are users granted?

Telemetry

• Is telemetry enabled or disabled?
  • docs: describe our telemetry #2641 may change the behavior of telemetry states