jade on Nostr: it seems that #opentelemetry will continue to ship a default configuration that does ...
it seems that #opentelemetry will continue to ship a default configuration that does not work if anyone who doesn't think about otel (read: the average OSS developer; the average customer) runs your software, and this is by design.
i am speechless. my systems will continue to deliberately violate the spec in this respect and only use otel if there's a collector endpoint explicitly configured.
https://github.com/open-telemetry/opentelemetry-specification/issues/3009#issuecomment-2112828775Published at
2024-05-15 18:37:41Event JSON
{
"id": "fe55a01a8d930bea59c76e047fe6cf6d2fb2e2ed90c78be0c9941c2626224cea",
"pubkey": "df7f26fa564153369124acfbadd80e7dab4a7aeba8a12c51fca30e741c29e062",
"created_at": 1715791061,
"kind": 1,
"tags": [
[
"t",
"opentelemetry"
],
[
"proxy",
"https://hachyderm.io/users/leftpaddotpy/statuses/112446083019491032",
"activitypub"
]
],
"content": "it seems that #opentelemetry will continue to ship a default configuration that does not work if anyone who doesn't think about otel (read: the average OSS developer; the average customer) runs your software, and this is by design.\n\ni am speechless. my systems will continue to deliberately violate the spec in this respect and only use otel if there's a collector endpoint explicitly configured.\n\nhttps://github.com/open-telemetry/opentelemetry-specification/issues/3009#issuecomment-2112828775",
"sig": "2ea59e516788e336d5316f157ea4f0da07271eb2ba044f5d92c6280d6774ec48e84b6d82cbe20d635e5abfdba2c47a2fea348f8a28f49c5716ec5558793e2679"
}