Implement clean namespacing for system-wide metrics #13

Problem

Currently, metrics are being registered with inconsistent naming conventions. To ensure SigNoz/Prometheus dashboards are intuitive, we need a "WaveHouse-first" prefixing strategy. Without this, it becomes difficult to filter WaveHouse-specific data from generic infrastructure metrics in a shared collector.

Proposed Solution

Enforce a strict naming convention across all OTel Meters:

• Prefix: All custom metrics must start with wavehouse_.
• Component Tags: Use OTel attributes to differentiate sources rather than putting them in the name (e.g., wavehouse_events_total with an attribute component=bento vs wavehouse_bento_events).
• Implementation: Standardize the following core names:
  • wavehouse_nats_connections
  • wavehouse_pebble_wal_size
  • wavehouse_bento_events_processed

Alternatives Considered

None

Additional Context

None