How is your experience with the OutSystems Community?
9
Views
2
Comments
Found Test Connection Log Streaming to DataDog Error (O11)
Platform Version
11.43.0 (Build 48120)

Hi Team,

We have POC Project about Log Streaming from OutSystems O11 (Dev environment) to DataDog,

But we faced the issue when click test connection in Lifetime

Error Message is about could not established connection


Please see our step have we done as below

1. Enable Log Subscribe in Dev Environment

2. Sign-up an account in DataDog

3. Download and install DataDog Agent and Open Telemetry in VM (Private Network)

4. Change API Key from DataDog in Data Dog config file

5. Allow port 4318 and IP Address of Dev Environment

6. Setup Log Streaming Config in LifeTime as picture below

6.1 Protocol: OTLP/HTTP

6.2 Endpoint: https://VM ip address:4318/v1/logs

6.3 New API Key: API key in step 4

6.4 New bearer token: From service account in DataDog



ps. We already read official document from OutSystems https://success.outsystems.com/documentation/11/monitoring_and_troubleshooting_apps/introduction_to_log_streaming/configuring_the_log_streaming_service_in_lifetime/stream_logs_to_datadog/

Any step that we missing, please advice.

2026-09-26 04-01-21
Huarlem Lima

The empty "Error detail" plus the "Failed to deserialize JSON" toast usually means LifeTime got no response at all from the endpoint, so this looks like a network/TLS issue rather than auth.

A couple of things might be causing it:

1) The collector VM is in a private network. If your environment is on OutSystems Cloud, it probably can't reach that IP. The endpoint needs to be reachable from the environment, so either a public endpoint or connectivity through VPN / private gateway.

2) You're using https:// with an IP address. The OTLP HTTP receiver on 4318 listens on plain HTTP by default, so unless TLS is configured on the collector with a valid certificate, the handshake will fail. Can you check if the otlp receiver in the collector config has a tls section?

A quick test is to call the endpoint with curl from a machine outside that network. If it doesn't answer there, LifeTime won't reach it either.

UserImage.jpg
Suthisak Pansaengthong

Dear Huarlem,

Thank you for your reply.

We have a question about point 1

1) The collector VM is in a private network. If your environment is on OutSystems Cloud, it probably can't reach that IP. The endpoint needs to be reachable from the environment, so either a public endpoint or connectivity through VPN / private gateway. 

--> We have setup VPN in Life Time as picture below.

but still get the error and we found information in OutSystems Document that the Log streaming will stream from OutSystems data platform.

Do we need VM to allow IP 52.46.74.134, 18.143.210.11 and, 52.74.33.192 or not.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.