Issue 3261 - Introduce module adblockplus::telemetry

hiera/roles/telemetryserver.yaml

Index: hiera/roles/telemetryserver.yaml
diff --git a/hiera/roles/telemetryserver.yaml b/hiera/roles/telemetryserver.yaml
new file mode 100644
index 0000000000000000000000000000000000000000..f155a5a8fb3219e716ba13e892798b4e2ab0d560
--- /dev/null
+++ b/hiera/roles/telemetryserver.yaml
@@ -0,0 +1,8 @@
+classes:
+  adblockplus::telemetry:
+    domain: "telemetry.adblockplus.org"
+
+adblockplus::telemetry::endpoints:
+  filter_hit_statistics:
+    location: /submit/filter-hit-statistics

[mathias, 2015/11/03 10:34:53]

Note that this location conflicts with the one initially suggested (/submit)
which, however, does not make much sense in the context of an explicit
telemetry.adblockplus.org domain which may host multiple endpoints - alongside
some other stuff - in the future.

To name a particular example: It could make sense to move the Adblock Browser
feedback endpoint to the telemetry.adblockplus.org domain as well, i.e.
/submit/adblock-browser-feedback. The current endpoint at adblockbrowser.org
could become a forwarding proxy until it does not receive requests any more.

[Felix Dahlke, 2015/11/10 15:29:14]

Well, feedback and telemetry are quite different things, I'd prefer to keep this
separated. If we were to combine it I think we would need a more generic
umbrella, e.g. "submit.adblockplus.org". (IIRC, Mozilla has "api.mozilla.org"
for a similar purpose.)

Also: How I remember the discussion, we would send _all_ telemetry data within
that one JSON, i.e. "/submit" seems fine. But let's double check that that's
really how we discussed it should work.

+