alloy icon indicating copy to clipboard operation
alloy copied to clipboard

Alloy version 1.4.2 not reporting correctly cloudwatchexporter metrics

Open diegobelotti opened this issue 4 months ago • 1 comments

What's wrong?

After upgrading from 1.3 to 1.4 some metrics are saved as 0, see attached image to clarify. Image Image

Steps to reproduce

Use V1.3 and 1.4 with this configuration to see value reported as 0 on some metrics.

prometheus.exporter.cloudwatch "RDS_prod" { sts_region = "eu-west-1" discovery_exported_tags = { "AWS/RDS" = ["name", "AnsibleEnv"], }

discovery {
	regions     = ["eu-west-1"]
	custom_tags = {
		account = "accountname",
	}
            dimension_name_requirements = ["DBInstanceIdentifier"]
	type = "AWS/RDS"
	metric {
		name       = "CPUUtilization"
		statistics = ["Maximum"]
		period     = "1m0s"
	}
	metric {
		name       = "FreeableMemory"
		statistics = ["Minimum"]
		period     = "5m0s"
	}
	metric {
		name       = "DatabaseConnections"
		statistics = ["Average"]
		period     = "1m0s"
	}
}
decoupled_scraping { }

} prometheus.scrape "RDS_prod" { targets = prometheus.exporter.cloudwatch.RDS_prod.targets forward_to = [prometheus.relabel.RDS_prod.receiver] job_name = "integrations/cloudwatch_exporter" } prometheus.relabel "RDS_prod" { forward_to = [prometheus.remote_write.mimir.receiver] rule { target_label = "job" replacement = "Cwatch" } rule { source_labels = ["tag_AnsibleEnv"] regex = ".test." action = "drop" } rule { target_label = "sistema" replacement = "MAIN" } }

System information

Centos 7 or Rocky 8

Software version

1.4.2

Configuration

No response

Logs

No response

diegobelotti avatar Oct 09 '24 09:10 diegobelotti