Eric J. Smith

Yeah, I'm really not sure how this would work. I don't want people to have to configure this and I don't want to have a ton of options. So I'm...

So the problem with this is that the majority of cost associated to accounts is the bandwidth and initial processing of the request. Our current policy is that we will...

To your original feedback, I think sending an email letting you know when we throttle your account and including data showing you why it got throttled would be really good....

@romanych we currently throttle you for those exact reasons so that 1 event like your redis server going down doesn't eat up all of your events for the months. I...

Current thoughts are this. 1. Add support for an EventRate header that gets returned from the event post API. This would tell the client to limit it's events to X...

I'm worried about us adding more features vs improving the ones that we do have, but maybe there is something simple that we can do. How would you see this...

If you just want counters, then we basically give you that ability now with being able to report events and then chart occurrences of those events over time. But timings...

I have been thinking about this some more and I think I have some ideas on how we can do it easily. - Add new event types for counter, gauge,...

I think it would be hard for us to have the events pipeline be completely stream based, but I wonder if we could have the reader be stream based and...

We don't currently have the ability to do that, but I like the idea. Do you want to submit a PR to add that ability? The exclusions are implemented here:...