Remove some old registry files from 0.1?
Change-Id: Ie89408761fc7359dea921cab040295ff40085deb
Reviewed-on: https://fuchsia-review.googlesource.com/c/cobalt/+/733489
Commit-Queue: Auto-Submit <auto-submit@fuchsia-infra.iam.gserviceaccount.com>
Fuchsia-Auto-Submit: Cameron Dale <camrdale@google.com>
Reviewed-by: Zach Bush <zmbush@google.com>
diff --git a/src/registry/demo/README.md b/src/registry/demo/README.md
deleted file mode 100644
index 6ea1def..0000000
--- a/src/registry/demo/README.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Cobalt Demo Config Registration Files
-
-These config registration files are used for a few purposes:
-* Manually doing an end-to-end demo of Cobalt.
-* Running the automated end-to-end tests
-* Running the continuous in-the-cloud test.
-
-There are therefore a few places in the code base that have been hard-coded
-to expect particular contents of these files. If you make any changes to
-these files you must synchronize your changes with the following code
-locations:
-
-* end_to_end_tests/cobalt_e2e_test.go
-* tools/demo/demo_reporter.py
diff --git a/src/registry/demo/registered_encodings.txt b/src/registry/demo/registered_encodings.txt
deleted file mode 100644
index 545e4f3..0000000
--- a/src/registry/demo/registered_encodings.txt
+++ /dev/null
@@ -1,133 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of EncodingConfigs
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new EncodingConfig or change
-# the definition of an EncodingConfig, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredEncodings Protocol Buffer message, which is defined in
-# encodings.proto
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-## Project 1
-
-#### Encoding (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- forculus {
- threshold: 20
- epoch_type: DAY
- }
-}
-
-#### Encoding (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- basic_rappor {
- prob_0_becomes_1: 0.1
- prob_1_stays_1: 0.9
- int_range_categories: {
- first: 0
- last: 23
- }
- }
-}
-
-#### Encoding (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- basic_rappor {
- prob_0_becomes_1: 0.01
- prob_1_stays_1: 0.99
- string_categories: {
- category: "apple"
- category: "banana"
- category: "cantaloupe"
- }
- }
-}
-
-#### Encoding (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- basic_rappor {
- prob_0_becomes_1: 0.2
- prob_1_stays_1: 0.8
- int_range_categories: {
- first: 0
- last: 10
- }
- }
-}
-
-#### Encoding (1, 1, 5)
-element {
- customer_id: 1
- project_id: 1
- id: 5
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- indexed_categories: {
- num_categories: 100
- }
- }
-}
-
-# Encoding (1, 1, 6) is the No-Op encoding.
-element {
- customer_id: 1
- project_id: 1
- id: 6
- no_op_encoding {
- }
-}
-
-#########################
-# Customer 2 (Acme)
-########################
-
-## Project 1
-
-#### Encoding (2, 1, 1)
-element {
- customer_id: 2
- project_id: 1
- id: 1
- # Note that a candidate set for this RAPPOR encoding is specified
- # in ReportConfig (2, 1, 1)
- rappor {
- num_bloom_bits: 64
- num_hashes: 2
- num_cohorts: 100
- prob_0_becomes_1: 0.2
- prob_1_stays_1: 0.8
- }
-}
-
-#### Encoding (2, 1, 2)
-element {
- customer_id: 2
- project_id: 1
- id: 2
- forculus {
- threshold: 50
- }
-}
-
diff --git a/src/registry/demo/registered_metrics.txt b/src/registry/demo/registered_metrics.txt
deleted file mode 100644
index 3a7dedc..0000000
--- a/src/registry/demo/registered_metrics.txt
+++ /dev/null
@@ -1,167 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of Metrics
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new Metric or change
-# the definition of a Metric, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredMetrics Protocol Buffer message, which is defined in
-# metrics.proto
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-## Project 1
-
-#### Metric (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuchsia Popular URLs"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "url"
- value {
- description: "A URL."
- data_type: STRING
- }
- }
-}
-
-#### Metric (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- name: "Fuschsia Usage by Hour"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "hour"
- value {
- description: "An integer from 0 to 23 representing the hour of the day."
- data_type: INT
- }
- }
-}
-
-#### Metric (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- name: "Fuschsia Fruit Consumption and Rating"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "fruit"
- value {
- description: "The name of a fruit that was consumed."
- }
- }
- parts {
- key: "rating"
- value {
- description: "An integer from 0 to 10"
- data_type: INT
- }
- }
-}
-
-#### Metric (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- name: "Rare Events"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "event"
- value {
- description: "The index of a rare event. See report config (1,1,4) for the labels corresponding to each index."
- data_type: INDEX
- }
- }
-}
-
-#### Metric (1, 1, 5)
-element {
- customer_id: 1
- project_id: 1
- id: 5
- name: "Fuchsia Module Usage"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "module"
- value {
- description: "A module identifier"
- data_type: STRING
- }
- }
-}
-
-#### Metric (1, 1, 6)
-element {
- customer_id: 1
- project_id: 1
- id: 6
- name: "Device Type"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "device"
- value {
- description: "Which type of device is Fuchsia running on"
- data_type: INDEX
- }
- }
-}
-
-#########################
-# Customer 2 (Acme)
-########################
-
-## Project 1
-
-#### Metric (2, 1, 1)
-element {
- customer_id: 2
- project_id: 1
- id: 1
- name: "Acme Module name"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "name"
- value {
- description: "The name of a module."
- data_type: STRING
- }
- }
-}
-
-#### Metric (2, 1, 2)
-element {
- customer_id: 2
- project_id: 1
- id: 2
- name: "Acme Popular URLs"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: UTC
- parts {
- key: "url"
- value {
- description: "A URL."
- }
- }
-}
diff --git a/src/registry/demo/registered_reports.txt b/src/registry/demo/registered_reports.txt
deleted file mode 100644
index dfaef5b..0000000
--- a/src/registry/demo/registered_reports.txt
+++ /dev/null
@@ -1,203 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of ReportConfigs
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new ReportConfig or change
-# the definition of an ReportConfig, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredReports Protocol Buffer message, which is defined in
-# report_configs.proto.
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-#########################
-
-## Project 1
-
-#### ReportConfig (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuchsia Popular URLs"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 1
- variable {
- metric_part: "url"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-test1-rudominer"
- }
- }
-}
-
-#### ReportConfig (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- name: "Fuchsia Usage by Hour"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 2
- variable {
- metric_part: "hour"
- }
-}
-
-#### ReportConfig (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- name: "Fuchsia Fruit Consumption and Rating Joint Analysis"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- variable {
- metric_part: "fruit"
- }
- variable {
- metric_part: "rating"
- }
-}
-
-#### ReportConfig (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- name: "Fuschsia Daily System Event Counts"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 4
- variable {
- metric_part: "event"
- index_labels {
- labels {
- key: 0
- value: "Event A"
- }
- labels {
- key: 1
- value: "Event B"
- }
- labels {
- key: 25
- value: "Event Z"
- }
- }
- }
-}
-
-#### ReportConfig (1, 1, 5)
-element {
- customer_id: 1
- project_id: 1
- id: 5
- name: "Fuchsia Module Usage"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 5
- variable {
- metric_part: "module"
- }
-}
-
-#### ReportConfig (1, 1, 6)
-element {
- customer_id: 1
- project_id: 1
- id: 6
- name: "Fuschsia Device Start Counts"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 6
- variable {
- metric_part: "device"
- index_labels {
- labels {
- key: 0
- value: "Type A"
- }
- labels {
- key: 1
- value: "Type B"
- }
- labels {
- key: 25
- value: "Type Z"
- }
- }
- }
-}
-
-#### ReportConfig (1, 1, 7)
-element {
- customer_id: 1
- project_id: 1
- id: 7
- name: "Fuchsia Daily Fruit Rating"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- report_type: RAW_DUMP
- variable {
- metric_part: "fruit"
- }
- variable {
- metric_part: "rating"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-test1-rudominer"
- }
- }
-}
-
-#########################
-# Customer 2 (Acme)
-########################
-
-## Project 1
-
-#### ReportConfig (2, 1, 1)
-element {
- customer_id: 2
- project_id: 1
- id: 1
- name: "Acme Module Names"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 1
- variable {
- metric_part: "name"
- rappor_candidates {
- candidates: "Module A"
- candidates: "Module B"
- }
- }
-}
-
-#### ReportConfig (2, 1, 2)
-element {
- customer_id: 2
- project_id: 1
- id: 3
- name: "Acme Popular URLs"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- variable {
- metric_part: "url"
- }
-}
-
diff --git a/src/registry/production/README.md b/src/registry/production/README.md
deleted file mode 100644
index 2a78690..0000000
--- a/src/registry/production/README.md
+++ /dev/null
@@ -1,14 +0,0 @@
-# Cobalt Official Production Config Registration Files
-
-These config registration files are used for production cobalt. Each of our
-clients has a copy of a subset of these files. Therefore if you make any
-changes to these files you must make corresponding changes in all of the
-relevent client code.
-
-Below we enumerate the customers and projects by ID:
-
-CustomerID, ProjecID, Customer Name, Project Name
------------ --------- ------------ ------------
-1 1 Fuchsia End-to-End Test
-1 2 Fuchsia Fuchsia Test App
-1 100 Fuchsia Ledger
diff --git a/src/registry/production/registered_encodings.txt b/src/registry/production/registered_encodings.txt
deleted file mode 100644
index 084a3b6..0000000
--- a/src/registry/production/registered_encodings.txt
+++ /dev/null
@@ -1,258 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of EncodingConfigs
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new EncodingConfig or change
-# the definition of an EncodingConfig, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredEncodings Protocol Buffer message, which is defined in
-# encodings.proto
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-########################### Project 100: Ledger ###############################
-
-#####################################################################
-# EncodingConfig(1, 100, 1)
-#
-# DEPRECATED: Please use EncodingConfig (1, 100, 2) instead.
-#
-# Name: Basic RAPPOR for Rare Event Occurrences
-# Description: A Configuration of Basic RAPPOR with no privacy, with string
-# category names, and with one category for each rare event.
-######################################################################
-element {
- customer_id: 1
- project_id: 100
- id: 1
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- string_categories: {
- category: "Ledger-startup"
- category: "Commits-received-out-of-order"
- category: "Commits-merged"
- category: "Merged-commits-merged"
- category: "Commits-received-out-of-order-not-recovered"
- }
- }
-}
-
-#####################################################################
-# EncodingConfig(1, 100, 2)
-# Name: Basic RAPPOR for Rare Event Occurrences
-# Description: A Configuration of Basic RAPPOR with no privacy, with 128
-# indexed categories.
-######################################################################
-element {
- customer_id: 1
- project_id: 100
- id: 2
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- indexed_categories: {
- num_categories: 128
- }
- }
-}
-
-##################### Project 101: Module Usage Tracking ######################
-
-#####################################################################
-# EncodingConfig(1, 101, 1)
-# Name: Forculus with minimal privacy
-# Description: We are using Forculus to collect arbitrary strings. We don't
-# need privacy at this time so we use a threshold of 2 and
-# an aggregation epoch of a month. This means that a string
-# will be decoded as long as it as sent by at least two differnt
-# devices in any given calendar month. At the time of this writing
-# we have not yet implemented persistent device identity so
-# every re-start of the Cobalt Client process on a Fuchsia
-# system counts as a new device.
-######################################################################
-element {
- customer_id: 1
- project_id: 101
- id: 1
- forculus {
- threshold: 2
- epoch_type: MONTH
- }
-}
-
-######################### Project 102: System Metrics ##########################
-
-#####################################################################
-# EncodingConfig(1, 102, 1)
-# Name: NoOp encoding
-# Description: Observations are sent unencoded.
-######################################################################
-element {
- customer_id: 1
- project_id: 102
- id: 1
- no_op_encoding {
- }
-}
-
-
-################################################################################
-# *** NOTICE: Below this line are testing-only projects. ***
-#
-# These project must all use project IDs less than 100.
-################################################################################
-
-## Project 1: End-to-End test
-
-#### EncodingConfig(1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- forculus {
- threshold: 20
- epoch_type: DAY
- }
-}
-
-#### EncodingConfig(1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- basic_rappor {
- prob_0_becomes_1: 0.1
- prob_1_stays_1: 0.9
- int_range_categories: {
- first: 0
- last: 23
- }
- }
-}
-
-#### EncodingConfig(1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- basic_rappor {
- prob_0_becomes_1: 0.01
- prob_1_stays_1: 0.99
- string_categories: {
- category: "apple"
- category: "banana"
- category: "cantaloupe"
- }
- }
-}
-
-#### EncodingConfig(1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- basic_rappor {
- prob_0_becomes_1: 0.2
- prob_1_stays_1: 0.8
- int_range_categories: {
- first: 0
- last: 10
- }
- }
-}
-
-#### EncodingConfig(1, 1, 5)
-element {
- customer_id: 1
- project_id: 1
- id: 5
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- indexed_categories: {
- num_categories: 100
- }
- }
-}
-
-# Encoding (1, 1, 6) is the No-Op encoding.
-element {
- customer_id: 1
- project_id: 1
- id: 6
- no_op_encoding {
- }
-}
-
-## Project 2: Fuchsia Test App
-
-#####################################################################
-# EncodingConfig(1, 2, 1)
-# Name: Basic RAPPOR for Daily Rare Event Counts
-# Description: A Configuration of Basic RAPPOR with no privacy, with string
-# category names, and with one category for each rare event.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 1
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- string_categories: {
- category: "Ledger-startup"
- category: "Commits-received-out-of-order"
- category: "Commits-merged"
- category: "Merged-commits-merged"
- }
- }
-}
-
-#####################################################################
-# EncodingConfig(1, 2, 2)
-# Name: Forculus with minimal privacy
-# Description: We are using Forculus to collect arbitrary strings. We don't
-# need privacy at this time so we use a threshold of 2 and
-# an aggregation epoch of a month. This means that a string
-# will be decoded as long as it as sent by at least two differnt
-# devices in any given calendar month. At the time of this writing
-# we have not yet implemented persistent device identity so
-# every re-start of the Cobalt Client process on a Fuchsia
-# system counts as a new device.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 2
- forculus {
- threshold: 2
- epoch_type: MONTH
- }
-}
-
-#####################################################################
-# EncodingConfig(1, 2, 3)
-# Name: Basic RAPPOR for Rare Event Occurrences
-# Description: A Configuration of Basic RAPPOR with no privacy, with 128
-# indexed categories.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 3
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- indexed_categories: {
- num_categories: 128
- }
- }
-}
diff --git a/src/registry/production/registered_metrics.txt b/src/registry/production/registered_metrics.txt
deleted file mode 100644
index 3e126b9..0000000
--- a/src/registry/production/registered_metrics.txt
+++ /dev/null
@@ -1,316 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of Metrics
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new Metric or change
-# the definition of a Metric, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredMetrics Protocol Buffer message, which is defined in
-# metrics.proto
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-########################### Project 100: Ledger ###############################
-
-#####################################################################
-# Metric (1, 100, 1)
-#
-# DEPRECATED: Please use Metric (1, 100, 2) instead.
-#
-# Name: Rare event occurrences.
-# Description: Occurrences of several events that are expected to occur
-# rarely if ever.
-# Parts: This metric has one part named "Event name"
-# Notes: At least initially, we plan to use Basic RAPPOR with no privacy to
-# collect this metric. Each category will be one of the rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 100
- id: 1
- name: "Deprecated: Rare event occurrences"
- description: "Occurrences of several events that are expected to occur rarely if ever."
- time_zone_policy: UTC
- parts {
- key: "Event name"
- value {
- description: "Which rare event occurred?"
- }
- }
-}
-
-#####################################################################
-# Metric (1, 100, 2)
-# Name: Rare event occurrences.
-# Description: Occurrences of several events that are expected to occur
-# rarely if ever.
-# Parts: This metric has one part named "event-index"
-# Notes: At least initially, we plan to use Basic RAPPOR with no privacy to
-# collect this metric. The events are specified by a zero-based index.
-# The meaning of each index is not specified here. See the definition
-# of report config (1, 100, 2).
-######################################################################
-element {
- customer_id: 1
- project_id: 100
- id: 2
- name: "Rare event occurrences"
- description: "Occurrences of several events that are expected to occur rarely if ever."
- time_zone_policy: UTC
- parts {
- key: "event-index"
- value {
- description: "The index of the rare event that occurred."
- data_type: INDEX
- }
- }
-}
-
-##################### Project 101: Module Usage Tracking ######################
-
-#####################################################################
-# Metric (1, 101, 1)
-# Name: Module views
-# Description: Tracks each incidence of viewing a module by its URL.
-# Parts: This metric has one part named "url"
-# Notes: At least initially, we plan to use Forculus with threshold set
-# to 2 to collect this. (Forculus doesn't support threshold=1.)
-######################################################################
-element {
- customer_id: 1
- project_id: 101
- id: 1
- name: "Module views"
- description: "Tracks each incidence of viewing a module by its URL."
- time_zone_policy: UTC
- parts {
- key: "url"
- value {
- description: "The URL of the module being launched."
- }
- }
-}
-
-######################### Project 102: System Metrics ##########################
-
-#####################################################################
-# Metric (1, 102, 1)
-# Name: System Uptime
-# Description: The system metrics daemon will log system uptime after 0, 1, 2, 4, 8... minutes.
-# Parts: This metric has one part named "system_uptime_minutes".
-#
-# Notes: We will use the no-op encoding.
-######################################################################
-element {
- customer_id: 1
- project_id: 102
- id: 1
- name: "System Uptime"
- description: "The system metrics daemon will log system uptime after 0, 1, 2, 4, 8... minutes."
- time_zone_policy: UTC
- parts {
- key: "system_uptime_minutes"
- value {
- description: "How long since the system booted in minutes?"
- data_type: INT
- }
- }
-}
-
-
-################################################################################
-# *** NOTICE: Below this line are testing-only projects. ***
-#
-# These project must all use project IDs less than 100.
-################################################################################
-
-## Project 1: End-to-End test
-
-#### Metric (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuchsia Popular URLs"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "url"
- value {
- description: "A URL."
- data_type: STRING
- }
- }
-}
-
-#### Metric (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- name: "Fuschsia Usage by Hour"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "hour"
- value {
- description: "An integer from 0 to 23 representing the hour of the day."
- data_type: INT
- }
- }
-}
-
-#### Metric (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- name: "Fuschsia Fruit Consumption and Rating"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "fruit"
- value {
- description: "The name of a fruit that was consumed."
- }
- }
- parts {
- key: "rating"
- value {
- description: "An integer from 0 to 10"
- data_type: INT
- }
- }
-}
-
-#### Metric (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- name: "Rare Events"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "event"
- value {
- description: "The index of a rare event. See report config (1,1,4) for the labels corresponding to each index."
- data_type: INDEX
- }
- }
-}
-
-#### Metric (1, 1, 5)
-element {
- customer_id: 1
- project_id: 1
- id: 5
- name: "Fuchsia Module Usage"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "module"
- value {
- description: "A module identifier"
- data_type: STRING
- }
- }
-}
-
-#### Metric (1, 1, 6)
-element {
- customer_id: 1
- project_id: 1
- id: 6
- name: "Device Type"
- description: "This is a fictional metric used for the development of Cobalt."
- time_zone_policy: LOCAL
- parts {
- key: "device"
- value {
- description: "Which type of device is Fuchsia running on"
- data_type: INDEX
- }
- }
-}
-
-## Project 2: Fuchsia Test App
-
-#####################################################################
-# Metric (1, 2, 1)
-# Name: Daily rare event counts
-# Description: Daily counts of several events that are expected to occur
-# rarely if ever.
-# Parts: This metric has one part name "Event name"
-# Notes: At least initially, we plan to use Basic RAPPOR with no privacy to
-# collect this metric. Each category will be one of the rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 1
- name: "Daily rare event counts"
- description: "Daily counts of several events that are expected to occur rarely if ever."
- time_zone_policy: UTC
- parts {
- key: "Event name"
- value {
- description: "Which rare event occurred?"
- }
- }
-}
-
-#####################################################################
-# Metric (1, 2, 2)
-# Name: Module views
-# Description: Tracks each incidence of viewing a module by its URL.
-# Parts: This metric has one part named "url"
-# Notes: At least initially, we plan to use Forculus with threshold set
-# to 2 to collect this. (Forculus doesn't support threshold=1.)
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 2
- name: "Module views"
- description: "Tracks each incidence of viewing a module by its URL."
- time_zone_policy: UTC
- parts {
- key: "url"
- value {
- description: "The URL of the module being launched."
- }
- }
-}
-
-#####################################################################
-# Metric (1, 2, 3)
-# Name: Rare event occurrences using indexes.
-# Description: Occurrences of several events that are expected to occur
-# rarely if ever.
-# Parts: This metric has one part named "event-index"
-# Notes: At least initially, we plan to use Basic RAPPOR with no privacy to
-# collect this metric. Each category will be one of the rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 3
- name: "Rare event occurrences"
- description: "Occurrences of several events that are expected to occur rarely if ever."
- time_zone_policy: UTC
- parts {
- key: "event-index"
- value {
- description: "The index of the rare event that occurred."
- data_type: INDEX
- }
- }
-}
diff --git a/src/registry/production/registered_reports.txt b/src/registry/production/registered_reports.txt
deleted file mode 100644
index fdde658..0000000
--- a/src/registry/production/registered_reports.txt
+++ /dev/null
@@ -1,382 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of ReportConfigs
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new ReportConfig or change
-# the definition of an ReportConfig, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredReports Protocol Buffer message, which is defined in
-# report_configs.proto.
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-########################### Project 100: Ledger ###############################
-
-#####################################################################
-# Report Config (1, 100, 1)
-#
-# DEPRECATED: Please use Report Config (1, 100, 2) instead.
-#
-# Name: Daily rare event counts
-# Description: A daily report of the daily counts of rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 100
- id: 1
- name: "Deprecated: Fuchsia Ledger Daily Rare Event Counts"
- description: "A daily report of the daily counts of rare events."
- metric_id: 1
- variable {
- metric_part: "Event name"
- }
-}
-
-#####################################################################
-# Report Config (1, 100, 2)
-# Name: Daily rare event counts
-# Description: A daily report of the daily counts of rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 100
- id: 2
- name: "Fuchsia Ledger Daily Rare Event Counts"
- description: "A daily report of the daily counts of rare events."
- metric_id: 2
- variable {
- metric_part: "event-index"
- index_labels {
- labels {
- key: 0
- value: "ledger startup"
- }
- labels {
- key: 1
- value: "commits received out-of-order"
- }
- labels {
- key: 2
- value: "commits merged"
- }
- labels {
- key: 3
- value: "merged-commits merged"
- }
- labels {
- key: 4;
- value: "commits received out-of-order: not-recovered"
- }
- labels {
- key: 5;
- value: "ledger leveldb state corrupted"
- }
- }
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-p100-ledger"
- }
- }
-}
-
-##################### Project 101: Module Usage Tracking ######################
-
-#####################################################################
-# Report Config (1, 101, 1)
-# Name: Daily module launch counts.
-# Description: A daily report of the daily counts of module launches.
-# Note that because we use Forculus to collect the Observations
-# for this report, a given URL will not appear in the report
-# unless it was used by at least two different devices in
-# the same calendar month. (At this time each reboot of Fuchsia
-# counts as a different device for this purpose.)
-######################################################################
-element {
- customer_id: 1
- project_id: 101
- id: 1
- name: "Fuchsia Module Daily Launch Counts"
- description: "A daily report of the daily counts of module launches by URL."
- metric_id: 1
- variable {
- metric_part: "url"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-p101-mod-usage"
- }
- }
-}
-
-######################### Project 102: System Metrics ##########################
-element {
- customer_id: 1
- project_id: 102
- id: 1
- name: "Fuchsia Uptime"
- description: "A daily report of how long Fuchsia instances have been running."
- metric_id: 1
- report_type: HISTOGRAM
- variable {
- metric_part: "system_uptime_minutes"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-default"
- }
- }
-}
-
-
-################################################################################
-# *** NOTICE: Below this line are testing-only projects. ***
-#
-# These project must all use project IDs less than 100.
-################################################################################
-
-## Project 1: End-to-End test
-
-#### ReportConfig (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuchsia Popular URLs"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 1
- variable {
- metric_part: "url"
- }
-}
-
-#### ReportConfig (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- name: "Fuchsia Usage by Hour"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 2
- variable {
- metric_part: "hour"
- }
-}
-
-#### ReportConfig (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- name: "Fuchsia Fruit Consumption and Rating Joint Analysis"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- variable {
- metric_part: "fruit"
- }
- variable {
- metric_part: "rating"
- }
-}
-
-#### ReportConfig (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- name: "Fuschsia Daily System Event Counts"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 4
- variable {
- metric_part: "event"
- index_labels {
- labels {
- key: 0
- value: "Event A"
- }
- labels {
- key: 1
- value: "Event B"
- }
- labels {
- key: 25
- value: "Event Z"
- }
- }
- }
-}
-
-#### ReportConfig (1, 1, 5)
-element {
- customer_id: 1
- project_id: 1
- id: 5
- name: "Fuchsia Module Usage"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 5
- variable {
- metric_part: "module"
- }
-}
-
-#### ReportConfig (1, 1, 6)
-element {
- customer_id: 1
- project_id: 1
- id: 6
- name: "Fuschsia Device Start Counts"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 6
- variable {
- metric_part: "device"
- index_labels {
- labels {
- key: 0
- value: "Type A"
- }
- labels {
- key: 1
- value: "Type B"
- }
- labels {
- key: 25
- value: "Type Z"
- }
- }
- }
-}
-
-## Project 2: Fuchsia Test App
-
-#####################################################################
-# Report Config (1, 2, 1)
-# Name: Daily rare event counts
-# Description: A Daily report of Rare Events metric.
-# Parts: This metric has one part name "Event name"
-# Notes: At least initially, we plan to use Basic RAPPOR with no privacy to
-# collect this metric. Each category will be one of the rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 1
- name: "Fuchsia Ledger Daily Rare Events"
- description: "A daily report of events that are expected to happen rarely."
- metric_id: 1
- variable {
- metric_part: "Event name"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-p2-test-app"
- }
- }
-}
-
-#####################################################################
-# Report Config (1, 2, 2)
-# Name: Daily module view counts.
-# Description: A daily report of the daily counts of module views.
-# Note that because we use Forculus to collect the Observations
-# for this report, a given URL will not appear in the report
-# unless it was used by at least two different devices in
-# the same calendar month. (At this time each reboot of Fuchsia
-# counts as a different device for this purpose.)
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 2
- name: "Fuchsia Module Daily Launch Counts"
- description: "A daily report of the daily counts of module launches by URL."
- metric_id: 2
- variable {
- metric_part: "url"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-p2-test-app"
- }
- }
-}
-
-#####################################################################
-# Report Config (1, 2, 3)
-# Name: Daily rare event counts
-# Description: A daily report of the daily counts of rare events.
-######################################################################
-element {
- customer_id: 1
- project_id: 2
- id: 3
- name: "Fuchsia Ledger Daily Rare Event Counts"
- description: "A daily report of the daily counts of rare events."
- metric_id: 3
- variable {
- metric_part: "event-index"
- index_labels {
- labels {
- key: 0
- value: "ledger startup"
- }
- labels {
- key: 1
- value: "commits received out-of-order"
- }
- labels {
- key: 2
- value: "commits merged"
- }
- labels {
- key: 3
- value: "merged-commits merged"
- }
- labels {
- key: 4;
- value: "commits received out-of-order: not-recovered"
- }
- }
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-p2-test-app"
- }
- }
-}
diff --git a/src/registry/test_files/registered_encodings_contains_duplicate.txt b/src/registry/test_files/registered_encodings_contains_duplicate.txt
deleted file mode 100644
index 32ee142..0000000
--- a/src/registry/test_files/registered_encodings_contains_duplicate.txt
+++ /dev/null
@@ -1,24 +0,0 @@
-# This is a valid textual representation of the RegisteredEncodings message
-# but it contains two EncodingConfigs with the same id. This file is used
-# by config_test.cc to test that the function EncodingRegistry::FromFile
-# correctly detects the duplicate registration.
-
-element {
- customer_id: 1
- project_id: 1
- id: 1
- forculus: {
- threshold: 20
- epoch_type: WEEK
- }
-}
-
-element {
- customer_id: 1
- project_id: 1
- id: 1
- forculus: {
- threshold: 50
- epoch_type: MONTH
- }
-}
diff --git a/src/registry/test_files/registered_encodings_valid.txt b/src/registry/test_files/registered_encodings_valid.txt
deleted file mode 100644
index 6448051..0000000
--- a/src/registry/test_files/registered_encodings_valid.txt
+++ /dev/null
@@ -1,97 +0,0 @@
-
-###########################################################################
-# This is a valid version of the registered_encodings.txt file that
-# is used by TEST(EncodingRegistryFromFile, ValidFile) in config_test.cc
-##########################################################################
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-## Project 1
-
-#### Encoding (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- forculus {
- threshold: 20
- epoch_type: WEEK
- }
-}
-
-#### Encoding (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- rappor {
- num_bloom_bits: 64
- num_hashes: 2
- num_cohorts: 100
- prob_0_becomes_1: 0.2
- prob_1_stays_1: 0.8
- }
-}
-
-#### Encoding (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- basic_rappor {
- prob_0_becomes_1: 0.1
- prob_1_stays_1: 0.9
- int_range_categories: {
- first: -1
- last: 1
- }
- }
-}
-
-#### Encoding (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- basic_rappor {
- prob_0_becomes_1: 0.0
- prob_1_stays_1: 1.0
- indexed_categories: {
- num_categories: 100
- }
- }
-}
-
-#########################
-# Customer 2 (Acme)
-########################
-
-## Project 1
-
-#### Encoding (2, 1, 1)
-element {
- customer_id: 2
- project_id: 1
- id: 1
- basic_rappor {
- prob_0_becomes_1: 0.1
- prob_1_stays_1: 0.9
- string_categories: {
- category: "dog"
- category: "cat"
- category: "fish"
- }
- }
-}
-
-#### Encoding (2, 1, 2)
-element {
- customer_id: 2
- project_id: 1
- id: 2
- forculus {
- threshold: 50
- }
-}
diff --git a/src/registry/test_files/registered_metrics_contains_duplicate.txt b/src/registry/test_files/registered_metrics_contains_duplicate.txt
deleted file mode 100644
index d695424..0000000
--- a/src/registry/test_files/registered_metrics_contains_duplicate.txt
+++ /dev/null
@@ -1,32 +0,0 @@
-
-# This is a valid textual representation of the RegisteredMetrics message
-# but it contains two MetricConfigs with the same id. This file is used
-# by config_test.cc to test that the function MetricRegistry::FromFile
-# correctly detects the duplicate registration.
-
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuschsia Rating and City"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "city"
- value {
- }
- }
-}
-
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuschsia Usage by Hour"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "hour"
- value {
- }
- }
-}
-
diff --git a/src/registry/test_files/registered_metrics_valid.txt b/src/registry/test_files/registered_metrics_valid.txt
deleted file mode 100644
index 811e770..0000000
--- a/src/registry/test_files/registered_metrics_valid.txt
+++ /dev/null
@@ -1,111 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of Metrics
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new Metric or change
-# the definition of a Metric, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredMetrics Protocol Buffer message, which is defined in
-# metrics.proto
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-## Project 1
-
-#### Metric (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuschsia Rating and City"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "rating"
- value {
- description: "An integer from 0 to 10"
- data_type: INT
- }
- }
- parts {
- key: "city"
- value {
- description: "The name of a city"
- }
- }
-}
-
-#### Encoding (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- name: "Fuschsia Usage by Hour"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "hour"
- value {
- description: "An integer from 0 to 23 representing the hour of the day."
- data_type: INT
- }
- }
-}
-
-#### Encoding (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- name: "Fuschsia System Events"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "event"
- value {
- description: "The index of one of the system event types."
- data_type: INDEX
- }
- }
-}
-
-#########################
-# Customer 2 (Acme)
-########################
-
-## Project 1
-
-#### Metric (2, 1, 1)
-element {
- customer_id: 2
- project_id: 1
- id: 1
- name: "Acme Module name"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "name"
- value {
- description: "The name of a module."
- data_type: STRING
- }
- }
-}
-
-#### Metric (2, 1, 2)
-element {
- customer_id: 2
- project_id: 1
- id: 2
- name: "Acme Popular URLs"
- description: "This is a fictional metric used for the development of Cobalt."
- parts {
- key: "url"
- value {
- description: "A URL."
- }
- }
-}
diff --git a/src/registry/test_files/registered_reports_contains_duplicate.txt b/src/registry/test_files/registered_reports_contains_duplicate.txt
deleted file mode 100644
index 1aeeec7..0000000
--- a/src/registry/test_files/registered_reports_contains_duplicate.txt
+++ /dev/null
@@ -1,40 +0,0 @@
-
-# This is a valid textual representation of the RegisteredReports message
-# but it contains two ReportConfigs with the same id. This file is used
-# by config_test.cc to test that the function ReportRegistry::FromFile
-# correctly detects the duplicate registration.
-
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuschsia Rating and City Joint Analysis"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 1
- variable {
- metric_part: "city"
- }
- variable {
- metric_part: "rating"
- }
- scheduling {
- report_finalization_days: 1
- aggregation_epoch_type: DAY
- }
-}
-
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuschsia Usage by Hour"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 2
- variable {
- metric_part: "hour"
- }
- scheduling {
- report_finalization_days: 5
- aggregation_epoch_type: WEEK
- }
-}
diff --git a/src/registry/test_files/registered_reports_valid.txt b/src/registry/test_files/registered_reports_valid.txt
deleted file mode 100644
index 063beb4..0000000
--- a/src/registry/test_files/registered_reports_valid.txt
+++ /dev/null
@@ -1,166 +0,0 @@
-
-###########################################################################
-# This file contains the source of truth for the set of ReportConfigs
-# that are registered in version 0.1 of Cobalt.
-#
-# This file is maintained by hand. To add a new ReportConfig or change
-# the definition of an ReportConfig, manually edit this file and
-# commit the change to the Cobalt repo.
-#
-# The format of this file is the textual representation of the
-# RegisteredReports Protocol Buffer message, which is defined in
-# report_configs.proto.
-##########################################################################
-
-
-#########################
-# Customer 1 (Fuchsia)
-########################
-
-## Project 1
-
-#### ReportConfig (1, 1, 1)
-element {
- customer_id: 1
- project_id: 1
- id: 1
- name: "Fuschsia Rating and City Joint Analysis"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 1
- variable {
- metric_part: "city"
- rappor_candidates {
- candidates: "San Francisco"
- candidates: "Los Angeles"
- }
- }
- variable {
- metric_part: "rating"
- }
- scheduling {
- report_finalization_days: 1
- aggregation_epoch_type: DAY
- }
-}
-
-#### ReportConfig (1, 1, 2)
-element {
- customer_id: 1
- project_id: 1
- id: 2
- name: "Fuschsia Usage by Hour"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 2
- variable {
- metric_part: "hour"
- }
- scheduling {
- report_finalization_days: 5
- aggregation_epoch_type: WEEK
- }
- export_configs {
- csv {}
- gcs {
- bucket: "bucket-1"
- }
- }
-}
-
-#### ReportConfig (1, 1, 3)
-element {
- customer_id: 1
- project_id: 1
- id: 3
- name: "Fuschsia Daily System Event Counts"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- variable {
- metric_part: "event"
- index_labels {
- labels {
- key: 0
- value: "Event A"
- }
- labels {
- key: 1
- value: "Event B"
- }
- labels {
- key: 25
- value: "Event Z"
- }
- }
- }
-}
-
-#### ReportConfig (1, 1, 4)
-element {
- customer_id: 1
- project_id: 1
- id: 4
- name: "Fuchsia Daily Fruit Rating"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- report_type: RAW_DUMP
- variable {
- metric_part: "fruit"
- }
- variable {
- metric_part: "rating"
- }
- scheduling {
- report_finalization_days: 3
- aggregation_epoch_type: DAY
- }
- export_configs {
- csv {}
- gcs {
- bucket: "fuchsia-cobalt-reports-test1-rudominer"
- }
- }
-}
-
-#########################
-# Customer 2 (Acme)
-########################
-
-## Project 1
-
-#### ReportConfig (2, 1, 1)
-element {
- customer_id: 2
- project_id: 1
- id: 1
- name: "Acme Module Names"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 1
- variable {
- metric_part: "name"
- rappor_candidates {
- candidates: "Module A"
- candidates: "Module B"
- }
- }
- scheduling {
- report_finalization_days: 5
- aggregation_epoch_type: MONTH
- }
-}
-
-#### ReportConfig (2, 1, 2)
-element {
- customer_id: 2
- project_id: 1
- id: 3
- name: "Acme Popular URLs"
- description: "This is a fictional report used for the development of Cobalt."
- metric_id: 3
- variable {
- metric_part: "url"
- }
- scheduling {
- report_finalization_days: 1
- aggregation_epoch_type: DAY
- }
-}
-
