THIS FORUM IS NO LONGER ACTIVE. Join us on CNCF Slack: https://cloud-native.slack.com/archives/CJFCJHG4Q.
otel | {"component_kind": "exporter", "component_type": "newrelic", "component_name": "newrelic"}
otel | 2021-01-22T01:37:01.839Z error newrelicexporter/newrelic.go:47 2021/01/22 01:37:01.839525 {"err":"unexpected post response code: 403: Forbidden"}
Unfortunately, you are not yet approved by the Corporate CLA of Splunk, Inc. on Cloud Native Computing Foundation (CNCF).
@/all , I have some meta-news to share about this Gitter channel!
Per this comment, now that OTel has reached Tracing Spec ≥ 1.0, we are formally moving off of Gitter as the "front door" for OpenTelemetry community chat.
Note that individual SIGs may (and will) continue to use Gitter for their own purposes (see a list here), but general-purpose OpenTelemetry community conversations and/or requests to be directed/redirected from new OTel community members should happen in the CNCF opentelemetry Slack channel, not here.
If you have major concerns, please post them to open-telemetry/community#362 rather than starting that discussion here.
Thank you for reading!
@/all , I have some meta-news to share about this Gitter channel!
Per this comment, now that OTel has reached Tracing Spec ≥ 1.0, we are formally moving off of Gitter as the "front door" for OpenTelemetry community chat.
Note that individual SIGs may (and will) continue to use Gitter for their own purposes (see a list here), but general-purpose OpenTelemetry community conversations and/or requests to be directed/redirected from new OTel community members should happen in the CNCF opentelemetry Slack channel, not here.
If you have major concerns, please post them to open-telemetry/community#362 rather than starting that discussion here.
Thank you for reading!
how do you join this slack?
Hello team, I'm trying to create a Docker image of the otel collector but when I run the command make docker-otelcontribcol
, I get the following error
140512693898056:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:ssl/statem/statem_clnt.c:1913:
ERROR: https://dl-cdn.alpinelinux.org/alpine/v3.13/main: Permission denied
WARNING: Ignoring https://dl-cdn.alpinelinux.org/alpine/v3.13/main: No such file or directory
Does anyone know how I can resolve this?
Hello team, I was able to resolve the above issue. But now I'm unable to run the Docker image with my config.yaml
file. I run the command docker run otelcontribcol --config path/to/my/config.yaml
and I get the following error:
WARNING: unable to read config file: open /path/to/my/config.yaml/config.json: not a directory
Error: cannot load configuration: error loading config file "/path/to/my/config.yaml": open /path/to/my/config.yaml: no such file or directory
For some reason, it adds config.json
to my path in the warning, then it tells me that there is no such file /path/to/my/config.yaml
when there is. Does anyone know how I can resolve this?
Hello Telemetors! 🔭
Why no room for opentelemetry-swift
? 😐
Has anybody experienced this for using opentelemetry-swift
on XCode 12?
open-telemetry/opentelemetry-swift#111
Thank you for any advice :bow:
opentelemetry-collector
repo and opentelemetry-collector-contrib
repo. I'm told that opentelemetry-collector-contrib
is a superset of opentelemetry-collector
but could someone explain how a collector running from opentelemetry-collector-contrib
can use exporters that are only in opentelemetry-collector
repo such as zipkinexporter
or jaegerexporter
?
Hi! I have deployed otel-collector on our cluster based on https://github.com/signalfx/splunk-otel-collector/blob/main/examples/kubernetes-yaml/splunk-otel-collector-gateway.yaml
I'm getting this "append failed" msg, bit confused why is it happening!!
otel-collector-8669588d78-qsj4l otel-collector {"level":"info","ts":1614648489.4920561,"caller":"scrape/scrape.go:930","msg":"","level":"warn","scrape_pool":"otel-collector","target":"http://localhost:8888/metrics","msg":"append failed","err":"HTTP 401 \"Unauthorized\""}
Resource
but it's not clear to me what to use for request-specific tags (e.g. something like enduser.id
). Baggage
seems like it might be appropriate, but how do I then automatically propagate the baggage tags to the active Span
?