Allow for Metric Scraping interval to be defined overall & per-metric via YAML config#473

Merged

tomkerkhove merged 30 commits intotomkerkhove:masterfrom brandonh-msft:brandonh/feature/metric-scraping-interval-impl

Mar 29, 2019

+315-220

Commits on Mar 28, 2019

Scraping Interval is not nullable on the metricDefaults in config anymore
brandonh-msft
committed
Utilize the MetricsDeclarationProvider to apply defaults to metrics; don't push this logic down in to the scrapers
brandonh-msft
committed
rename UseCronScheduler to ScheduleMetricScraping
brandonh-msft
committed
Allow MetricScrapingJob to take the Metric to scrape; enables jobs targeting different metrics to be scheduled
brandonh-msft
committed
reworking scraping.interval -> scraping.schedule (string) to be used as a cron expression instead of System.Timespan
brandonh-msft
committed
adding scraper.schedule to metric builder used by UTs
brandonh-msft
committed
moving scheduling from env var -> YAML config
brandonh-msft
committed
add metric scraping schedule validation
brandonh-msft
committed
IEnumerable<T> + yield return refactor for Validators
brandonh-msft
committed
when validating and returning metric detail, apply defaults from metricDefaults to metrics that don't have values for those properties
brandonh-msft
committed
add default scraping schedule + different scraping schedule for some metrics to illustrate cusomizability and new usage of metricDefaults for overall scraping schedule (vs old env variable)
brandonh-msft
committed
Utilize the MetricsDeclarationProvider to apply defaults to metrics; don't push this logic down in to the scrapers
brandonh-msft
committed
reworking scraping.interval -> scraping.schedule (string) to be used as a cron expression instead of System.Timespan
brandonh-msft
committed
adding scraper.schedule to metric builder used by UTs
brandonh-msft
committed
add default scraping schedule + different scraping schedule for some metrics to illustrate cusomizability and new usage of metricDefaults for overall scraping schedule (vs old env variable)
brandonh-msft
committed
temp: working on UTs
brandonh-msft
committed
fixing declaration provider's default assigning
brandonh-msft
committed
deserializing scraping default w/ its own deserializer
brandonh-msft
committed
adding validation to scraping default YAML item
brandonh-msft
committed
adding scraping default value to default instance of declaration builder for UTs
brandonh-msft
committed
conforming Richard's changes to the new metricDefaults architecture
brandonh-msft
committed
codeFactor fix
brandonh-msft
committed
fixing resharper warnings
brandonh-msft
committed
supporting docs for metric scraping interval change
brandonh-msft
committed
move metric resourceGroupName -> new optional area of metric definition docs
brandonh-msft
committed
this catch no longer needed due to internal refactoring of deserialization & validation
brandonh-msft
committed
remove redundant setting of metricDefaults in UT declaration builder
brandonh-msft
committed
whoops
brandonh-msft
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Allow for Metric Scraping interval to be defined overall & per-metric via YAML config#473

Commits on Mar 28, 2019

Scraping Interval is not nullable on the metricDefaults in config anymore

Utilize the MetricsDeclarationProvider to apply defaults to metrics; don't push this logic down in to the scrapers

rename UseCronScheduler to ScheduleMetricScraping

Allow MetricScrapingJob to take the Metric to scrape; enables jobs targeting different metrics to be scheduled

reworking scraping.interval -> scraping.schedule (string) to be used as a cron expression instead of System.Timespan

adding scraper.schedule to metric builder used by UTs

moving scheduling from env var -> YAML config

add metric scraping schedule validation

IEnumerable<T> + yield return refactor for Validators

when validating and returning metric detail, apply defaults from metricDefaults to metrics that don't have values for those properties

add default scraping schedule + different scraping schedule for some metrics to illustrate cusomizability and new usage of metricDefaults for overall scraping schedule (vs old env variable)

Utilize the MetricsDeclarationProvider to apply defaults to metrics; don't push this logic down in to the scrapers

reworking scraping.interval -> scraping.schedule (string) to be used as a cron expression instead of System.Timespan

adding scraper.schedule to metric builder used by UTs

add default scraping schedule + different scraping schedule for some metrics to illustrate cusomizability and new usage of metricDefaults for overall scraping schedule (vs old env variable)

temp: working on UTs

fixing declaration provider's default assigning

deserializing scraping default w/ its own deserializer

adding validation to scraping default YAML item

adding scraping default value to default instance of declaration builder for UTs

conforming Richard's changes to the new metricDefaults architecture

codeFactor fix

fixing resharper warnings

supporting docs for metric scraping interval change

move metric resourceGroupName -> new optional area of metric definition docs

this catch no longer needed due to internal refactoring of deserialization & validation

remove redundant setting of metricDefaults in UT declaration builder

whoops

Commits on Mar 29, 2019

Merge branch 'master' into brandonh/feature/metric-scraping-interval-impl

Merge branch 'master' into brandonh/feature/metric-scraping-interval-impl