[server] Introduce /debug/logging

[geropl]

Description

Introduces an endpoint for changing log levels at runtime, similar to the one introduced here.

Currently this is server-only. DebugApp can and should easily be moved to a common-ts package, but did not want to make this part of this PR.

Related Issue(s)

Context: #5551

How to test

1. kubectl port-forward deployment server 6060
2. curl localhost:6060/debug/logging -d '{"level":"info"}'

Release Notes

runtime configurable log-level for `server`

[svenefftinge]

Can't we just change the LOG_LEVEL on the deployment? Having an endpoint that mutates the state of one server instance (which one?) seems unnecessary, because restarts shouldn't be a problem with servers.

[geropl]

Can't we just change the LOG_LEVEL on the deployment? Having an endpoint that mutates the state of one server instance (which one?) seems unnecessary, because restarts shouldn't be a problem with servers.

Sadly restarts are a problem with servers: reconncets from dashboard and workspaces are not seemless, but lead to temporary unavailability.

Also, I don't feel that this endpoint adds a lot of complexity. And if shifts the whole debate around logging from "reduce amount of logging" to "improve quality of logging" (bc of the argument "zero cost loglevel switch"), which I really really like.

Furthermore, we should re-use DebugApp for ws-manage-bridge and payment-endpoint where we rather not restart as well.

[aledbf]

Having an endpoint that mutates the state of one server instance

That is not possible in Kubernetes. Any update to Deployments or Daemonsets updates all the pods and also implies reconnections due to the replacement of pods.

[aledbf]

/approve

[aledbf]

@geropl thank you for working on this ❤️

[aledbf]

/approve

[geropl]

The last force-pushes were conflict resolutions.

[aledbf]

/lgtm

[roboquat]

LGTM label has been added.

Git tree hash: 5bb286baa012e9ad6135b02c168f73bf7a6a0b2f

[roboquat]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: aledbf

Associated issue: #5551

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [aledbf]
• components/ee/db-sync/OWNERS
• components/ee/payment-endpoint/OWNERS
• components/gitpod-protocol/OWNERS
• components/server/OWNERS
• components/ws-manager-bridge/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment