Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Tigran Najaryan
    @tigrannajaryan
    @albertteoh sure, gitter and github will remain available for discussions.
    Milo Espitia
    @mcadac
    Hello Guys!
    Milo Espitia
    @mcadac
    I got a question. We migrate from Opentracing to Opentelemetry (Java) and deploy jaeger-agents into each host, but I don't know how to send the traces to the jaeger-agents using the protocol UDP/6831; do you know how we can do it? Or any recommendation to migrate?
    Or should we replace the jaeger-agents for open telemetry collectors?
    Bogdan Drutu
    @bogdandrutu
    I don't think in Java we support the UDP protocol we support proto/http or thrift/http I think
    2 replies
    Milo Espitia
    @mcadac
    so how can I send data to a jaeger-agent using opentelemetry?
    3 replies
    Jude DSouza
    @dsouzajude
    Hi all, just wanted to know if the OpenTelemetry collector's design allows one to run multiple replica instances of the collector, for example behind a load balancer?
    12 replies
    Endre Karlson
    @ekarlso
    So anyone looked at OTEL Collector vs https://github.com/timberio/vector/ ?
    8 replies
    Rashmi Modhwadia
    @rushminatorr
    Hello Team, Anyone from new-relic opentelemetry-collector-contrib space and can please help me? I am not sure if its an account error or not?
    I have a basic setup with logging exporter and new-relic exporter. Logging exporter logs my metrics on console but NR exporter fails with
    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"}
    3 replies
    Tigran Najaryan
    @tigrannajaryan
    I didn't see any objections so Collector SIG meeting will be at 9am PT starting from this week. Calendar updated.
    Weyert de Boer
    @weyert
    Are there any plans to support logging in the collector? If so, would it support something similar to the trace processors?
    2 replies
    Machhindra
    @MacNale
    Hello Team, Is there any guideline on how can I migrate from using vendor auto instrumentation to opentelemetry phase wise. I can not change all the applications in one go. There will be some applications with vendor specific tracing. New applications will start using opentelemetry tracing. I am not sure how this will come together.
    7 replies
    Pablo Baeyens
    @mx-psi
    Hi all, I have this PR open-telemetry/opentelemetry-collector-contrib#2275 which was assigned to review by @//nilebox which is no longer an approver. It already has a review from Datadog. Should a different reviewer be assigned to it?
    Naga
    @tannaga
    Hello All.. i am in the process of upgrading otel collector from v0.10.0 to v0.19.0.. One of thing i observed is that for otlp http , it expects trace and span id to be plain hex instead of base64 encoded..
    Is it true? Would like to know the reason behind this change if possible
    Weyert de Boer
    @weyert
    I am trying to get a better understanding of collector. If I am using GKE is the idea thats is a sidecar in every pod? And then have those instances send to a 'main' collector which collects it from those and this 'main' collector finally sends its data to prometheus and/or zipkin?
    Or do the service in the pod just send it straight to the 'main' collector? Is there any advise about this?
    best practices
    the goal is to send traces to stackdriver and send metrics to prometheus
    Advise would be appreciated
    Jordan Sinko
    @JordanSinko
    Anyone get the awsxray exporter to actually work? I just configured the exporter like so:
    exporters:
        awsxray:
            region: us-east-1
    I am able to export using the logging exporter and datadog exporter fine. Is there any prereqs that need to be up outside of the collector?
    5 replies
    Jordan Sinko
    @JordanSinko
    Also seeing nothing related to xray in the logs besides the exporter starting/started logs
    Eric Mustin
    @ericmustin
    for a basic docker-compose setup, if i want to collect container logs from stdout/stderr, is there an out of the box solution here? my gut says stanzareceiver but a little lost trying to work thru the stanza docs
    13 replies
    doesn't need to be production ready necessarily just trying to do some POC stuffs
    Maor Goldberg
    @maorgoldberg
    Hey all,
    Is the spanmetrics processor currently usable? Or is it still no functional
    2 replies
    Juraci Paixão Kröhling
    @jpkrohling
    is a maintainer available to review/merge this one? it's been in the queue for a really long time now: open-telemetry/opentelemetry-collector#2322
    3 replies
    Eric Mustin
    @ericmustin
    I think the fluentbit extension in the collector is a nice little extra, makes some logging stuff much easier since i don't have to rely on a specific exporter being available. however the docs say it's experimental and potentially removed at any times...any thoughts or updates on the future of this extension? would love to see it kept in the collector until logging at least reaches beta https://github.com/open-telemetry/opentelemetry-collector/tree/main/extension/fluentbitextension
    2 replies
    Jude DSouza
    @dsouzajude

    Hi, i would like to parameterize the OTEL collector config using environment variables and i came across this link on the official docs: https://opentelemetry.io/docs/collector/configuration/#configuration-environment-variables but is there a way to provide a default value to null?

    I'm trying to set the role_arn for the AWS X-Ray exporter:
    https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/master/exporter/awsxrayexporter#exporter-configuration

    Bogdan Drutu
    @bogdandrutu
    hm... not sure about null, maybe we can think of a solution to not set that entry if the env is missing, I think we need to think about how to support null
    Juraci Paixão Kröhling
    @jpkrohling
    how about simply setting the env var to the string "null"? I mean, nobody would create an option with "null'' being a valid string value, would they?
    I see that the otel-collector channel at Slack has been created -- are we moving this room here there?
    1 reply
    Jude DSouza
    @dsouzajude
    Sorry i wasn't aware of this channel. I'm a newbie to OpenTelemetry :) Thanks however for your response. I'll try moving the conversation there.
    Tigran Najaryan
    @tigrannajaryan
    @/all there is now a Slack channel for Collector: https://app.slack.com/client/T08PSQ7BQ/C01N6P7KR6W
    Unless there are objections I suggest to move to Slack.
    Jay Camp
    @jrcamp
    @tigrannajaryan that link doesn't seem to work. is it in CNCF slack workspace?
    1 reply
    looks like it. CNCF workspace is: http://slack.cncf.io/ and the channel is #otel-collector
    Pavol Loffay
    @pavolloffay
    Hi, a question about attributes processor. Is there a way to remove attributes which match a regex? e.g. remove all attributes that match http.request.header.* key?
    1 reply
    Bence Janos Toth
    @benonymus

    Hey,
    Does anyone have a good example of deploying otel_collector (trying to use the contrib image with elastic exporter) as a sidecar to an elixir project using:
    https://hex.pm/packages/opentelemetry in the project.
    At the moment the deployment succeeds but nothing is coming through the pipeline.
    I added an receiver for opencensus as well that we are migrating from, but nothing comes there either.
    This indicates that the link between the 2 parts is missing.
    Any ideas or examples?

    Thanks

    Tigran Najaryan
    @tigrannajaryan
    Reminder: this discussion room has moved to CNCF Slack: https://cloud-native.slack.com/archives/C01N6P7KR6W
    Please don't use Gitter anymore.
    ChrisSmith
    @ChrisSmith
    If you're not already in the CNCF slack workspace that link won't work. You can join here https://slack.cncf.io/
    rupinder10
    @rupinder10
    I have configured the opentelemetry collector windows service. I tried adding the datadog exporter but when I do that I get an error 1064 while starting the service. Where does it log its details about what the problem is ?
    5 replies
    Filipe Oliveira
    @oliveirafilipe
    Hi folks. I'm really noob in the grpc world. I set up a open telemetry collector listening grpc.
    Does anyone have a grpcurlgrpcurl example on how can I use the protos for open telemetry and see if my collector is up and running correctly?
    1 reply
    Juraci Paixão Kröhling
    @jpkrohling
    Tigran Najaryan
    @tigrannajaryan
    Reminder: this discussion room has moved to CNCF Slack: https://cloud-native.slack.com/archives/C01N6P7KR6W
    Please don't use Gitter anymore. If you're not already in the CNCF slack workspace join here https://slack.cncf.io/
    Andrea Tosato
    @andreatosato
    I'm study otel, I have created this repo but it not work properly. I have no trace but zpages counter is not 0 in collector.
    I have traced with zipkin and jeager, i have used exporter directly in .net app.
    Tigran Najaryan
    @tigrannajaryan
    This discussion room has moved to CNCF Slack: https://cloud-native.slack.com/archives/C01N6P7KR6W
    Please don't use Gitter anymore. If you're not already in the CNCF slack workspace join here https://slack.cncf.io/
    Stephen Hong
    @stephenhong
    Hello team, I'm trying to forward metrics from one otel collector to another otel collector. These collectors are running on two different ec2 instances. I configured otlp receiver on one collector and otlp and otlp http exporter on the other. However, I get context deadline exceeded error from the collector that's trying to export metrics. Any suggestions on how to resolve this? Also, is there a better receiver/exporter pair for this particular use case? Thank you.
    Juraci Paixão Kröhling
    @jpkrohling

    Reminder - we have moved to #opentelemetry-collector channel on Slack http://slack.cncf.io/