Currently we log long-lived connections after they complete. This means there's no visibility into who is connecting or what endpoint they're hitting until they disconnect from the server cleanly or otherwise.

Every long-lived endpoint using WebSocket or SSE should be updated to trigger the request logging right after they've fully accepted the client and are ready to start streaming data. Usually this means right before the loopy part of the handler.

One customer is seeing a rise in pubsub subscriptions in Prometheus but there's no indication of who or why.

Relates to#16903 (same customer incident)

Implementation

I think we could add a context field with a pointer to a struct that contains a "fields" property for additional fields to log (for#16903), as well as aWriteLog(status int) method that immediately writes the logs.

typeRequestLoggerContextstruct {Fieldsmap[string]anylog slog.Loggerwrittenbool}func (c*RequestLoggerContext)WriteLog(statusint) {ifc.written {return  }// write the log with the extra fields...}// in the middleware:logContext:=&RequestLoggerContext{... }deferfunc() {  logContext.WriteLog(...)}()ctx=ctx.WithValue(logContextKey,logContext)next.ServeHTTP(r.WithContext(ctx),w)