Tyk 5.2: See everything with powerful new OpenTelemetry Tracing

We weren’t kidding when we said observability will be fundamental to getting the best from your APIs in 2024. Now, we’re backing that prediction up with a powerful new feature as part of Tyk 5.2: OpenTelemetry Tracing. Get ready for all sorts of data-driven insights into your APIs!

Tyk 5.2 also brings much-requested OpenAPI Specification (OAS) body transformations, per-endpoint timeouts for response caching and header management in Universal Data Graph. Time to roll up your sleeves and get under the hood of Tyk 5.2…

Empowering users with enhanced visibility 

Tyk’s powerful new feature, OpenTelemetry Tracing, delivers end-to-end visibility into API request processing. This facilitates plugin development, performance optimisation, error detection and troubleshooting.

Superior observability means you can take a proactive approach to root cause analysis, issue resolution, providing an enhanced user experience and optimising your API operations. Say goodbye to bad API observability and hello to improved trace information and comprehensive support.

Are you ready for the future of observability? With this empowering new OpenTelemetry Tracing included as standard from Tyk 5.2, we’ll be deprecating OpenTracing 12 months from now. Check out our comprehensive article on migrating from OpenTracing to OpenTelemetry for all you need to know.

Core API management updates

There are plenty of other features and tweaks to get excited about with Tyk 5.2. For one, we’re adding much-requested body transformations to Tyk OAS. You can now configure middleware for both request and response body transformations. As a Tyk Dashboard user, you can do so from within our simple and elegant API Designer tool.

We’re also adding the ability to reference the Tyk OAS API definition from within your custom Go Plugins, bringing them up to standard alongside those you might use with a Tyk Classic API.

And that’s not all. You can now configure per-endpoint timeouts for Tyk’s response cache. The result? Increased flexibility to tailor your APIs to your upstream services. While doing this, we’ve also fixed a longstanding issue within the Tyk Dashboard so that you can configure more of the advanced caching options from within the user interface (UI).

In the spirit of seeing more, we’ve also enhanced the licensing information page within the Tyk Dashboard UI so you can see your usage of licensed APIs, gateways and distributed data planes over time.

API as integration 

Another area we’ve focused on with Tyk 5.2 is the concept of header management in Universal Data Graph. With multiple upstream data sources, data graphs need to send the right headers upstream. This enables you to effectively track usage and enforce security rules at each stage.

All Universal Data Graph headers now have access to request context variables like JWT claims, IP address of the connecting client or request ID.

Finally, we’ve expanded support for WebSocket protocols between clients and Tyk Gateway. Instead of only supporting the graphql-ws protocol, which is becoming deprecated, we now also support graphql-transport-ws.

The Tyk team has been busily beavering away at these exciting changes, which we are confident will enable you to achieve even greater things with your APIs. Check out our full release notes (Tyk Gateway 5.2  and Tyk Dashboard 5.2) for more in-depth details, or connect with the team to chat about all the fabulous new features of Tyk 5.2.