Repository navigation
feat(otlp-receiver): Otel receiver config value defaults and missing env vars - #80
Merged
Merged
Conversation
Adds a run-data-migration init container that runs after run-migration and before the API starts. It uses the API image with -role=migrate-data to run the versioned data migration registry, which backfills schema_versions, transformation_configs, join_configs, and sink_configs for pre-v3 pipelines.
…nabled (ETL-1058)
Nuzhnov
approved these changes
May 7, 2026
feat: add run-data-migration init container for pipeline v2→v3 promotion (ETL-676)
ashish-bagri
approved these changes
May 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
maxConcurrentRequestsandnatsChunkSizeas first-class chart values wired toGLASSFLOW_OTLP_MAX_CONCURRENT_REQUESTSandGLASSFLOW_OTLP_NATS_CHUNK_SIZEGLASSFLOW_OTEL_METRICS_ENABLEDandGLASSFLOW_OTEL_LOGS_ENABLEDin its configmap, so both defaulted totrueat startup and the receiver always tried to connect to the OTel collector — even when it wasn't deployed. This caused noisy connection errors in the logs. Now both flags are driven byglobal.observability.metrics.enabled/global.observability.logs.enabled, matching what the API configmap already does.Config changes
sources.otlpReceiver.maxConcurrentRequests50GLASSFLOW_OTLP_MAX_CONCURRENT_REQUESTSsources.otlpReceiver.natsChunkSize1000GLASSFLOW_OTLP_NATS_CHUNK_SIZEglobal.observability.metrics.enabledtrueGLASSFLOW_OTEL_METRICS_ENABLEDglobal.observability.logs.enabledfalseGLASSFLOW_OTEL_LOGS_ENABLEDRelated