Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Maor Goldberg
    @maorgoldberg
    Hey all, any information regarding the spanmetrics processor and when it will be released?
    David Ashpole
    @dashpole
    Hey all, there are a few of us in the Collector sig meeting right now, but the later time slot we have been using every other week has been very lightly attended the past month or two. I asked on the call, and there weren't any folks who preferred the later time slot. If you prefer the later time, please let us know here. Otherwise, if there are no objections, i'd like to propose moving it to an earlier time.
    Iris Grace Endozo
    @irisgve
    Hi, @tigrannajaryan wondering if there is any news on this: open-telemetry/opentelemetry-collector#669 or if it's something we can contribute to. We're planning on implementing a custom rate limit processor and would love for the receivers to throttle the clients with appropriate status + retry code.
    5 replies
    Ferenc Hubicsak
    @fhubi
    Hi, when will the Loki exporter be available? I got this error message: "cannot load configuration: unknown exporters type loki". I used the otel/opentelemetry-collector-contrib-dev:latest docker image. Or is there any other exporter that I can use for logs?
    6 replies
    Juraci Paixão Kröhling
    @jpkrohling
    @bogdandrutu @tigrannajaryan I'll move the code for the builder next week, from its current location to the new repostory -- I'll probably do a force-push after copying the current files from the new repository (codeowners only, I believe). This way, the history and tags are kept with the same references. In fact, the ideal would really be to "move" the repository, so that the releases would get moved as well, but might be too late for that.
    3 replies
    image.png
    yaldong
    @yaldong
    Hi ALL, I still got errors when I "make otelcol" after "make install-tools" $ make install-tools
    cd ./internal/tools && go install github.com/client9/misspell/cmd/misspell
    cd ./internal/tools && go install github.com/golangci/golangci-lint/cmd/golangci-lint
    cd ./internal/tools && go install github.com/google/addlicense
    cd ./internal/tools && go install github.com/jstemmer/go-junit-report
    cd ./internal/tools && go install github.com/mjibson/esc
    cd ./internal/tools && go install github.com/ory/go-acc
    cd ./internal/tools && go install github.com/pavius/impi/cmd/impi
    cd ./internal/tools && go install github.com/tcnksm/ghr
    cd ./internal/tools && go install golang.org/x/tools/cmd/goimports
    cd ./internal/tools && go install honnef.co/go/tools/cmd/staticcheck
    cd cmd/mdatagen && go install ./
    $ make otelcol
    go generate ./...
    receiver/hostmetricsreceiver/codegen.go:17: running "mdatagen": exec: "mdatagen": executable file not found in $PATH
    service/internal/gen.go:17: running "esc": exec: "esc": executable file not found in $PATH
    Makefile:147: recipe for target 'otelcol' failed
    make: * [otelcol] Error 1
    Anyone know how to fix it?
    1 reply
    Juraci Paixão Kröhling
    @jpkrohling
    can I get a review from an approver for this one? open-telemetry/opentelemetry-collector-builder#3
    Tigran Najaryan
    @tigrannajaryan
    @/all the last few times we had very low participation for the Collector SIG meeting that is scheduled for 4pm Pacific Time. We would like to change the meeting time to 9am Pacific Time every week. If anyone has a strong desire to participate the 4pm meeting please object, otherwise we will move it to 9am.
    Albert
    @albertteoh

    Thanks for the heads up @tigrannajaryan . If it's okay with maintainers to discuss proposals over gitter or github Issues and provide feedback, then I'm okay with this and understand the motivation behind the change; hopefully it will be easy to get the attention of maintainers and community at large :).

    I'm perhaps one of a small handful of folks based in the APAC region that benefit from the 4pm meeting slot; and grateful that the 4pm timeslot was available at the time to gather feedback for a proposal. Many thanks for trying to accommodate APAC!

    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?
    3 replies
    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.