Open telemetry collector

[filhodanuvem]

Hello community, did someone managed to run an otel collector on render.com ?
I have a collector running as a free web service on render but requests to the service causes timeouts.
From the render logs, the service is healthy and exposed by the port 4318.

The collector is using a receiver otpl with http protocol

receivers:
  otlp:
    protocols:
      http: 
        endpoint: 0.0.0.0:4318

I’ve took a look on other topics, but there’s no direct answered on them. I assume this is an usuable use case for render users. I could create a documentation on it as soon as I have it running.

Docker deployment stops 30 seconds after it's live `Received signal from OS {"signal": "terminated"}`

I am trying to deploy an instance of the OpenTelemetry Collector on Render using a private service. It seems to build fine, and be deployed, but around 30 seconds after, it shuts down. [shot-9xfm3vQY] I believe this to be a Render issue because it works fine locally and the message Received signal from OS {"signal": "terminated"} sounds like it’s coming from the Render system around the container. I saw this post: Deploy of Docker as private service fails with timeout, and thought it could …

OpenTelemetry Collector w/ ZipKin

Has anyone set up an OpenTelemetry Collector on Render? Are there any examples we can follow about how to do this? https://github.com/open-telemetry/opentelemetry-collector

[John_B]

I’m not familiar with open telemetry but let me share some details:

• We only permit external connections to webservices via port 443, in your screenshot we’ve picked 4318 so they would be available as port 443 via the external address
• Services using free instance types can’t use the internal network

Maybe that’s enough to help you understand here?

Regards,

John B
Render Support, UTC+1

[filhodanuvem]

That helped a lot John, I probably missed that a public service will be exposed always on the port 443, also the log message mentioning the auto detection of 4318 confused me.
I think that was the only problem, but I’m finishing my tests, thank you.

[filhodanuvem]

We can close this topic. As mentioned before the port that I was trying to use to reach out the otel collector was the problem. As mentioned by John my application should send metrics to the port 443.

In case someone use this topic as a documentation; a better approach would be having the service deployed as a private one on Render, or at least enable the otel collector to work with an authorization layer, there are different extensions in that direction: