Monitoring proxy for time series data

appengine/chrome_infra_mon_proxy/queue.yaml

Index: appengine/chrome_infra_mon_proxy/queue.yaml
diff --git a/appengine/chrome_infra_mon_proxy/queue.yaml b/appengine/chrome_infra_mon_proxy/queue.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..ef0fad61dd84a6db0b779dba58ea6edd7a8f40c2
--- /dev/null
+++ b/appengine/chrome_infra_mon_proxy/queue.yaml
@@ -0,0 +1,28 @@
+total_storage_limit: 500M
+queue:
+- name: vm1
+  target: vm1
+  rate: 500/s
+  bucket_size: 100
+  max_concurrent_requests: 500
+  retry_parameters:
+    task_retry_limit: 0
+    task_age_limit: 1s

[ghost stip (do not use), 2015/04/14 00:36:43]

this is cool? we don't lose data because of this?

[Sergey Berezin (google), 2015/04/16 04:39:07]

We may, but with timeseries we'll lose data even on Monarch side.

In any case, my tests show that task queues are not appropriate for proxy, I'll
be removing this file altogether.

+
+- name: vm2
+  target: vm2
+  rate: 500/s
+  bucket_size: 100
+  max_concurrent_requests: 500
+  retry_parameters:
+    task_retry_limit: 0
+    task_age_limit: 1s
+
+- name: vm3
+  target: vm3
+  rate: 500/s
+  bucket_size: 100
+  max_concurrent_requests: 500
+  retry_parameters:
+    task_retry_limit: 0
+    task_age_limit: 1s