[checkmk-commits] [tribe29/checkmk] 8caaf1: agent_azure: refactor

Branch: refs/heads/1.6.0 Home: https://github.com/tribe29/checkmk Commit: 8caaf14a4d0ce666f94aa525a50dffeb225800ea https://github.com/tribe29/checkmk/commit/8caaf14a4d0ce666f94aa525a50dffeb2… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: M agents/special/agent_azure Log Message: ----------- agent_azure: refactor This commit prepares for several improvements. Note that in preemptive hindsight we make the subscription an extra argument to 'main_subscription'. Change-Id: Ic707940ed5f04dfd5582722d4be9e7bffa4452a0 Commit: 9cbef0471762560beee04f86806cd18883d8dc0d https://github.com/tribe29/checkmk/commit/9cbef0471762560beee04f86806cd1888… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: M agents/special/agent_azure Log Message: ----------- agent_azure: do not cache empty usage details The Azure API sometimes reports empty usage details for no obvious reason. We should not cache it in these cases, but report an exception to the monitoring server. Change-Id: I09236eec1e1b46ce2052e8c9a1035fa88974e1f6 Commit: 4e2ee4a20935cf7bae893f870a96b8af2a2181e5 https://github.com/tribe29/checkmk/commit/4e2ee4a20935cf7bae893f870a96b8af2… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: M agents/special/agent_azure Log Message: ----------- agent_azure: do not cache result in case of API error Change-Id: Ib8e1d2733b4e8ccb0fd67db1e8e0e14845fae931 Commit: f8166d8421e60b73d61c65f5a10b79708ac83c2f https://github.com/tribe29/checkmk/commit/f8166d8421e60b73d61c65f5a10b79708… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: A .werks/10474 M agents/special/agent_azure Log Message: ----------- 10474 FIX agent_azure: No longer report missing metrics as warning Previously metrics not found in the API response have resulted in a warning reported to the 'Agent Azure Info' service. As it turns out this happens to often to be usefull. Now an info is reported instead of a warning. CMK-3225 Change-Id: I7b405bd9461ba90df78e47c7fe499dd01df42b87 Commit: 2f4549804efac20746674d504fb359389bfc5959 https://github.com/tribe29/checkmk/commit/2f4549804efac20746674d504fb359389… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: M checks/azure_agent_info Log Message: ----------- azure_agent_info: minor refactoring * use check_levels * create subfunctions * do not display empty groups-list Change-Id: If1103ca48b0a65500d6ca8ef7868117489c2134b Commit: 10c24d9abb7e9871645f43d512ee75923b05bfb8 https://github.com/tribe29/checkmk/commit/10c24d9abb7e9871645f43d512ee75923… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: A .werks/10476 M agents/special/agent_azure M checks/azure_agent_info M cmk/gui/plugins/wato/check_parameters/azure.py Log Message: ----------- 10476 azure_agent_info: Add option to pin down monitored resources Since werk 10475 services no longer go to UNKNOWN if data is missing. If you want to strictly monitor the resources found for monitoring, you can now enable resource pinning in the WATO rule "Azure Agent Info". A rediscovery is required for the "Azure agent info" service. CMK-3225 Change-Id: I813062b0ba18213df124353464d6e3a87be25957 Commit: 62d1ef0646ec15e90b3336f681c823f7f01ae2f2 https://github.com/tribe29/checkmk/commit/62d1ef0646ec15e90b3336f681c823f7f… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: A .werks/10475 M checks/azure.include M checks/azure_databases M checks/azure_sites M checks/azure_storageaccounts M checks/azure_usagedetails M checks/azure_virtualmachines M checks/azure_virtualnetworkgateways Log Message: ----------- 10475 FIX Azure Checkplugins: Go to stale state if info is missing Previously a service resulting from one of the Azure checkplugins went to UNKOWN if the corresponding data was not found in the agent output, as is common for many checkmk services. Unfortunately, this happens too often to be usefull, as the Azure API appears to not allways report the full data. Now the affected services go to a stale state instead. CMK-3225 Change-Id: I880dc9087e0c6380edc08c898aa9b78a0dea0c17 Commit: 5f7e5787ca6a88f1120fd0ac9e96a9311c6b170c https://github.com/tribe29/checkmk/commit/5f7e5787ca6a88f1120fd0ac9e96a9311… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: A .werks/10477 M cmk/special_agents/agent_azure.py Log Message: ----------- 10477 FIX agent_azure: recover from missing metrics Previously the special agent did not return any metric if one or more of the required metrics were not present. It now recovers from those errors and return as many metrics as we can get. CMK-3225 Change-Id: Ic81e29ff5193abb8a3cf5e9f5d2b6d4a38cb83f8 Commit: 08ec1ef7d5b12232b904618a0298ca35af1e0a8c https://github.com/tribe29/checkmk/commit/08ec1ef7d5b12232b904618a0298ca35a… Author: Moritz Kiemer <moritz.kiemer(a)tribe29.com> Date: 2020-01-16 (Thu, 16 Jan 2020) Changed paths: A .werks/10478 M agents/special/agent_azure M checks/azure_agent_info M checks/azure_usagedetails Log Message: ----------- 10478 FIX agent_azure: Do not warn about missing usage details for one hour The "Microsoft.Consumption" API sometimes fails with a timeout. Since the usage information is only updated once every day anyway, we do not warn about such exceptions for the first hour. Only if an errror occurs longer than that, the state will go to CRIT. CMK-3225 Change-Id: Idfe7d4e4a90b12699a817817750448fcda71d33b Compare: https://github.com/tribe29/checkmk/compare/51c190596938...08ec1ef7d5b1