OpenTelemetry Echo by Labstack [otelecho]
OpenTelemetry Echo instrumentation allows developers to monitor and diagnose issues with their Echo applications, providing valuable insights into application behavior in production.
What is Echo?
Echo is a high performance, extensible, minimalist web framework for Go. It features a highly optimized HTTP router with zero dynamic memory allocations, making it one of the fastest Go web frameworks available.
Echo's key features include:
- Optimized router with zero dynamic memory allocation
- Middleware support with built-in middleware
- Data binding for JSON, XML, and form payloads
- HTTP/2 support
- Automatic TLS via Let's Encrypt
Echo's simplicity and performance make it a popular choice for building web applications and RESTful APIs in Go.
What is OpenTelemetry?
OpenTelemetry is an open-source observability framework that aims to standardize and simplify the collection, processing, and export of telemetry data from applications and systems.
OpenTelemetry supports multiple programming languages and platforms, making it suitable for a wide range of applications and environments.
OpenTelemetry enables developers to instrument their code and collect telemetry data, which can then be exported to various OpenTelemetry backends or observability platforms for analysis and visualization. The OpenTelemetry architecture provides a modular, vendor-neutral approach to observability.
Echo instrumentation
OpenTelemetry Echo instrumentation (otelecho) provides automatic tracing and metrics collection for your Echo applications. It captures HTTP request details, timing information, and error states without requiring manual instrumentation.
Note: Metrics support (WithMeterProvider, WithMetricAttributeFn, WithEchoMetricAttributeFn) requires otelecho v0.63.0 or later.
To install otelecho instrumentation:
go get go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho
Usage
You can instrument Echo router by installing OpenTelemetry middleware:
import (
"github.com/labstack/echo/v4"
"go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho"
)
func main() {
e := echo.New()
e.Use(otelecho.Middleware("my-service"))
e.GET("/users/:id", getUser)
e.Start(":8080")
}
Once instrumented, otelecho automatically creates spans for each incoming HTTP request, capturing method, route, status code, and timing information.
Middleware options
The otelecho middleware supports several configuration options:
| Option | Description |
|---|---|
WithTracerProvider | Use a custom TracerProvider instead of the global one |
WithMeterProvider | Use a custom MeterProvider instead of the global one |
WithPropagators | Specify propagators for extracting trace context |
WithSkipper | Skip tracing (return true to skip, false to trace) |
WithMetricAttributeFn | Extract custom attributes from http.Request for metrics |
WithEchoMetricAttributeFn | Extract custom attributes from echo.Context for metrics |
Skipping health checks
Use the WithSkipper option to exclude certain endpoints from tracing:
import (
"github.com/labstack/echo/v4"
"go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho"
)
e := echo.New()
e.Use(otelecho.Middleware("my-service",
otelecho.WithSkipper(func(c echo.Context) bool {
// Return true to skip, false to trace
return c.Path() == "/health" || c.Path() == "/ready"
}),
))
Custom tracer and meter providers
For more control over telemetry collection, you can specify custom providers:
import (
"github.com/labstack/echo/v4"
"go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho"
"go.opentelemetry.io/otel"
)
e := echo.New()
e.Use(otelecho.Middleware("my-service",
otelecho.WithTracerProvider(otel.GetTracerProvider()),
otelecho.WithMeterProvider(otel.GetMeterProvider()),
))
Adding custom attributes
Extract custom attributes from requests to enhance your metrics:
import (
"net/http"
"github.com/labstack/echo/v4"
"go.opentelemetry.io/contrib/instrumentation/github.com/labstack/echo/otelecho"
"go.opentelemetry.io/otel/attribute"
)
e := echo.New()
e.Use(otelecho.Middleware("my-service",
otelecho.WithMetricAttributeFn(func(r *http.Request) []attribute.KeyValue {
return []attribute.KeyValue{
attribute.String("http.client_ip", r.RemoteAddr),
attribute.String("http.user_agent", r.UserAgent()),
}
}),
))
HTTP metrics
Starting from v0.63.0, the otelecho middleware automatically collects the following HTTP server metrics:
| Metric | Description |
|---|---|
http.server.request.duration | Duration of HTTP server requests |
http.server.request.body.size | Size of HTTP server request bodies |
http.server.response.body.size | Size of HTTP server response bodies |
These metrics follow the OpenTelemetry semantic conventions for HTTP and include attributes like method, route, and status code.
What is Uptrace?
Uptrace is an OpenTelemetry APM that supports distributed tracing, metrics, and logs. You can use it to monitor applications and troubleshoot issues.

Uptrace comes with an intuitive query builder, rich dashboards, alerting rules with notifications, and integrations for most languages and frameworks.
Uptrace can process billions of spans and metrics on a single server and allows you to monitor your applications at 10x lower cost.
In just a few minutes, you can try Uptrace by visiting the cloud demo (no login required) or running it locally with Docker. The source code is available on GitHub.
What's next?
With OpenTelemetry Echo instrumentation in place, you can monitor request latency, track error rates, and trace requests across your distributed systems.
Next steps to enhance your observability:
- Add database instrumentation with GORM
- Create custom spans using the OpenTelemetry Go Tracing API
- Explore other Go frameworks like Gin or Beego
- Set up the OpenTelemetry Collector for production deployments