Description
GCI-0046 compares only scrape_interval. OTel pull receivers such as hostmetrics use collection_interval, which also sets DPM. Lab stacks carry 10s and 15s collection_interval values that GCI-0046 does not see. Extend the same in-memory parser and view rather than adding a second surface.
Acceptance Criteria
- #1 collection_interval on wired OTel pull receivers is parsed and compared with the default alongside scrape_interval
- #2 The view states which attribute produced each interval
Definition of Done
- #1 just test
- #2 just tf-validate
- #3 just check-identifiers and just no-em-dashes both return clean
Implementation Notes
Only explicit collection_interval on wired non-prometheus receivers is read; receiver defaults differ, so omission is not guessed. Live check on robknight OTel pipelines matched grep, and correctly skipped an unwired host_metrics/datadog receiver at 10s. Existing scrape_* record keys keep their names and now include collection intervals; interval_attributes names the source.
Final Summary
OTel collection_interval now feeds the same faster-than-default comparison, metrics, view, finding and alert as scrape_interval, with an Interval attributes column in risk_fleet_scrape_intervals.