HTTPErrorHandler stacktrace

[koi-tattoo]

Hello !

I am currently trying to report our API errors to the GCP error reporting service through echo's HTTPErrorHandler.

Here is the code I'm using to test this:

	e := echo.New()
	e.HTTPErrorHandler = func(err error, c echo.Context) {
		errorClient.Report(errorreporting.Entry{
			Error: err,
			Req:   c.Request(),
		})
		e.DefaultHTTPErrorHandler(err, c)
	}

The reporting in itself works perfectly, the issue is I am losing all the stacktrace information with this method, which is quiet essential to debug errors.

Here is an example stacktrace I receive on GCP (I filtered some information for privacy purposes) through the HTTPErrorHandler:

at main.main.func1 (...)
at github.com/labstack/echo/v4.(*context).Error ( /go/pkg/mod/github.com/labstack/echo/[email protected]/context.go:616 )
at github.com/labstack/echo/v4/middleware.GzipWithConfig.func1.1 ( /go/pkg/mod/github.com/labstack/echo/[email protected]/middleware/compress.go:98 )
at github.com/labstack/echo/v4.(*Echo).ServeHTTP ( /go/pkg/mod/github.com/labstack/echo/[email protected]/echo.go:662 )
at net/http.serverHandler.ServeHTTP ( /usr/local/go/src/net/http/server.go:2947 )
at net/http.(*conn).serve ( /usr/local/go/src/net/http/server.go:1991 )

So, I'm now wondering if there is still a way to use the HTTPErrorHandler and keeping the original stacktrace ? I'd rather not have to call errorClient.Report on every error in the application to keep it clean and easily maintainable.

I've also seen this issue but the only solution offered is to wrap errors to pack the stacktrace in it 😕 I'm asking again because the issue is from 5 years ago.

Thanks for any feedback !

[aldas]

The way handler/middleware chain works makes it not possible to have stacktrace as error value is returned - and calling methods/functions do not have in Go any mechanism of knowing what the method call stack was when that particular (error) object was created. unless the place that created what error encapsulates stacktrace there.

Basically you have to adopt Go way and let go of Java etc exceptions and their stacktraces or start initiating error objects with by embedding stack information at the time when that error object is created.

I think there is somewhere blogpost or something from Go authors that if you want something tracelike - start wrapping errors places where you handle them.