From 6a05a1eec2381527f4d012cfe70f906ba63bf4b1 Mon Sep 17 00:00:00 2001 From: "gauthier.ampe@fr.clara.net" Date: Wed, 14 Aug 2019 13:53:27 +0200 Subject: [PATCH] MON-484 Ajust monitor telemetry ingress nosent --- cloud/azure/iothubs/monitors-iothubs.tf | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/cloud/azure/iothubs/monitors-iothubs.tf b/cloud/azure/iothubs/monitors-iothubs.tf index ffb1764..f744dbb 100644 --- a/cloud/azure/iothubs/monitors-iothubs.tf +++ b/cloud/azure/iothubs/monitors-iothubs.tf @@ -478,10 +478,9 @@ resource "datadog_monitor" "too_many_d2c_telemetry_ingress_nosent" { #For this monitor, the avg is needed to smooth the -1 and +1 that we meet regularly. With just a tiny diff like -1 / + 1, if we put 0.3 it should not ring anymore. But there is a bigger difference (exemple 20) The average will be strongly raised and an alert will be triggered. query = < ${var.too_many_d2c_telemetry_ingress_nosent_rate_threshold_critical} + 100-(default(avg:zure.devices_iothubs.d2c.telemetry.ingress.success${module.filter-tags.query_alert} by {resource_group,region,name}.as_rate() / + avg:azure.devices_iothubs.d2c.telemetry.ingress.all_protocol${module.filter-tags.query_alert} by {resource_group,region,name}.as_rate(),1) + * 100) > ${var.too_many_d2c_telemetry_ingress_nosent_rate_threshold_critical} EOQ thresholds = {