This would allow visibility into pricing and help optimize query patterns
You can now optionally see how long a query took, how many events where used, how many properties per event where used, and how many total properties where scanned.
To do so you just need to include the url query param: "include_metadata=true" in ad-hoc requests.
Detailed documentation is available at https://keen.io/docs/api/#execution-metadata
I think for the sake of backwards compatibility we would need to introduce an optional flag, e.g. "billing_metadata=true" that defaults to false.
Yea, this definitely seems beneficial for users. Any thoughts on implementation? As an optional flag ? or automatically for every request as response header ?