Keep service/route name when the entity is deleted
What: When a service/route is deleted from the platform, the name can no longer be seen in Analytics reports which creates confusion when running Reports and analysis around usage.
What: Allow me to click on specific entities, or data points, within the chart preview to create a new filter. That would reduce the number of clicks I need to do and I can much quicker create what I need. Why: Today when I create a new custom rep...
Human-friendly date/time format inside the exported CSV
What: When you export a custom report into a CSV, the result includes a column for timestamp which is currently shown as a unix timestamp. A more human-friendly date-time format would be better so that users avoid having to convert this all the time.
Provide "KSearch-like" experience for API Requests
What: API Requests now provides users the ability to enter key:value strings into a textbox to add filters instead of the current click-modal-badge experience. (image only represents the idea and the final product may look different) It's importan...
What: Users are able to organize custom reports so it is easier to access common reports. Possible options we could think about: Favourite custom reports. Introduce folders and put custom reports underneath them. Why: As the number of reports incr...
Provide a way to filter out deleted entities from Konnect reports
What: When a lot of deleted entities exist, it makes reviewing reports on active services very difficult. It would help to have a way to filter out deleted services (also a way to only see deleted services as well).
What: I want to sort requests in the API Requests feature based on a metric like kong latency or request latency so that I can pull up the slowest requests and then look at their traces
What: As a Konnect customer I would like to be able to create custom report based on the the Geo, City, Country, ASN where the traffic is originating from. This allow for better visibility into the client traffic, capacity planning and etc...
What: Customers would like insight into the health of their Kong dataplanes nodes to determine the health of their deployments. For example, average, peak CPU/memory utilization would be useful.