3 ms·
We're looking at a similar challenge. Rather than gate limiting a feature, we want to gate limit debug logging per customer. Currently looking at a way to injec
by bberenberg 5y ago
We're looking at a similar challenge. Rather than gate limiting a feature, we want to gate limit debug logging per customer. Currently looking at a way to inject a customer identifier into debug code using a tool like LaunchDarkly or GrowthBook. They seem to support injection of arbitrary variables.
- sssslyz 5y agoI may be wrong here but I don't think LaunchDarkly or GrowthBook are suitable tools for this use-case. If you are already on them, sure, you could do a hack and slap on your customer ID. This only gets metadata onto the event. You would still need to follow up with: periodically extracting the data, aggregating the counts by user and writing custom code to gate your users. I would definitely consider 'debug logging limits per customer' as a product feature, and it's a perfect use-case for a tool like Limiter. Let me know if you want to give it a shot. I can work with you to refine it till it's fit for your production needs in return for a testimonial :)