Qpoint’s Post

Transcript

Welcome to the Winter 2024 Keypoint Interface update. We've delivered a slurry of new capabilities that make the platform more valuable than ever. Let's take a look. We'll start with the new landing page, which gives you instant visibility into your API ecosystem through key metrics such as total average availability across services, total number of recorded API issues, total requests and connections. Bandwidth usage both sent and received. As well as request duration, both average and percentile. Next, let's do a deep dive on the new Inventory tab. This is the vengers view which gives you an overview showing all of your external API providers. Key metrics that we provide have been enhanced to include things like connections by descent, bytes received, errors, availability, and average duration. Clicking on a vendor. We get a drill down into what endpoints are being called the clients. In this case we have 4 different languages and the API tokens that are associated with those endpoints. The vendor view is designed to give you a sense of everything that your services are communicating with. The client view is designed to tell you what services are generating those outbound queries. We can see which clients are responsible for generating the outbound traffic. We can define clients by things like binary host, IP, container, pod etc etc. For example, if I wanted to see which outbound requests were stemming from our Java application here, I could see which vendors Java was talking to, as well as which API tokens are associated with this communication. Lastly, let's take a look at the API token functionality. Here, I'm going to pick a specific endpoint filter. For that, we can see what API tokens were associated with these particular endpoints, both by mask and by hash. We can see how much data was sent and received, the status as well as the number projections. Now the last major update, we've unified filtering across the entire platform. We can filter by any number of parameters. These are stackable. So for example, if I wanted to filter for a particular language in particular container, I can do that and then traverse across to the tried and true traffic page as well as the connection page. This is a game changer for troubleshooting and analysis workflows. This means you can start investigating an issue in traffic and jump to the inventory tab to see impacted. Vendors See what API tokens are associated with that traffic. See which clients. It's a great way to troubleshoot and analyze. Now I'm trying to keep this short and sweet. There's a lot I didn't get to cover. If you'd like to see more, go ahead and reach out to us at hello at Q point dot IO. Thank you so much for your time and have a great day.