)]}'
{"specs/rocky/approved/metrics-retention.rst":[{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":27,"context_line":"on adaily base which could eliminate the need of longer retention of metering"},{"line_number":28,"context_line":"metrcs. Monasca needs to support metric retention policy that can be tailored"},{"line_number":29,"context_line":"per metric or metric type."},{"line_number":30,"context_line":""},{"line_number":31,"context_line":"Use Cases"},{"line_number":32,"context_line":"---------"},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_80e97d81","line":30,"updated":"2018-02-28 18:31:29.000000000","message":"Determination/setting of metrics retention should consider things like Functional area, metric granularity/time interval, roll-up policy. Essentially we want to enable the admin/user to be able to dump any metrics that are no longer relevant to their operations","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":51,"context_line":"  The metric agent plugin sets retention policy when generates a new metric."},{"line_number":52,"context_line":"  This is mostly a means to overwrite the default retention policy for"},{"line_number":53,"context_line":"  monitoring metrics."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"Proposed change"},{"line_number":56,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":57,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_208f49cd","line":54,"updated":"2018-02-28 18:31:29.000000000","message":"These use cases seem to focus on how the data was collected. We should be looking to enable setting retention policy on groups of similarly behaving metrics. This could either be predefined groups of metrics or adhoc groupings defined by the admin. As noted above, this would be more driven by things like the collection interval (metrics collected every 60 seconds are not real relevant after 3 months), type of metric, class of metric, ...","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":69,"context_line":"1. Monasca api "},{"line_number":70,"context_line":"   Add an optional metric property \"TTL\" in the create mwetrics api. TTL is the"},{"line_number":71,"context_line":"   number of seconds before the metric sets to expire. If set, the TTL property"},{"line_number":72,"context_line":"   will be included When posting a new metric message to Kafka."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"2. Monasca persister"},{"line_number":75,"context_line":"   Persister reads the default retention policy setting from the service"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_20a8a91d","line":72,"range":{"start_line":72,"start_character":62,"end_line":72,"end_character":63},"updated":"2018-02-28 18:31:29.000000000","message":"So is this optional property support for cases where the submitter wants to override an policy based retention period?","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":86,"context_line":""},{"line_number":87,"context_line":"   The TTL is set in the parameterized database query when persisting the metrics"},{"line_number":88,"context_line":"   into the time series database, including both Cassandra and InfluxDB."},{"line_number":89,"context_line":""},{"line_number":90,"context_line":"3. Monasca Ceilometer (aka Ceilosca)"},{"line_number":91,"context_line":"   Add TTL property in the pipeline-api.yaml::"},{"line_number":92,"context_line":"    - name: image_source"}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_a07119e3","line":89,"updated":"2018-02-28 18:31:29.000000000","message":"How is the policy set? Is there an API for this?","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":104,"context_line":""},{"line_number":105,"context_line":"   Monasca-ceilometer implementation will parse the new property and set the TTL"},{"line_number":106,"context_line":"   when posting new metric message."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"4. Monasca trasnform"},{"line_number":109,"context_line":"   Add TTL property in transform_specs.json::"},{"line_number":110,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_207d09b1","line":107,"updated":"2018-02-28 18:31:29.000000000","message":"Having a seperate mechanism to configure retention based on the fact that it is collected somewhere else is not really great. I would prefer a more central policy","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":112,"context_line":""},{"line_number":113,"context_line":"   Monasca-transform implementation will parse the new property and set the TTL"},{"line_number":114,"context_line":"   when posting new rolled up metric messages."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Alternatives"},{"line_number":117,"context_line":"------------"},{"line_number":118,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_405ff540","line":115,"updated":"2018-02-28 18:31:29.000000000","message":"Same as comment as monasca ceilometer, we should look at options to centralize","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":9320,"name":"Dan Dyer","email":"dan.dyer00@gmail.com","username":"dandyer00"},"change_message_id":"2a2f9727f77524c6d276e4d96795e4e2110cc6f0","unresolved":false,"context_lines":[{"line_number":160,"context_line":""},{"line_number":161,"context_line":"* Example use case including typical API samples for both data supplied"},{"line_number":162,"context_line":"  by the caller and the response"},{"line_number":163,"context_line":""},{"line_number":164,"context_line":"Security impact"},{"line_number":165,"context_line":"---------------"},{"line_number":166,"context_line":""}],"source_content_type":"text/x-rst","patch_set":6,"id":"1f9dbf25_0059ed58","line":163,"updated":"2018-02-28 18:31:29.000000000","message":"How about some kind of configuration API?","commit_id":"e2115e21efaf98ed06df1ffe4ffa487e11c29b13"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Story board: https://storyboard.openstack.org/#!/story/2001576"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Metric retention policy must be in place to avoid disk being filled up. "},{"line_number":14,"context_line":"Retention period should be adjustable for different types of metrics, e.g.,"},{"line_number":15,"context_line":"monitoring vs. metering. "},{"line_number":16,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_347be9be","line":13,"updated":"2018-03-20 22:00:48.000000000","message":"space at the end of the line","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":13,"context_line":"Metric retention policy must be in place to avoid disk being filled up. "},{"line_number":14,"context_line":"Retention period should be adjustable for different types of metrics, e.g.,"},{"line_number":15,"context_line":"monitoring vs. metering. "},{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Problem description"},{"line_number":18,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":19,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_f44ed194","line":16,"updated":"2018-03-20 22:00:48.000000000","message":"space at the end of the line","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":19,"context_line":""},{"line_number":20,"context_line":"In a cloud of 200 compute hosts, there can be up to one billion metrics"},{"line_number":21,"context_line":"generated daily. The time series database disks will be filled up in weeks"},{"line_number":22,"context_line":"if not months if old metric data is not purged regualrly. The retention"},{"line_number":23,"context_line":"requirement can be different based on the type of the metrics and the usage"},{"line_number":24,"context_line":"model. For example, the customer may want to preserve the metering metrics"},{"line_number":25,"context_line":"for months or years, while s/he has no interest in more than a week old"}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_34544921","line":22,"updated":"2018-03-20 22:00:48.000000000","message":"I\u0027d change in: ... up in months if not weeks ...","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":40,"context_line":""},{"line_number":41,"context_line":"- Use case 2"},{"line_number":42,"context_line":"  Operator configures the retention policy for the roll up metrics in the"},{"line_number":43,"context_line":"  Monasca transform. Roll up metrics generally requires longer retntion period."},{"line_number":44,"context_line":""},{"line_number":45,"context_line":"- Use case 3"},{"line_number":46,"context_line":"  Operator configures the retention policy for Ceilometer metrics in the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_741f2170","line":43,"updated":"2018-03-20 22:00:48.000000000","message":"typo: retntion -\u003e retention","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":66,"context_line":"get preliminary feedback. If so please say: Posting to get preliminary feedback"},{"line_number":67,"context_line":"on the scope of this spec."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"1. Monasca api "},{"line_number":70,"context_line":"   Add an optional metric property \"TTL\" in the create mwetrics api. TTL is the"},{"line_number":71,"context_line":"   number of seconds before the metric sets to expire. If set, the TTL property"},{"line_number":72,"context_line":"   will be included When posting a new metric message to Kafka."}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_7483a1aa","line":69,"range":{"start_line":69,"start_character":3,"end_line":69,"end_character":10},"updated":"2018-03-20 22:00:48.000000000","message":"trailer white space","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":74,"context_line":"2. Monasca persister"},{"line_number":75,"context_line":"   Persister reads the default retention policy setting from the service"},{"line_number":76,"context_line":"   configuration file in the influxDbConfiguration and cassandraDbConfiguration"},{"line_number":77,"context_line":"   section.::"},{"line_number":78,"context_line":"     # Retention policy may be left blank to indicate default policy."},{"line_number":79,"context_line":"     retentionPolicy: 7"},{"line_number":80,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_7408812c","line":77,"updated":"2018-03-20 22:00:48.000000000","message":"why \".::\"?","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":75,"context_line":"   Persister reads the default retention policy setting from the service"},{"line_number":76,"context_line":"   configuration file in the influxDbConfiguration and cassandraDbConfiguration"},{"line_number":77,"context_line":"   section.::"},{"line_number":78,"context_line":"     # Retention policy may be left blank to indicate default policy."},{"line_number":79,"context_line":"     retentionPolicy: 7"},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"   It may makes more sense to move this property to metricConfiguration section"}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_f4c011e3","line":78,"updated":"2018-03-20 22:00:48.000000000","message":"It looks like this indentation is wrong (I looked at console output)","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"},{"author":{"_account_id":14123,"name":"Stefano Canepa","email":"sc@linux.it","username":"sc"},"change_message_id":"12041e2634ffb74304985533ca3510b4574ec85b","unresolved":false,"context_lines":[{"line_number":209,"context_line":"  jgu"},{"line_number":210,"context_line":""},{"line_number":211,"context_line":"Other contributors:"},{"line_number":212,"context_line":"  "},{"line_number":213,"context_line":""},{"line_number":214,"context_line":"Work Items"},{"line_number":215,"context_line":"----------"}],"source_content_type":"text/x-rst","patch_set":8,"id":"df7087c5_946c3509","line":212,"updated":"2018-03-20 22:00:48.000000000","message":"Spaces","commit_id":"33c489665a09db058cc5c86b45962feabdc19d3c"}]}