Skip to main content
The Go SDK now uses OpenTelemetry to collect and send metrics, logs, and traces.
Request logging and tracing are now enabled by default. If you previously used the SDK for metrics only, set SampleRate = 0 to keep that behavior.

Installation and setup

The updated setup guides provide the installation steps and initialization code for each framework. Follow these to replace your existing SDK integration. The SDK now requires Go 1.25 or later. The Gin module has been renamed from github.com/apitally/apitally-go/gin to github.com/apitally/apitally-go/gin-v1. Update your imports and remove the old module with go mod tidy.

Write tokens replace client IDs

The SDK now authenticates with a write token instead of a client ID. Your existing app’s token (apt_...) is available under Setup instructions in the Apitally dashboard. NewConfig() no longer takes a client ID. Set the WriteToken option, or set the APITALLY_WRITE_TOKEN environment variable. A missing or invalid token no longer fails silently in the background. Instead, the SDK logs an error and disables itself.

Init replaces the middleware

Replace the Middleware registration with a call to Init, which registers everything the SDK needs. Call it after your recovery middleware and OpenTelemetry HTTP instrumentation, and before your other middleware, groups and routes.

Graceful shutdown

Call the new apitally.Shutdown function when your application exits, after your HTTP server has stopped, so the SDK can deliver the remaining telemetry. The setup guides show the full pattern.

Configuration changes

The RequestLoggingConfig type and the RequestLogging field have been removed. Their settings are now fields directly on Config, with the option changes listed below.

Changed options

The following options have been changed:
OptionChange
ClientIDReplaced by WriteToken, which requires a new credential.
EnvCan now also be set with the APITALLY_ENV environment variable.
RequestLogging.LogRequestHeadersRenamed to CaptureRequestHeaders.
RequestLogging.LogRequestBodyRenamed to CaptureRequestBody.
RequestLogging.LogResponseHeadersRenamed to CaptureResponseHeaders.
RequestLogging.LogResponseBodyRenamed to CaptureResponseBody.
RequestLogging.MaskQueryParamsMoved to MaskQueryParams, now []string.
RequestLogging.MaskHeadersMoved to MaskHeaders, now []string.
RequestLogging.MaskBodyFieldsMoved to MaskBodyFields, now []string.
RequestLogging.ExcludePathsMoved to ExcludePaths, now []string. Matches actual request paths instead of matched route patterns.
RequestLogging.MaskRequestBodyCallbackMoved to MaskRequestBody with new arguments.
RequestLogging.MaskResponseBodyCallbackMoved to MaskResponseBody with new arguments.
RequestLogging.ExcludeCallbackReplaced by SampleOnRequest or SampleOnResponse with new arguments and return values.
Pattern options now take regular expressions as strings instead of *regexp.Regexp values. They are matched case-insensitively unless a pattern sets its own flags, such as (?-i:...).

Removed options

These options have been removed:
Removed optionMigration
RequestLoggingSet its fields directly on Config, applying the changes above. Remove its Enabled flag.
RequestLogging.Enabled and
RequestLogging.CaptureTraces
Previously defaulted to false. Request logging and tracing are now enabled by default. Use SampleRate = 0 to disable request logs and traces.
RequestLogging.LogQueryParamsQuery parameters are now always captured. To mask all values, use .
RequestLogging.CaptureLogsLogs are captured when you wrap your log/slog handler with NewSlogHandler (see below).
RequestLogging.LogPanicPanics are now always captured in request traces.
DisableSyncUse the Disabled option or the APITALLY_DISABLED environment variable. Apitally is also disabled in go test binaries.
The configuration reference lists all available options.

Consumer identification

The request helpers, such as SetConsumer(), now take a context.Context instead of the framework’s request or context type. This changes the call sites on Echo, Fiber v2 and Chi: SetConsumerIdentifier has been removed. Use SetConsumer with only the Identifier field set.
You can also provide custom attributes for each consumer:

Validation errors

CaptureValidationError has been removed. Pass validation errors to CaptureError with the request context instead. See request context for the context to pass on each framework.

Application logs

The SDK no longer wraps the default log/slog handler automatically. To capture logs, wrap your handler with NewSlogHandler and log with the request context, for example with slog.InfoContext:
Records logged without the request context are not linked to requests and are not captured. See request context for the context to pass on each framework.

Body masking callbacks

MaskRequestBodyCallback and MaskResponseBodyCallback are now named MaskRequestBody and MaskResponseBody. Both receive (span, body), rather than the Request and Response objects. The body is passed as []byte after decompression. Callbacks may run later on another goroutine against an ended span. Request metadata is available through span.Attributes(). For example, a callback that masks bodies for admin routes becomes:

Request exclusion

Use sampling callbacks to exclude requests: SampleOnRequest for early decisions based on the request, or SampleOnResponse for decisions based on the response status or consumer. Both receive the span as their only argument. The callbacks should return 1, true to capture the request, and 0, true to exclude it. Callbacks can also return any probability between 0 and 1. Returning false as the second value from SampleOnRequest applies SampleRate, and from SampleOnResponse preserves the earlier sampling decision. For example, to capture only error responses:
Replace the ExcludeCallback option with the appropriate sampling callback. Note that captured headers and bodies are not available in sampling callbacks. Sampling affects request logs and traces, but not metrics. See sampling for details.

Path exclusions

ExcludePaths now matches request paths rather than matched route patterns. If a pattern contains route parameters, update it to match concrete values. For example, replace ^/users/:id$ with ^/users/[^/]+$ to match /users/123.

Existing OpenTelemetry setups

If your application registers a tracer provider from go.opentelemetry.io/otel/sdk/trace with otel.SetTracerProvider before starting the server, the SDK automatically adds its span processor. No manual registration is required. Review these settings when upgrading:
  • Sampling: Previously, your provider’s sampler affected traces but not Apitally’s request logs. It now affects both. Check that its sampling rate provides the request log coverage you want. Metrics remain unsampled.

Other changes

  • Network access: The SDK now sends data to otlp.apitally.io instead of hub.apitally.io. Update firewall allowlists if necessary.
  • Removed types: The ApitallyMiddleware, ApitallyConfig and ApitallyConsumer aliases and the Request and Response types have been removed from the public API.