Deploy failed: open-telemetry

[Read Only] Questions and Answers
1

Hello everyone.

My deployments are failing in a strange way and I can’t determine if the problem is in my application. My application is written in Ruby and in principle I have no dependence on the library GitHub - open-telemetry/opentelemetry-collector-contrib: Contrib repository for the OpenTelemetry Collector.

I have configured a Readiness Health Check like this:

image
image422×668 11.5 KB

And the deploy fails me in this way:

image
image2488×874 358 KB

And in the Live Logs I see this error:

2024-09-13T08:15:01.871Z error helper/transformer.go:102 Failed to process entry {"kind": "receiver", "name": "filelog", "data_type": "logs", "operator_id": "json_parser", "operator_type": "json_parser", "error": "ReadMapCB: expect { or n, but found #, error found in #1 byte of ...|# Logfile c|..., bigger context ...|# Logfile created on 2024-09-13 08:15:01 +0000 by l|...", "action": "send"}

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/helper.(*TransformerOperator).HandleEntryError

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/helper/transformer.go:102

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/helper.(*ParserOperator).ParseWith

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/helper/parser.go:140

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/helper.(*ParserOperator).ProcessWithCallback

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/helper/parser.go:112

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/helper.(*ParserOperator).ProcessWith

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/helper/parser.go:98

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/parser/json.(*Parser).Process

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/parser/json/parser.go:24

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/helper.(*WriterOperator).Write

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/helper/writer.go:53

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/operator/input/file.(*Input).emit

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/operator/input/file/input.go:54

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/fileconsumer/internal/reader.(*Reader).ReadToEnd

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/fileconsumer/internal/reader/reader.go:90

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/fileconsumer.(*Manager).consume.func1

github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza@v0.102.0/fileconsumer/file.go:164

Could you tell me if this has something to do with the way Qovery does the Health Check? I don’t recognize anything in my application about this library and I have other pods in the same application based on the same code that do deploy correctly, but their health check is different, that’s why I think it can be something of Qovery.

Thank you in advance and best regards!

2

Hi @dolarsrg,

could you please share the Qovery URL of the application you’re trying to deploy?

3

I’m closing this topic. feel free to re-open it if you still face any issue.