otel configuration | Dagger | Page 1

worldly bough Oct 30, 2024, 2:47 PM

#

is there any way to configure the otlp endpoint that otel trace data is emitting to?

void spear Oct 30, 2024, 3:12 PM

#

worldly bough is there any way to configure the otlp endpoint that otel trace data is emitting...

I think you can set standard otel env variables. Out of curiosity, what otel tooling are you trying to use?

worldly bough Oct 30, 2024, 3:21 PM

#

i just wanted to point it at a dd agent 🙂

worldly bough Oct 30, 2024, 4:22 PM

#

for the record, i know the current monetization route is through the cloud services you have experimentally posted, but there are some of us out there who would love to give you money even if we are sidestepping your cloud offerings to conform with the broader strategic decisions in our companies. had a delightful conversation with lev about this yesterday

sand sparrow Nov 20, 2024, 5:30 PM

#

How did this end up? I have datadog in my environment so did you end up flipping some env variables and everything worked?

worldly bough Nov 20, 2024, 10:46 PM

#

not yet! they made me stop playing and finish up my rds/pg schema deployment lambda builder (which is dagger), but i shall return to this in a week or so 😄

#

they being the folks who pay me lol

worldly bough Dec 11, 2024, 5:06 PM

#

better late than never, i think. i found some other threads under different names for this - one of them had a link here https://github.com/dagger/dagger/blob/ba70be4ef8c2517bf9b683ca49e565cfaa771cae/engine/buildkit/executor_spec.go#L70. So those are how you can point stuff to your dd agent. I did notice that for some reason i was getting errors on otel log message submissions when i was using the http/protobuf protocol, but those went away when i swippy swapped to grpc (so i do think something is broken there, but i truthfully wanted to use grpc anyway, so I just kinda raised an eyebrow and moved on with my day). On the dd agent side, this was the config that worked for me:

apm_config:
  apm_non_local_traffic: false
  enabled: true
  receiver_port: '8126'
logs_enabled: true
otlp_config:
  receiver:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318
  metrics:
    enabled: true
  traces:
    enabled: true
  logs:
    enabled: true

I didn't test all elements of the config exhaustively to figure out what is truly necessary (i.e. is logs_enabled: true is truly necessary or not). That said, i did test out whether or not apm needed to be enabled or not (cuz you know - if i can sneak by without paying for another apm enabled host...), but alas - it was required (I believe it controls the trace service under the covers).

#

and as for which env vars specifically, i set the following in the context that was invoking dagger:

export OTEL_EXPORTER_OTLP_TRACES_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=<url>:4317
export OTEL_EXPORTER_OTLP_LOGS_PROTOCOL=grpc
export OTEL_EXPORTER_OTLP_LOGS_ENDPOINT=<url>:4317

I did not touch the metrics one because in said thread that had the buildkit spec link it alluded to metrics not being implemented yet?

#

@sand sparrow - not trying to be rude with random mentions, but wanted to make sure you saw this ^_^

#otel configuration