What is the module?
terraform-signalfx-detectors/modules/integration_gcp-pubsub-topic/detectors-topics.tf
What is the detector?
terraform-signalfx-detectors/modules/integration_gcp-pubsub-topic/detectors-topics.tf
Describe the bug
When an unavailable MTS is present ratio goes to 100% directly, even if ratio should be a lot lower
Additional contextresponse_code is a dimension of metric topic/send_message_operation_count and not a property, so when a response_code=unavailable datapoint is present signal B is split in two MTS, one with response_code=unavailable and the other one with response_code!=unavailable
So signal signal is also split in two: one with the ratio response_code=unavailable / response_code!=unavailable and the other one with the ratio response_code=unavailable / response_code=unavailable, the second one is always 100%
What is the module? terraform-signalfx-detectors/modules/integration_gcp-pubsub-topic/detectors-topics.tf
What is the detector? terraform-signalfx-detectors/modules/integration_gcp-pubsub-topic/detectors-topics.tf
Describe the bug When an unavailable MTS is present ratio goes to 100% directly, even if ratio should be a lot lower
Additional context
response_codeis a dimension of metrictopic/send_message_operation_countand not a property, so when aresponse_code=unavailabledatapoint is present signalBis split in two MTS, one withresponse_code=unavailableand the other one withresponse_code!=unavailableSo signalsignalis also split in two: one with the ratioresponse_code=unavailable / response_code!=unavailableand the other one with the ratioresponse_code=unavailable / response_code=unavailable, the second one is always 100%