3 Commits

Author	SHA1	Message	Date
Lunny Xiao	d782cad7f8	Add start time on perf trace because it seems some steps haven't been recorded. (#35282) ... The new trace log looks like ``` http start=2025-08-14 15:03:04 duration=0.6978s http.route=/ http.func start=2025-08-14 15:03:04 duration=0.6978s func=common.ForwardedHeadersHandler.ForwardedHeaders http.func start=2025-08-14 15:03:04 duration=0.6978s func=routing.(*requestRecordsManager).handler-fm http.func start=2025-08-14 15:03:04 duration=0.6978s func=gzhttp.NewWrapper http.func start=2025-08-14 15:03:04 duration=0.6975s func=session.Sessioner http.func start=2025-08-14 15:03:04 duration=0.6973s func=context.Contexter ```	2025-08-18 15:17:19 +00:00
TheFox0x7	2a59dfbd47	enable staticcheck QFxxxx rules (#34064)	2025-03-29 17:32:28 -04:00
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