{"action":"opened","issue":{"url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1091","repository_url":"https://api.github.com/repos/rcbops/rpc-openstack","labels_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1091/labels{/name}","comments_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1091/comments","events_url":"https://api.github.com/repos/rcbops/rpc-openstack/issues/1091/events","html_url":"https://github.com/rcbops/rpc-openstack/issues/1091","id":155782322,"number":1091,"title":"CDM alarms should have both warning and critical threshold","user":{"login":"kstev","id":2184858,"avatar_url":"https://avatars.githubusercontent.com/u/2184858?v=3","gravatar_id":"","url":"https://api.github.com/users/kstev","html_url":"https://github.com/kstev","followers_url":"https://api.github.com/users/kstev/followers","following_url":"https://api.github.com/users/kstev/following{/other_user}","gists_url":"https://api.github.com/users/kstev/gists{/gist_id}","starred_url":"https://api.github.com/users/kstev/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kstev/subscriptions","organizations_url":"https://api.github.com/users/kstev/orgs","repos_url":"https://api.github.com/users/kstev/repos","events_url":"https://api.github.com/users/kstev/events{/privacy}","received_events_url":"https://api.github.com/users/kstev/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-05-19T16:39:53Z","updated_at":"2016-05-19T16:39:53Z","closed_at":null,"body":"##### What version (commit) do you encounter this issue on?\r\nr12.2.0\r\n\r\n##### What type of issue is this (bug, feature, documentation, regression)?\r\nFeature\r\n\r\n##### What is the expected behavior?\r\nCDM alarms should possess a CRITICAL threshold so that a Rackspace support ticket will be generated on tripping the alarm.\r\n \r\n##### What is actually happening?\r\nFor example, the cpu_check alarm will never generate a support ticket as there is no critical threshold defined. This being the case, 90% of Rackspace customers will never derive much value from this alarm.\r\n\r\n##### How can we reproduce this issue?\r\nGenerate very high CPU (stress?). Monitor for MaaS alert tickets. See none\r\n\r\n##### How can we verify your issue is addressed?\r\nGenerate very high CPU (stress?). Monitor for MaaS alert tickets. See alerts\r\n\r\n##### If this is a large issue, what can be done immediately to alleviate the issue while working on a longer-term solution?\r\n\r\n##### What is your evaluation on the importance of this issue, and why?\r\nLow. Not having a critical threshold did cause us to not see an issue and therefore caused a 24 hour \"outage\" for one of my customers that experienced a hardware issue. That being said, it was probably an edge case.\r\n\r\n##### What branches / milestones do you believe this issue should target?\r\n###### The list below is what is currently supported for backports\r\n###### Remove branches (lines) you do not wish to target.\r\n- [ ] Master\r\n- [ ] liberty-12.2\r\n- [ ] liberty-12.1\r\n- [ ] kilo\r\n"}}