What

Audit monitoring_system collectors, plugins, exporters, and placeholder paths, then classify their support level as production, experimental, test-only, or remove.

Part of kcenon/common_system#684.

The 2026-05-21 analysis found a high count of placeholder/stub markers in monitoring-related benchmarks, tests, transports, collectors, and plugin areas. This issue should separate harmless test scaffolding from public functionality that needs documentation or implementation.

Why

The README describes a modern observability platform with collectors, tracing, alerting, plugins, and exporters. Users need to know which collectors/plugins are production-ready versus examples or placeholders. Without that classification, feature claims are hard to verify and downstream systems cannot make safe integration decisions.

Where

• include/kcenon/monitoring/collectors/**
• include/kcenon/monitoring/plugins/**
• include/kcenon/monitoring/exporters/**
• src/**
• tests/**
• benchmarks/**
• docs/plugin_*
• README.md feature matrix

How

Approach

1. Audit TODO, FIXME, HACK, stub, placeholder, and not implemented markers across headers, sources, tests, examples, and benchmarks.
2. Build a support-status table for each collector/plugin/exporter.
3. Move test-only stub language out of user-facing docs where appropriate.
4. Mark experimental public features explicitly in docs and headers.
5. Open follow-up implementation issues for any feature documented as production but backed by a stub/placeholder.

Acceptance Criteria

• Support-status table posted in this issue or committed under docs/
• README and plugin docs reflect the support status table
• Public APIs do not imply production support for placeholder implementations
• Follow-up issues opened for production-claimed but incomplete collectors/plugins/exporters
• [EPIC] Ecosystem hardening follow-up from 2026-05-21 analysis common_system#684 receives the final monitoring summary

Verification

• rg -n -i "TODO|FIXME|HACK|stub|placeholder|not implemented" include src tests benchmarks results are either eliminated or accounted for in the support table
• Relevant collector/plugin tests pass on the standard CI preset