Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm currently building an API and am looking for a tool to allow me to monitor (in a GUI) and rate-limit usage. I've come across a few enterprise solutions including:

The Apigee enterprise plan is exactly what I'm looking for but plans start at $3000 / month which is out of my price range. The other solutions are all either too expensive or do not provide the solution I'm looking for.

This led me to look at some open source options including:

Varnish seems like a fairly complete solution; however, I would need to build a GUI to visualise the data.

My final option would to build a solution from scratch using EventMachine and ruby.

Any advice?

share|improve this question

closed as off-topic by mgorven, mdpc, Dennis Kaarsemaker, Falcon Momot, Tim Brigham Jan 13 '14 at 18:12

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions seeking product, service, or learning material recommendations are off-topic because they tend to become obsolete quickly. Instead, describe your situation and the specific problem you're trying to solve." – mdpc, Dennis Kaarsemaker, Falcon Momot, Tim Brigham
If this question can be reworded to fit the rules in the help center, please edit the question.

Mike. I'm the developer of Api Axle. There's no visualisation of statistics but Axle comes with an API which should make it relatively easy to build one. Do ping me if you think I can be of help. – Phil Jackson Apr 12 '12 at 13:44
I haven't tested it but what about using nginx with redis and implementing this kind of algorithm – hellvinz Apr 25 '12 at 17:11

I think you overestimate how hard this is.

In your code just have a counter with redis/memcached/mongodb (1/24 hour counter or hourly/daily counter depending on your needs) and return the appropriate error when the limit has been met. You can either increment the counts right there, or do that asynchronously when processing your logs.

For showing the data, just make a simple web page summarizing the counts as needed.

For our use we don't need to limit things exactly, so we generally just log through our log infrastructure and one of the (real-time-ish through scribe) log processors will summarize this sort of thing. The output is a simple HTML page with the busy IPs/clients, some page that nagios can monitor and some URLs that munin pulls data from to make graphs.

share|improve this answer

You can use naxsi with nginx. just override your /requestDenied location with limit rules you need:

map naxsi redirect parameters to corresponding limit:

map $arg_uri $limit_uri {
  123.php   limit_zone1;
  234.php   limit_zone2;
default limit_default;

use limits in location:

 location /RequestDenied {
     limit_req $limit_uri;
share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.