Customer would like to see an API interface to report MTK consumption by flags. Quote from customer: "This will allow us to programmatically track and alert on unexpected MTK increases and take prompt actions. Today even the Harness team doesn’t have a direct way to generate the report and has to rely on their backend infra team to do it. - the impact is that we often get surprised when the MTK usage shows a spike, potentially breaching our contracted allowance. There’s a lot of manual overhead today to stay on top of the MTK usage as there’s no way to tell which flags were causing the spikes."

Enhancement to the product's usage reporting capabilities, specifically for Monthly Tracked Keys (MTKs). The goal is to provide engineering and product teams with direct visibility into which Feature Flags (FFs) are consuming the highest volume of MTKs. This information should be easily accessible, ideally within the existing product dashboard or via an automated notification mechanism, to allow teams to proactively manage usage and prevent unexpected overages without manual reports.

We are modeling the MTK reduction and many teams are able to do a good amount of clean up still, but we are not able to tell whether the MTK dropped enough. We definitely appreciate the manual report you can help pulling but if the console is the only way to get the data and the iteration cycle is monthly, it won’t be something really actionable.

Customer would like to have increased visibility into their MTK and Event volumes and be alerted if they start to approach entitlements or significantly drop below the average volumes they see.

For example: they would like to be able to send over an api call to see "since yesterday how many lead events did you receive".

They would also like to see MTKs broken down by flags so they can track traffic more granularly.

Would like to have an MTK report that is by owner/groups. They want to know which owners/groups are the worst offenders and put those folks on an MTK diet when needed.

Customer, among many others, are desperate for greater visibility into their usage, similar to the MTK and Events reports support pulls for CSMs daily. Being able to associate details by FF would be helpful as well.

Customer would like to be able to more granularly monitor their MTKs. They would like to have self-service options for getting the visibility they see from the MTK reports that we can request and share with them. Ideally they would want to be able to see MTKs broken down by flags, by traffic types, and also be able to get notified when they reach their MTK entitlement.

Customer has recently added 80M MTKs for 100M MTKs total but they are losing confidence in their ability to predict volumes which has been escalated in their org.