Task · MDE-0033

Honor configured collector concurrency without distorting health

Description

Release review finding P1.6 remains live at src/meraki_dashboard_exporter/collectors/manager.py:38-49. Shipped defaults configure five concurrent collectors but derive an effective limit of two from the serving executor, while admission expiry can consume the collector timeout and risks being confused with collector health. The effective concurrency contract must be explicit, capacity-safe, and keep queue pressure separate from endpoint failure accounting.

Acceptance Criteria

Definition of Done

Implementation Plan

Root-owned manager seam shared with MDE-0032: make shipped effective collector concurrency intentional and keep admission expiry separate from health, with targeted concurrent tests and operator docs.

Implementation Notes

Shipped defaults intentionally admit two collectors from executor workers 10 divided by per-collector fan-out 5; warning diagnostics name every input, and admission expiry remains separate from health accounting. Generated config docs were refreshed. Integrated gate: 2827 passed.

Final Summary

Made the effective collector-concurrency contract explicit, pinned shipped defaults and admission-expiry health behavior, and regenerated operator documentation; just check and just ci pass.

View the source file on GitHub