mirror of
https://github.com/hanzoai/otel-collector.git
synced 2026-10-30 18:26:25 +00:00
Rename ONLY the physical ClickHouse DATABASE/TABLE identifiers the schema-migrator CREATEs and the exporters WRITE, matching the o11y read plane + the data-preserving RENAME migration (hanzoai/o11y#28): databases: signoz_{traces,metrics,logs,metadata,analytics,meter} -> o11y_{traces,metrics,logs,metadata,analytics,meter} tables: (distributed_)signoz_{index_v3,index_v2,error_index_v2,spans} -> (distributed_)o11y_{index_v3,index_v2,error_index_v2,spans} Word-boundary anchored (\bsignoz_<db>\b) so wire contracts are untouched: spanmetrics/usage METRIC names (signoz_calls_total, signoz_latency, signoz_*_count/_bytes, signoz_metadata_exporter_json_logs_processed, signoz_normalize_operator_logs_processed), signoz.* resource ATTRIBUTES (signoz.gen_ai.*), OTel component TYPE strings (signozclickhousemetrics, signozclickhousemeter, signozlogspipeline, signozllmpricing), and all github.com/SigNoz/* deps + LICENSE/NOTICE attribution all preserved. Coordinated cutover: deploy this collector, run o11y#28 RENAME migration, then deploy o11y + cloud readers — together, or telemetry blackholes. go build ./... = 0. schema-migrator tests green. Two pre-existing test failures (flaky TestExporterPushTracesData usage-collector timing; o11ydatastoremeter go.signoz.io scope-name debrand) reproduce identically on unmodified v0.144.7.