Skip to content

Quota Service

Demo quota service, geared for a log collection usecase (but can be easily applied for similar needs elsewhere too).

This is a HTTP application running alongside an example log receiver setup (logs in via TCP -> tremor -> elastic out), that allows operators to easily (and quickly) update the throttling rates for various classes of logs. It also allows retrieving the current quotas for all classes, which can potentially be used by logging clients to pre-throttle on their end, even before transmitting the logs to tremor (or the information can be used to always provide up-to-date quota limits to folks using this log platform).

The application itself is written on top of tremor, utilizing the linked transports feature introduced as part of tremor v0.9.



All the application code here is available from the docs git repository.

# needed for elasticsearch container to start successfully
sudo sysctl -w vm.max_map_count=262144

# start everything (tremor/elasticsearch/kibana)
docker-compose up

Following services should now be accessible:

Log Ingestion

# send logs periodically to the tcp log receiver port (powered by tremor)
./ | nc localhost 12202

You should now see an elasticsearch index (test_logs) being created with the logs. Example:

$ curl localhost:9200/_cat/indices
yellow open test_logs xtdBODqGQ7Gub1PfUlcaWA 5 1 788 0  139kb  139kb

You can also inspect/visualize the logs from kibana. Create an index pattern here (eg: test_logs*), choosing ingestion_timestamp as the time field -- this allows timeseries navigation in the Discover page as the logs are ingested (useful since we are replaying old log data dump).

Using the Quota Service

List routes

$ curl http://localhost:8139

      Welcome to the Logging Quota Service!

      Available routes:

      GET /quotas
      POST /quotas
      POST /flush

      HEAD /ping
      GET /stats


Get quotas

# populated from file etc/tremor/data/quotas.json on startup
# output is keyed by class name (the details of the classification are defined in etc/tremor/config/logs.trickle)
$ curl -XGET localhost:8139/quotas


Set quotas

# set rate for tremolo class of logs to 1 message per second
# returns the overall quotas state on success
$ curl -XPOST -H'Content-Type: application/json' http://localhost:8139/quotas -d'{"tremolo": 1}'


# If you are monitoring the tremolo logs from kibana, you should now see the (debug) field `tremor_class_rate` change to 1 (from 100).
# More importantly, the log volume visible there should have also decreased.

# to remove the rate override for tremolo (i.e. switch to the default, hard-coded rate for it)
# curl -XPOST -H'Content-Type: application/json' http://localhost:8139/quotas -d'{"tremolo": null}'

Example kibana view demonstrating the change in number of tremolo logs, after setting the quota dynamically from the above api:

Kibana View for Quota Service Demo

Flush quotas

# force save of quotas to disk as well as publishing of quotas to any other pipelines present.
# both actions are handled on quota updates as well -- this path is there in case manual flush is needed.
# returns 202 if the request was succesfully accepted, along with overall quotas state.
$ curl -XPOST http://localhost:8139/flush


# to load the saved quotas during tremor restart, we need to do the following before tremor restarts right now:
sudo cp etc/tremor/data/ etc/tremor/data/quotas.json
# and after startup, run the flush once more

Debug request

$ curl -XPOST localhost:8139/echo -d'{"snot": "badger"}'

{"body":"{\"snot\": \"badger\"}","meta":{"method":"POST","headers":{"content-length":["18"],"content-type":["application/x-www-form-urlencoded"],"user-agent":["curl/7.65.3"],"accept":["*/*"],"host":["localhost:8139"]},"url":{"scheme":"http","host":"localhost","port":8139,"path":"/echo"}}}