)]}'
{"specs/kilo/deprecate-existence-meters.rst":[{"author":{"_account_id":7052,"name":"Fabio Giannetti","email":"fgiannet@cisco.com","username":"fabgia"},"change_message_id":"3bbd4eb8164c805585a607345c1740594265acf0","unresolved":false,"context_lines":[{"line_number":19,"context_line":""},{"line_number":20,"context_line":"The \"Existence of xyz\" meters we store in our samples database"},{"line_number":21,"context_line":"represents a significant portion of the data we store. These meters however"},{"line_number":22,"context_line":"offer no useful measurement value and it\u0027s true value is to capture the"},{"line_number":23,"context_line":"state of the resource at a given time. Additionally, the volume\u003d1 value is very"},{"line_number":24,"context_line":"confusing to consumers of data as for a while, Horizon used that value as the"},{"line_number":25,"context_line":"total number of values and often users would wonder why there was always 1"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_2941810b","line":22,"updated":"2014-12-01 17:28:52.000000000","message":"Gordon I don\u0027t understand where are you coming from ...The fact that you receive a notification of existence is *really* important for billing. You know something is up and running and this is vital data.","commit_id":"3d0f17d3b1048f1cc77df210073b1321d4ffbfe5"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"081b3cfd0b04ab2a5fefc76f27dc20eff32954d7","unresolved":false,"context_lines":[{"line_number":19,"context_line":""},{"line_number":20,"context_line":"The \"Existence of xyz\" meters we store in our samples database"},{"line_number":21,"context_line":"represents a significant portion of the data we store. These meters however"},{"line_number":22,"context_line":"offer no useful measurement value and it\u0027s true value is to capture the"},{"line_number":23,"context_line":"state of the resource at a given time. Additionally, the volume\u003d1 value is very"},{"line_number":24,"context_line":"confusing to consumers of data as for a while, Horizon used that value as the"},{"line_number":25,"context_line":"total number of values and often users would wonder why there was always 1"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_4e89186e","line":22,"in_reply_to":"5a890539_2941810b","updated":"2014-12-03 17:16:51.000000000","message":"as mentioned in irc chat, this spec isn\u0027t dropping/blocking any notification.","commit_id":"3d0f17d3b1048f1cc77df210073b1321d4ffbfe5"},{"author":{"_account_id":7052,"name":"Fabio Giannetti","email":"fgiannet@cisco.com","username":"fabgia"},"change_message_id":"3bbd4eb8164c805585a607345c1740594265acf0","unresolved":false,"context_lines":[{"line_number":28,"context_line":"As we move to a more time-series focused storage for samples, the \"volume\u003d1\""},{"line_number":29,"context_line":"meters we collect has not just an impact on storage size, but also the overhead"},{"line_number":30,"context_line":"of rolling up and computing statistics on something as trivial and meaningless"},{"line_number":31,"context_line":"as the constant 1."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_a99e5161","line":31,"updated":"2014-12-01 17:28:52.000000000","message":"I would disagree with this statement. Let me give you an example:\nI am billing my customers on a hourly base. So the customer will pay for an instance that is running up to the hour. Even if the instance is happily running for 24h I have to have the data that supports the fact that the instance was running every hour in that interval.\nNow if the start and stop is stored as meters and the existence as events you will have to get data from different places for the same thing. Moreover, how do I give a hourly representation of the instances running if this data is not in the timeseries?","commit_id":"3d0f17d3b1048f1cc77df210073b1321d4ffbfe5"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"081b3cfd0b04ab2a5fefc76f27dc20eff32954d7","unresolved":false,"context_lines":[{"line_number":28,"context_line":"As we move to a more time-series focused storage for samples, the \"volume\u003d1\""},{"line_number":29,"context_line":"meters we collect has not just an impact on storage size, but also the overhead"},{"line_number":30,"context_line":"of rolling up and computing statistics on something as trivial and meaningless"},{"line_number":31,"context_line":"as the constant 1."},{"line_number":32,"context_line":""},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Proposed change"}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_11cbb572","line":31,"in_reply_to":"5a890539_a99e5161","updated":"2014-12-03 17:16:51.000000000","message":"... i don\u0027t understand how your example relates to my comment that rolling up constant will always be the same value?\n\nin fact, without events, your scenario may fall apart as the granularity of samples is rolled up and you lose individual datapoints...","commit_id":"3d0f17d3b1048f1cc77df210073b1321d4ffbfe5"},{"author":{"_account_id":7052,"name":"Fabio Giannetti","email":"fgiannet@cisco.com","username":"fabgia"},"change_message_id":"3bbd4eb8164c805585a607345c1740594265acf0","unresolved":false,"context_lines":[{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"The \"Existence of xyz\" and \"volume\u003d1\" meters can be better represented as what"},{"line_number":38,"context_line":"they really are: Events. The core event functionality was implemented in"},{"line_number":39,"context_line":"previous cycles and should be expanded to better cover these non-measurement"},{"line_number":40,"context_line":"meters."},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_e904d9c7","line":38,"updated":"2014-12-01 17:28:52.000000000","message":"I think Ceilometer already gives the option of having either events or meters. Having some of the data in one place and some of the other will break many systems that rely either on using meters or using events.","commit_id":"3d0f17d3b1048f1cc77df210073b1321d4ffbfe5"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"081b3cfd0b04ab2a5fefc76f27dc20eff32954d7","unresolved":false,"context_lines":[{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"The \"Existence of xyz\" and \"volume\u003d1\" meters can be better represented as what"},{"line_number":38,"context_line":"they really are: Events. The core event functionality was implemented in"},{"line_number":39,"context_line":"previous cycles and should be expanded to better cover these non-measurement"},{"line_number":40,"context_line":"meters."},{"line_number":41,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"5a890539_b1958133","line":38,"in_reply_to":"5a890539_e904d9c7","updated":"2014-12-03 17:16:51.000000000","message":"you can still share the same db. i\u0027m still curious what value you use in the existence of samples that makes them useful (as a verbose sample item)","commit_id":"3d0f17d3b1048f1cc77df210073b1321d4ffbfe5"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":55,"context_line":"     add them to the event_definitions file. The vast majority of them are"},{"line_number":56,"context_line":"     created from notifications so no work needs to be done aside from adding"},{"line_number":57,"context_line":"     them to event_defintion."},{"line_number":58,"context_line":"  2. Change default pipeline to not enable these meters. NOTE: this does not"},{"line_number":59,"context_line":"     affect existing solutions nor will it break anything."},{"line_number":60,"context_line":"  3. Some meters such as network related meters (LBaaS, VPNaaS, SDN,"},{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_1819c279","line":58,"updated":"2014-12-16 01:43:06.000000000","message":"For one case, could you confirm that ?\n\nIs it possible for users to enable these meters in pipeline ?","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":55,"context_line":"     add them to the event_definitions file. The vast majority of them are"},{"line_number":56,"context_line":"     created from notifications so no work needs to be done aside from adding"},{"line_number":57,"context_line":"     them to event_defintion."},{"line_number":58,"context_line":"  2. Change default pipeline to not enable these meters. NOTE: this does not"},{"line_number":59,"context_line":"     affect existing solutions nor will it break anything."},{"line_number":60,"context_line":"  3. Some meters such as network related meters (LBaaS, VPNaaS, SDN,"},{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_38eafe77","line":58,"in_reply_to":"3a961159_1819c279","updated":"2015-01-20 13:46:53.000000000","message":"yes. you will still be able to use this meters... how well it will work depends on whether you continue using current backend offerings or if you move to a tsdb.","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":58,"context_line":"  2. Change default pipeline to not enable these meters. NOTE: this does not"},{"line_number":59,"context_line":"     affect existing solutions nor will it break anything."},{"line_number":60,"context_line":"  3. Some meters such as network related meters (LBaaS, VPNaaS, SDN,"},{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"},{"line_number":62,"context_line":"     republish information as events."},{"line_number":63,"context_line":"  4. Offer a migration option for moving existing meters to events. This may"},{"line_number":64,"context_line":"     be better as a tool rather than a migration script as some users may"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_5d1c1c78","line":61,"updated":"2014-12-16 01:43:06.000000000","message":"For here, did you mean this convert periodically ? Or something else,\nif periodically, it is would be same as samples.\n\nThanks","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":58,"context_line":"  2. Change default pipeline to not enable these meters. NOTE: this does not"},{"line_number":59,"context_line":"     affect existing solutions nor will it break anything."},{"line_number":60,"context_line":"  3. Some meters such as network related meters (LBaaS, VPNaaS, SDN,"},{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"},{"line_number":62,"context_line":"     republish information as events."},{"line_number":63,"context_line":"  4. Offer a migration option for moving existing meters to events. This may"},{"line_number":64,"context_line":"     be better as a tool rather than a migration script as some users may"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_9e54bbc7","line":61,"in_reply_to":"3a961159_12fb6c16","updated":"2015-01-20 13:46:53.000000000","message":"sure.","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":3012,"name":"Dina Belova","email":"dbelova@mirantis.com","username":"dbelova"},"change_message_id":"6ad34a5c2225aa524e1ff4867a79c3dd454447d4","unresolved":false,"context_lines":[{"line_number":58,"context_line":"  2. Change default pipeline to not enable these meters. NOTE: this does not"},{"line_number":59,"context_line":"     affect existing solutions nor will it break anything."},{"line_number":60,"context_line":"  3. Some meters such as network related meters (LBaaS, VPNaaS, SDN,"},{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"},{"line_number":62,"context_line":"     republish information as events."},{"line_number":63,"context_line":"  4. Offer a migration option for moving existing meters to events. This may"},{"line_number":64,"context_line":"     be better as a tool rather than a migration script as some users may"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_12fb6c16","line":61,"in_reply_to":"3a961159_5d1c1c78","updated":"2015-01-19 10:40:35.000000000","message":"I would say that this information should be received as a notifications from LBaas, etc. And it looks like we do have this support now - https://github.com/openstack/ceilometer/blob/master/ceilometer/network/notifications.py#L230 and etc. - may you please place some examples here of meters we poll, needed to be converted?","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"},{"line_number":62,"context_line":"     republish information as events."},{"line_number":63,"context_line":"  4. Offer a migration option for moving existing meters to events. This may"},{"line_number":64,"context_line":"     be better as a tool rather than a migration script as some users may"},{"line_number":65,"context_line":"     want to carry on with meters?"},{"line_number":66,"context_line":"  5. Henceforth, Samples will be measurements which can be aggregated and"},{"line_number":67,"context_line":"     rolled up in meaningful ways (within gnocchi). Events will be the raw"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_fd04e819","line":64,"updated":"2014-12-16 01:43:06.000000000","message":"Could you explain  what\u0027s the difference between tool and migration script here?","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":61,"context_line":"     etc...) come from pollsters. We will need to convert these pollsters to"},{"line_number":62,"context_line":"     republish information as events."},{"line_number":63,"context_line":"  4. Offer a migration option for moving existing meters to events. This may"},{"line_number":64,"context_line":"     be better as a tool rather than a migration script as some users may"},{"line_number":65,"context_line":"     want to carry on with meters?"},{"line_number":66,"context_line":"  5. Henceforth, Samples will be measurements which can be aggregated and"},{"line_number":67,"context_line":"     rolled up in meaningful ways (within gnocchi). Events will be the raw"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_38911ef8","line":64,"in_reply_to":"3a961159_fd04e819","updated":"2015-01-20 13:46:53.000000000","message":"migration is forced changed in data structure... tool is optional. i\u0027ll make this explicit","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Audit data. This is an issue that already exists and will just be migrated from"},{"line_number":96,"context_line":"Samples to Events. It should be possible to add a tag to the event_definition"},{"line_number":97,"context_line":"file to mark data as audit. \u003cDISCUSSION\u003e"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Pipeline impact"},{"line_number":100,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_987212ac","line":97,"updated":"2014-12-16 01:43:06.000000000","message":"seems interesting, do we have some details for that ? Or I don\u0027t know such discussion before.","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Audit data. This is an issue that already exists and will just be migrated from"},{"line_number":96,"context_line":"Samples to Events. It should be possible to add a tag to the event_definition"},{"line_number":97,"context_line":"file to mark data as audit. \u003cDISCUSSION\u003e"},{"line_number":98,"context_line":""},{"line_number":99,"context_line":"Pipeline impact"},{"line_number":100,"context_line":"---------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_1e5e0b14","line":97,"in_reply_to":"3a961159_987212ac","updated":"2015-01-20 13:46:53.000000000","message":"https://bugs.launchpad.net/ceilometer/+bug/1376915","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":99,"context_line":"Pipeline impact"},{"line_number":100,"context_line":"---------------"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Switch to disable \"volume\u003d1\" meters by default. Indirectly, we should probably"},{"line_number":103,"context_line":"add a pipeline for Events."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"Other end user impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_389afec5","line":102,"updated":"2014-12-16 01:43:06.000000000","message":"1. For this volume\u003d1, it not only for volume, it is a just an example, right ?","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":99,"context_line":"Pipeline impact"},{"line_number":100,"context_line":"---------------"},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"Switch to disable \"volume\u003d1\" meters by default. Indirectly, we should probably"},{"line_number":103,"context_line":"add a pipeline for Events."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"Other end user impact"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_98b77285","line":102,"in_reply_to":"3a961159_389afec5","updated":"2015-01-20 13:46:53.000000000","message":"not sure what you are asking. this is basically saying: \u0027meters\u0027 we build currently that have a hardcoded volume value of 1 will not be enable by default...","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":113,"context_line":"-------------------------------"},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"Less sample data. Less equivalent data in Events (because of trait filtering)."},{"line_number":116,"context_line":"Events are a bit more scalable in it\u0027s design (maybe not the SQL backend)."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"Other deployer impact"},{"line_number":119,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_9824d2b0","line":116,"updated":"2014-12-16 01:43:06.000000000","message":"Good to hear that for less data.\n\nDid we have some data for such estimation sample vs event (if this spec adopted and implemented) ?","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":113,"context_line":"-------------------------------"},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"Less sample data. Less equivalent data in Events (because of trait filtering)."},{"line_number":116,"context_line":"Events are a bit more scalable in it\u0027s design (maybe not the SQL backend)."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"Other deployer impact"},{"line_number":119,"context_line":"---------------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_3e2d8790","line":116,"in_reply_to":"3a961159_9824d2b0","updated":"2015-01-20 13:46:53.000000000","message":"not exactly. it\u0027s somewhat dependent on how your event_definitions file is configured. by default, our samples stores the entire notification message. the event_definitions essentially forces deployers to specify specific values rather than store all","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":7049,"name":"Kai Qiang Wu(Kennan)","email":"wkq5325@gmail.com","username":"Kennan"},"change_message_id":"ada1cfd17c19f18e82b2ae7745930d754cc252b2","unresolved":false,"context_lines":[{"line_number":120,"context_line":""},{"line_number":121,"context_line":"We should turn on store_events option by default. This will probably require"},{"line_number":122,"context_line":"deployers to use event_connection option as it probably isn\u0027t advisable to"},{"line_number":123,"context_line":"store sample and event data together but they could."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Developer impact"},{"line_number":126,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_f8495661","line":123,"updated":"2014-12-16 01:43:06.000000000","message":"So here, for deployer, you means  \n\nFor best practice, they need a separated database for the event ?\n\nThey can also use same db as meters if they like to do.\n\nRight ?","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"fdcb0430797d3feecd1eb6ddf8a6e2084996b507","unresolved":false,"context_lines":[{"line_number":120,"context_line":""},{"line_number":121,"context_line":"We should turn on store_events option by default. This will probably require"},{"line_number":122,"context_line":"deployers to use event_connection option as it probably isn\u0027t advisable to"},{"line_number":123,"context_line":"store sample and event data together but they could."},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"Developer impact"},{"line_number":126,"context_line":"----------------"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a961159_be6fb7c3","line":123,"in_reply_to":"3a961159_f8495661","updated":"2015-01-20 13:46:53.000000000","message":"right. you can store all your data (event and samples and alarms) on the same db (assuming support) or you can split it depending on needs... this functionality currently exists. i\u0027m just reiterating it.","commit_id":"5f7b901db1f4b6cd1c8566e9923b127b315558b7"},{"author":{"_account_id":9562,"name":"Ildiko Vancsa","email":"ildiko.vancsa@gmail.com","username":"ildikov"},"change_message_id":"0697af1b89f224949abc243edff15d3362f2fcf8","unresolved":false,"context_lines":[{"line_number":103,"context_line":"Pipeline impact"},{"line_number":104,"context_line":"---------------"},{"line_number":105,"context_line":""},{"line_number":106,"context_line":"Switch to disable \"volume\u003d1\" meters by default. Indirectly, we should probably"},{"line_number":107,"context_line":"add a pipeline for Events."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Other end user impact"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_9cee03b4","line":106,"updated":"2015-02-18 08:07:01.000000000","message":"Is this still applicable? I mean that this patch cover the disable option: https://review.openstack.org/#/c/156747/ . I mean this patch could be referenced here as a/the solution.","commit_id":"4af3b3e215979b33ce036d0510e146477e93d2b0"},{"author":{"_account_id":9562,"name":"Ildiko Vancsa","email":"ildiko.vancsa@gmail.com","username":"ildikov"},"change_message_id":"0697af1b89f224949abc243edff15d3362f2fcf8","unresolved":false,"context_lines":[{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Users STILL have the option to keep these meters but we should advocate they"},{"line_number":113,"context_line":"use Events instead. This will change how users query their data so we should"},{"line_number":114,"context_line":"probably document it."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"Performance/Scalability Impacts"},{"line_number":117,"context_line":"-------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_dc123bb3","line":114,"updated":"2015-02-18 08:07:01.000000000","message":"I would prefer to have a deprecation model for these meters. Not as the part of this spec, but to mention that it would be nice to have these meters deprecated after a certain time period. And also document in the Developer docs in the \"how to add new meters\" part that the \u0027volume\u003d1\u0027 meters should go to events. So I would force a bit that this tendency should not be continued.","commit_id":"4af3b3e215979b33ce036d0510e146477e93d2b0"},{"author":{"_account_id":9562,"name":"Ildiko Vancsa","email":"ildiko.vancsa@gmail.com","username":"ildikov"},"change_message_id":"0697af1b89f224949abc243edff15d3362f2fcf8","unresolved":false,"context_lines":[{"line_number":175,"context_line":"Documentation Impact"},{"line_number":176,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":177,"context_line":""},{"line_number":178,"context_line":"- mark meters in measurement as available as Events and add a link to events."},{"line_number":179,"context_line":""},{"line_number":180,"context_line":""},{"line_number":181,"context_line":"References"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da86d52c_5c264b17","line":178,"updated":"2015-02-18 08:07:01.000000000","message":"Maybe add a short point here about the how to contribute part that non-metric meters should go to the events store as opposed to converted into samples, as I mentioned above.","commit_id":"4af3b3e215979b33ce036d0510e146477e93d2b0"}],"specs/liberty/deprecate-existence-meters.rst":[{"author":{"_account_id":7478,"name":"Nadya Shakhat","email":"nadmi4@gmail.com","username":"nprivalova"},"change_message_id":"206046b7d42479086fbc9470fa7196cac216cc91","unresolved":false,"context_lines":[{"line_number":93,"context_line":"---------------"},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Audit data. This is an issue that already exists and will just be migrated from"},{"line_number":96,"context_line":"Samples to Events. It should be possible to add a tag to the event_definition"},{"line_number":97,"context_line":"file to mark data as audit. I is technically possible to redirect audit data to"},{"line_number":98,"context_line":"a separate db using event pipeline[4]"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a50d1a3_03a41e55","line":96,"updated":"2015-07-20 08:50:34.000000000","message":"I \u003d\u003e It","commit_id":"7824b10dd7305bc3884ca11979f70af8fe7ba08b"},{"author":{"_account_id":6537,"name":"gordon chung","email":"gord@live.ca","username":"chungg"},"change_message_id":"c1183cc6135856f1399156b073ccf1450ae76060","unresolved":false,"context_lines":[{"line_number":93,"context_line":"---------------"},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"Audit data. This is an issue that already exists and will just be migrated from"},{"line_number":96,"context_line":"Samples to Events. It should be possible to add a tag to the event_definition"},{"line_number":97,"context_line":"file to mark data as audit. I is technically possible to redirect audit data to"},{"line_number":98,"context_line":"a separate db using event pipeline[4]"},{"line_number":99,"context_line":""}],"source_content_type":"text/x-rst","patch_set":5,"id":"3a50d1a3_a102b86d","line":96,"in_reply_to":"3a50d1a3_03a41e55","updated":"2015-07-21 12:50:27.000000000","message":"Done","commit_id":"7824b10dd7305bc3884ca11979f70af8fe7ba08b"}]}