Batch Scrape Fails when Some Resources within a Batch do not have a Particular Metric

[hkfgo]

Report

This is an edge case where metric is available for some resources in a batch but not others. Concrete example is the AzureSQL type resource, where certain metrics are only available for vCore type databases.

Expected Behavior

Metrics should be published for applicable resources.

Actual Behavior

Whole batch fails.

Steps to Reproduce the Problem

Run a Promitor deployment targeting vCore and DTU databases, some metrics like cpu_limit will disappear.

Component

Scraper

Version

Scraper-v2.12.0

Configuration

Configuration:

# Add your scraping configuration here

Logs

example

Platform

None

Contact Details

No response

[github-actions]

Thank you for opening an issue! We rely on the community to maintain Promitor. (Learn more)

Is this something you want to contribute?