wxiaoguang 7069369e03

Support performance trace (#32973) ...

1. Add a OpenTelemetry-like shim-layer to collect traces
2. Add a simple builtin trace collector and exporter, end users could
download the diagnosis report to get the traces.

This PR's design is quite lightweight, no hard-dependency, and it is
easy to improve or remove. We can try it on gitea.com first to see
whether it works well, and fine tune the details.

---------

Co-authored-by: silverwind <me@silverwind.io>

2025-01-21 18:57:07 +00:00

..

middleware

Refactor request context (#32956)

2024-12-24 11:43:57 +08:00

routing

Support performance trace (#32973)

2025-01-21 18:57:07 +00:00

types

Refactor web package and context package (#25298)

2023-06-18 09:59:09 +02:00

handler.go

Prepare for support performance trace (#33286)

2025-01-15 20:05:18 +00:00

routemock_test.go

Refactor names (#31405)

2024-06-19 06:32:45 +08:00

routemock.go

Refactor names (#31405)

2024-06-19 06:32:45 +08:00

router_combo.go

Refactor arch route handlers (#32993)

2024-12-28 03:31:46 +00:00

router_path.go

Refactor package (routes and error handling, npm peer dependency) (#33111)

2025-01-06 22:45:20 +08:00

router_test.go

Refactor maven package registry (#33049)

2024-12-31 05:30:52 +00:00

router.go

Refactor arch route handlers (#32993)

2024-12-28 03:31:46 +00:00