What’s your API data telling you about your Web3 App? By lifting relevant information from your App’s API transactions and call logs, you can identify and proactively catch issues before they’re surfaced by your customers. Keep your customers happy and reduce churn - make your customer success team performant.
As you may know, event logs are a common feature in operating systems and other software that keep track of system and application errors. When you have API traffic to follow or front-end actions you want to watch, using Moesif’s Live Event Log is a simple way to filter and find the data you need.
Many API developers and companies struggle to find ways to set up systems to monetize their APIs easily. Some are simple but not customizable and some are complex and require massive engineering effort to actually get it all running. To make things easier, Moesif created the Billing Meters feature which gives massive customizability but with a minimal amount of code and engineering effort to monetize APIs.
Learn why most web apps and web services use REST (RESTful) APIs–and why GraphQL and gRPC APIs are emerging as alternatives to REST APIs in a growing number of organizations. Most web traffic today is actually API traffic for web applications and REST web services.
Today, API-driven microservices applications are a source of speed to innovation and competitive advantage – according to SmartBear’s most recent State of Software Quality – API report: However, this modern way of architecting software doesn’t come without challenges. Neglecting to adapt a new approach to service architecture design with a new approach to the underpinnings – API design and testing – can undermine the efforts.
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.
