As an application developer, have you ever had to troubleshoot an issue that only happens in production? Bugs can occur when your application gets released into the wild, and they can be extremely difficult to debug when you cannot reproduce without production data. In this blog, I am going to show you how to safely send your production data to development applications deployed using a service mesh to help you better debug and build production proof releases.

Kong connects APIs and microservices natively within clouds, data centers, and Kubernetes platforms using intelligent automation. Built on an open source core, Kong’s solutions enable digital innovation by allowing organizations to reliably and securely manage the full lifecycle of APIs for legacy as well as modern architectures, including container runtimes and serverless technologies.

For the third consecutive year, we’re happy to announce that Kong has been recognized as a Leader in the Gartner Magic Quadrant for Full Life Cycle API Management and is positioned furthest to the right for Completeness of Vision. This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document.

Observability is a critical part of Kong’s API Gateway. In this post, we’ll describe two options to monitor Kong Gateway using Prometheus. Prometheus is an open source system monitor toolkit built at SoundCloud that is now widely adopted. StatsD was originally a simple daemon developed by Etsy to aggregate and summarize application metrics. Prometheus provides a StatsD exporter to collect metrics that are sent in StatsD format.

Today we’re excited to announce the release of Kong Mesh and Kuma 2.0. With this new major release, we’re announcing the first availability of our next-generation policies, in addition to new eBPF capabilities. 2.0 is also significant as we have unified the version scheme between Kong Mesh and Kuma. Previously, Kuma versions had an n-1 version naming convention when compared with Kong Mesh.

As a Solutions Engineer here at Kong, one question that frequently comes across my desk is “how can I transform a Kong logging plugin message into a format that my insert-observability-stack-here understands, i.e. ELK, Loki, Splunk, etc.?” In this blog, I’m going to show you how to easily accomplish converting a Kong logging payload to the Elastic Common Schema. In order to accomplish this task, we’re going to be running Kong Gateway in Kubernetes and using two Kong plugins.

A common use case that is frequently requested is how to dynamically route requests based on authentication attributes. An example of this technique is routing requests to relevant upstream services based on claims contained in a JWT token. Admins would like all their clients to go to the same URI as it makes the implementation easier. But behind the scenes they might need to tailor specific configuration/applications for them, hence routing their request based on their identity.

From time to time, Kong’s Brad Drysdale and Ahmed Koshok exchange emails about the latest trends in tech. In this exchange, Brad and Ahmed discuss the continued quest for more innovation faster, the role of automation in API strategy, and more. from: Brad to: Ahmed date: Oct. 29, 2022, 6:58 PM subject: Elements for Building Cloud Native Applications Greetings from Australia, Ahmed!

We’re excited to announce new features in Kong Konnect, including the ability to take advantage of identity management APIs, streamlined certificate management, and latency metrics as part of Analytics. Read on to learn about these features and how kong helps future-proof API security.