)]}'
{"doc/source/specs/osh-required-alert-list.rst":[{"author":{"_account_id":11636,"name":"Mateusz Blaszkowski","email":"mateusz.blaszkowski@intel.com","username":"mateuszb"},"change_message_id":"bd5160983bbc10d52e78375250516ac6a9c1263a","unresolved":false,"context_lines":[{"line_number":43,"context_line":"2. Link Down / log:dmesg\u003dlink down|Link is Down"},{"line_number":44,"context_line":""},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"Logging-based Alert Requirements (Mariadb)"},{"line_number":47,"context_line":"------------------------------------------"},{"line_number":48,"context_line":""},{"line_number":49,"context_line":"(alert title / alert trigger rule)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f485f77_cf02ba09","line":46,"updated":"2017-11-15 13:44:52.000000000","message":"In general, I\u0027d avoid sticking to MariaDB and assume that other database may be used. So instead of retrieving MariaDB logs, we can retrieve database exceptions from oslo.db (https://github.com/openstack/oslo.db/blob/128e5438b14e596fc01032cc3bd1210391e77e19/oslo_db/exception.py - DBError and its children)","commit_id":"682a0c61bd2bc9bd4cb1ce56c09de3a3595542a7"},{"author":{"_account_id":11636,"name":"Mateusz Blaszkowski","email":"mateusz.blaszkowski@intel.com","username":"mateuszb"},"change_message_id":"bd5160983bbc10d52e78375250516ac6a9c1263a","unresolved":false,"context_lines":[{"line_number":58,"context_line":"1."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Logging-based Alert Requirements (OpenStack)"},{"line_number":62,"context_line":"--------------------------------------------"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"(alert title / alert trigger rule)"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f485f77_b925875e","line":61,"updated":"2017-11-15 13:44:52.000000000","message":"I\u0027ve been also thinking about alerts related to Nova services issues (like compute service is down) - but I don\u0027t have an appropriate log pattern right now.","commit_id":"682a0c61bd2bc9bd4cb1ce56c09de3a3595542a7"},{"author":{"_account_id":11636,"name":"Mateusz Blaszkowski","email":"mateusz.blaszkowski@intel.com","username":"mateuszb"},"change_message_id":"bd5160983bbc10d52e78375250516ac6a9c1263a","unresolved":false,"context_lines":[{"line_number":63,"context_line":""},{"line_number":64,"context_line":"(alert title / alert trigger rule)"},{"line_number":65,"context_line":"1. No Free Vol Capacity / log:cinder\u003dfree_capacity_gb: 0"},{"line_number":66,"context_line":"2. Cinder-Ceph Conn Error / log:cinder\u003derror calling connect: errno EINVAL"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Metric-based Alert Requirements"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f485f77_cf2bda7f","line":66,"updated":"2017-11-15 13:44:52.000000000","message":"Proposal: average API response time (especially for Nova, Neturon) within a specified period of time is higher than a threshold. Example nova-api-osapi log:\n\n  2017-11-15 12:07:06.505 1 INFO nova.osapi_compute.wsgi.server [req-cce1f487-68c2-4011-b3e8-c80e7376123c abb32d12995248b696eebaf10cd0270f dbb3940c171a427198c6a3b6a8772c45 - default default] 100.200.1.7,10.244.1.0 \"GET /v2/dbb3940c171a427198c6a3b6a8772c45/servers/detail?all_tenants\u003d1\u0026limit\u003d100 HTTP/1.1\" status: 200 len: 206 time: 0.0661469","commit_id":"682a0c61bd2bc9bd4cb1ce56c09de3a3595542a7"},{"author":{"_account_id":11636,"name":"Mateusz Blaszkowski","email":"mateusz.blaszkowski@intel.com","username":"mateuszb"},"change_message_id":"bd5160983bbc10d52e78375250516ac6a9c1263a","unresolved":false,"context_lines":[{"line_number":64,"context_line":"(alert title / alert trigger rule)"},{"line_number":65,"context_line":"1. No Free Vol Capacity / log:cinder\u003dfree_capacity_gb: 0"},{"line_number":66,"context_line":"2. Cinder-Ceph Conn Error / log:cinder\u003derror calling connect: errno EINVAL"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"Metric-based Alert Requirements"},{"line_number":70,"context_line":"-------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"1f485f77_8ff602f9","line":67,"updated":"2017-11-15 13:44:52.000000000","message":"A new section for RabbitMQ alerts would be nice. We could catch transport related errors basing on oslo.messaging exceptions: https://github.com/openstack/oslo.messaging/blob/master/oslo_messaging/exceptions.py","commit_id":"682a0c61bd2bc9bd4cb1ce56c09de3a3595542a7"}]}