-
BREAKING CHANGE: The package-level scrape instrumentation collectors in
pkg/promutilhave been replaced bypromutil.ScrapeMetricsandpromutil.NewScrapeMetrics(registry). Go library users importing those metrics must create apromutil.ScrapeMetricsvalue (which registers its counters on theprometheus.Registereryou supply) and use its fields orCollectors()method instead. Users ofexporter.Metricswill need to build clients withpromutil.DeprecatedScrapeMetrics()to continue using them, or otherwise switch topromutil.ScrapeMetricsandpromutil.NewScrapeMetrics(registry). Bothexporter.UpdateMetricsandexporter.MetricsAPIs are now deprecated and will be removed in a future release. -
BREAKING CHANGE:
cloudwatch.NewClient,tagging.NewClient, andclients.NewFactorynow require a*promutil.ScrapeMetricsargument for AWS API request instrumentation. Build one withpromutil.NewScrapeMetrics(registry), or passpromutil.Discardto disable scrape telemetry.
- [CHANGE] Add
pkg/config.Configandpkg/metrics.Scraperso Go applications can embed YACE with isolated scrape configuration, scrape instrumentation collectors, and one-shot CloudWatch scraping by @ArthurSens. #1857 - [CHANGE] Deprecate the legacy
pkg/exporterentrypoints and defaults by @ArthurSens. Useconfig.DefaultConfig(),config.DefaultMetricsPerQuery,config.DefaultLabelsSnakeCase,config.DefaultTaggingAPIConcurrency,config.DefaultCloudwatchConcurrency, instead of the constants from the exporter package. #1857 - [ENHANCEMENT] pkg/clients: use method-value closures to avoid defeating dead-code elimination by @roidelapluie. #1867
- [ENHANCEMENT] enhance RDS metrics handling by filtering valid DB instance identifiers from ARNs by @andriikushch. #1877
Dependency updates