)]}'
{"doc/admin-guide-cloud-rst/source/telemetry-alarms.rst":[{"author":{"_account_id":6843,"name":"Phil Hopkins","email":"phil.hopkins@rackspace.com","username":"phil-hopkins-a"},"change_message_id":"bc05fe5490837e23a7164276c8bffc0d68f80d9a","unresolved":false,"context_lines":[{"line_number":148,"context_line":"    Cloud administrator can limit each alarm\u0027s maximum actions"},{"line_number":149,"context_line":"    for three states, and disables normal user to create"},{"line_number":150,"context_line":"    log:// and test:// to avoid bad things happe."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"The sliding time window over which the alarm is evaluated is 30"},{"line_number":153,"context_line":"minutes in this example. This window is not clamped to wall-clock"},{"line_number":154,"context_line":"time boundaries, rather it\u0027s anchored on the current time for each"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a50d1a3_ff31f70b","line":151,"updated":"2015-07-28 12:49:53.000000000","message":"A couple of nits - the sentence should start with the word \"The\" and disables normal user should read \"disables a normal user\". Also happe is misspelled.","commit_id":"3456c84774561bd19bb4fb7842bfe7f7e26eb54b"},{"author":{"_account_id":6843,"name":"Phil Hopkins","email":"phil.hopkins@rackspace.com","username":"phil-hopkins-a"},"change_message_id":"e50245627b71349e51efa0f7ac6805907d2a3207","unresolved":false,"context_lines":[{"line_number":147,"context_line":"    individual project."},{"line_number":148,"context_line":"    The cloud administrator can limit each alarm\u0027s maximum actions"},{"line_number":149,"context_line":"    for three states, and disables a normal user to create"},{"line_number":150,"context_line":"    log:// and test:// to avoid bad things happen."},{"line_number":151,"context_line":""},{"line_number":152,"context_line":"The sliding time window over which the alarm is evaluated is 30"},{"line_number":153,"context_line":"minutes in this example. This window is not clamped to wall-clock"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a50d1a3_1cd8661d","line":150,"updated":"2015-07-28 15:27:35.000000000","message":"I missed this: happen should be happening","commit_id":"2db29f2807d4784bf34ec31ab2ff38f758760a95"},{"author":{"_account_id":14046,"name":"Chris Cannon","email":"ccannon@hp.com","username":"Helimaniac"},"change_message_id":"306c47a49303646fdb1d365e8252b11702ec05bf","unresolved":false,"context_lines":[{"line_number":145,"context_line":".. note::"},{"line_number":146,"context_line":"    Alarm names must be unique for the alarms associated with an"},{"line_number":147,"context_line":"    individual project."},{"line_number":148,"context_line":"    The cloud administrator can limit each alarm\u0027s maximum actions"},{"line_number":149,"context_line":"    for three states, and disables a normal user to create"},{"line_number":150,"context_line":"    log:// and test:// to avoid bad things happening."},{"line_number":151,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a50d1a3_fd35fcda","line":148,"updated":"2015-07-30 16:53:07.000000000","message":"This explanation is not clear, and I believe we should better explain the reasoning for having this option.  I suggest replacing the paragraph starting at line 148 with the following:  \"The cloud administrator can limit the maximum resulting actions for three different states, and the ability for a normal user to create log:// and test:// notifiers is disabled.  This prevents unintentional consumption of disk and memory resources by the Telemetry service.\"","commit_id":"4c31c462c616659d35173dd8a44a92756791d9de"},{"author":{"_account_id":167,"name":"Christian Berendt","email":"berendt@osism.tech","username":"berendt"},"change_message_id":"ad8e390eba78dfef4221e9d902e5252d79e33479","unresolved":false,"context_lines":[{"line_number":147,"context_line":"    individual project."},{"line_number":148,"context_line":"    The cloud administrator can limit the maximum resulting actions"},{"line_number":149,"context_line":"    for three different states, and the ability for a normal user to"},{"line_number":150,"context_line":"    create log:// and test:// notifiers is disabled. This prevents"},{"line_number":151,"context_line":"    unintentional consumption of disk and memory resources by the"},{"line_number":152,"context_line":"    Telemetry service."},{"line_number":153,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"1a4dcd0f_4e4ed6c2","line":150,"updated":"2015-08-03 17:57:21.000000000","message":"Should we use ``log://`` and ``test://`` here?","commit_id":"1156468c548c3bea8b166586bec3bf7e2108bdea"}],"doc/admin-guide-cloud/telemetry/section_telemetry-alarms.xml":[{"author":{"_account_id":6843,"name":"Phil Hopkins","email":"phil.hopkins@rackspace.com","username":"phil-hopkins-a"},"change_message_id":"bc05fe5490837e23a7164276c8bffc0d68f80d9a","unresolved":false,"context_lines":[{"line_number":111,"context_line":"        \u003cpara\u003eAlarm names must be unique for the alarms associated with an individual project.\u003c/para\u003e"},{"line_number":112,"context_line":"        \u003cpara\u003eCloud administrator can limit each alarm\u0027s maximum actions for three states,"},{"line_number":113,"context_line":"          and disables normal user to create log:// and test:// to avoid bad things happe\u003c/para\u003e"},{"line_number":114,"context_line":"      \u003c/note\u003e"},{"line_number":115,"context_line":"      \u003cpara\u003eThe sliding time window over which the alarm is evaluated is 30 minutes in this example. This window is not clamped to wall-clock time boundaries, rather it\u0027s anchored on the current time for each evaluation cycle, and continually creeps forward as each evaluation cycle rolls around (by default, this occurs every minute).\u003c/para\u003e"},{"line_number":116,"context_line":"      \u003cpara\u003eThe period length is set to 600s in this case to reflect the out-of-the-box default cadence for collection of the associated meter. This period matching illustrates an important general principal to keep in mind for alarms:\u003c/para\u003e"},{"line_number":117,"context_line":"      \u003cnote\u003e"}],"source_content_type":"application/xml","patch_set":1,"id":"3a50d1a3_3f2c3fab","line":114,"updated":"2015-07-28 12:49:53.000000000","message":"A couple of nits - the sentence should start with the word \"The\" and disables normal user should read \"disables a normal user\". Also happe is misspelled.","commit_id":"3456c84774561bd19bb4fb7842bfe7f7e26eb54b"},{"author":{"_account_id":6843,"name":"Phil Hopkins","email":"phil.hopkins@rackspace.com","username":"phil-hopkins-a"},"change_message_id":"e50245627b71349e51efa0f7ac6805907d2a3207","unresolved":false,"context_lines":[{"line_number":110,"context_line":"      \u003cnote\u003e"},{"line_number":111,"context_line":"        \u003cpara\u003eAlarm names must be unique for the alarms associated with an individual project.\u003c/para\u003e"},{"line_number":112,"context_line":"        \u003cpara\u003eThe cloud administrator can limit each alarm\u0027s maximum actions for three states,"},{"line_number":113,"context_line":"          and disables a normal user to create log:// and test:// to avoid bad things happen.\u003c/para\u003e"},{"line_number":114,"context_line":"      \u003c/note\u003e"},{"line_number":115,"context_line":"      \u003cpara\u003eThe sliding time window over which the alarm is evaluated is 30 minutes in this example. This window is not clamped to wall-clock time boundaries, rather it\u0027s anchored on the current time for each evaluation cycle, and continually creeps forward as each evaluation cycle rolls around (by default, this occurs every minute).\u003c/para\u003e"},{"line_number":116,"context_line":"      \u003cpara\u003eThe period length is set to 600s in this case to reflect the out-of-the-box default cadence for collection of the associated meter. This period matching illustrates an important general principal to keep in mind for alarms:\u003c/para\u003e"}],"source_content_type":"application/xml","patch_set":2,"id":"3a50d1a3_dc043e7f","line":113,"updated":"2015-07-28 15:27:35.000000000","message":"I missed this: happen should be happening","commit_id":"2db29f2807d4784bf34ec31ab2ff38f758760a95"},{"author":{"_account_id":14046,"name":"Chris Cannon","email":"ccannon@hp.com","username":"Helimaniac"},"change_message_id":"306c47a49303646fdb1d365e8252b11702ec05bf","unresolved":false,"context_lines":[{"line_number":109,"context_line":"      \u003cpara\u003eThis creates an alarm that will fire when the average CPU utilization for an individual instance exceeds 70% for three consecutive 10 minute periods. The notification in this case is simply a log message, though it could alternatively be a webhook URL.\u003c/para\u003e"},{"line_number":110,"context_line":"      \u003cnote\u003e"},{"line_number":111,"context_line":"        \u003cpara\u003eAlarm names must be unique for the alarms associated with an individual project.\u003c/para\u003e"},{"line_number":112,"context_line":"        \u003cpara\u003eThe cloud administrator can limit each alarm\u0027s maximum actions for three states,"},{"line_number":113,"context_line":"          and disables a normal user to create log:// and test:// to avoid bad things happening.\u003c/para\u003e"},{"line_number":114,"context_line":"      \u003c/note\u003e"},{"line_number":115,"context_line":"      \u003cpara\u003eThe sliding time window over which the alarm is evaluated is 30 minutes in this example. This window is not clamped to wall-clock time boundaries, rather it\u0027s anchored on the current time for each evaluation cycle, and continually creeps forward as each evaluation cycle rolls around (by default, this occurs every minute).\u003c/para\u003e"}],"source_content_type":"application/xml","patch_set":3,"id":"3a50d1a3_5d80b049","line":112,"updated":"2015-07-30 16:53:07.000000000","message":"As commented previously in the RST section -- This explanation is not clear, and I believe we should better explain the reasoning for having this option. I suggest replacing the paragraph starting at line 112 with the following: \"The cloud administrator can limit the maximum resulting actions for three different states, and the ability for a normal user to create log:// and test:// notifiers is disabled. This prevents unintentional consumption of disk and memory resources by the Telemetry service.\"","commit_id":"4c31c462c616659d35173dd8a44a92756791d9de"},{"author":{"_account_id":167,"name":"Christian Berendt","email":"berendt@osism.tech","username":"berendt"},"change_message_id":"ad8e390eba78dfef4221e9d902e5252d79e33479","unresolved":false,"context_lines":[{"line_number":110,"context_line":"      \u003cnote\u003e"},{"line_number":111,"context_line":"        \u003cpara\u003eAlarm names must be unique for the alarms associated with an individual project.\u003c/para\u003e"},{"line_number":112,"context_line":"        \u003cpara\u003eThe cloud administrator can limit the maximum resulting actions for three different states,"},{"line_number":113,"context_line":"          and the ability for a normal user to create log:// and test:// notifiers is disabled."},{"line_number":114,"context_line":"          This prevents unintentional consumption of disk and memory resources by the Telemetry service.\u003c/para\u003e"},{"line_number":115,"context_line":"      \u003c/note\u003e"},{"line_number":116,"context_line":"      \u003cpara\u003eThe sliding time window over which the alarm is evaluated is 30 minutes in this example. This window is not clamped to wall-clock time boundaries, rather it\u0027s anchored on the current time for each evaluation cycle, and continually creeps forward as each evaluation cycle rolls around (by default, this occurs every minute).\u003c/para\u003e"}],"source_content_type":"application/xml","patch_set":4,"id":"1a4dcd0f_2eccaa34","line":113,"updated":"2015-08-03 17:57:21.000000000","message":"Should we use \u003cliteral\u003elog://\u003c/literal\u003e and \u003cliteral\u003etest://\u003c/literal\u003e here?","commit_id":"1156468c548c3bea8b166586bec3bf7e2108bdea"}]}