Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Pablo Baeyens
    @mx-psi
    Hi, we would like to get this PR merged before 0.18.0 is released, it is a small change on a previous PR by me open-telemetry/opentelemetry-collector-contrib#1962 It has been already reviewed by someone from Datadog. Could it be merged?
    Kartik Verma
    @vkartik97

    Hi,
    I are using otel collector and with open census and we are getting this error

    exporterhelper/queued_retry.go:239        Exporting failed. The error is not retryable. Dropping data.        {"component_kind": "exporter", "component_type": "prometheusremotewrite", "component_name": "prometheusremotewrite", "error": "Permanent error: [Permanent error: nil data point. opencensus.io/http/client/roundtrip_latency is dropped; Permanent error: nil data point. opencensus.io/http/client/received_bytes is dropped; Permanent error: nil data point. grpc.io/server/sent_messages_per_rpc is dropped; Permanent error: nil data point. grpc.io/server/received_bytes_per_rpc is dropped; Permanent error: nil data point. grpc.io/server/sent_bytes_per_rpc is dropped; Permanent error: nil data point. opencensus.io/http/client/sent_bytes is dropped; Permanent error: nil data point. grpc.io/server/received_messages_per_rpc is dropped; Permanent error: nil data point. grpc.io/server/server_latency is dropped; Permanent error: nil data point. grpc.io/server/completed_rpcs is dropped]", "dropped_items": 9}

    screenshot
    image.png

    the config is :

    extensions:
      health_check:
      pprof:
        endpoint: 0.0.0.0:1777
    
    receivers:
        opencensus:
            endpoint: "0.0.0.0:55678"
    
    processors:
        batch:
        memory_limiter:
          ballast_size_mib: 683
          limit_mib: 1500
          spike_limit_mib: 512
          check_interval: 5s
        queued_retry:
    
    exporters:
      logging:
        logLevel: debug
      jaeger:
        endpoint: <jaeger_collector_url>
        insecure: true
      prometheusremotewrite:
        endpoint: <prom_remote_url>
    
    service:
      pipelines:
        traces:
          receivers: [opencensus]
          processors: [memory_limiter, batch, queued_retry]
          exporters: [jaeger]
        metrics:
          receivers: [opencensus]
          processors: [memory_limiter, batch, queued_retry]
          exporters: [prometheusremotewrite]
      extensions: [health_check, pprof]

    Please help

    Eric Mustin
    @ericmustin
    repost from ruby gitter, do we communicate any info about "lang" to the collector? is there any info available to an exporter on a span's lang?
    1 reply
    Pavan Krishna
    @pavankrish123

    Hello Friends, I have submitted a PR open-telemetry/opentelemetry-collector-contrib#1887 to collector contrib couple of weeks back - it is currently approved state - any estimate on when it can be expected in master. A kind request to include this change in the upcoming release - Please and Thank you

    Hello Folks, Happy Monday - any updates on this review request? Please and Thank you.

    Sandeep Raveesh
    @crsandeep
    Hello All. While using prometheus receiver I noticed that the labels and metrics auto generated by prometheus are dropped by prometheus receiver. Example - metric "up and scrape_duration_seconds" and labels "job and instance". Is this intentional or may be a bug?
    Juraci Paixão Kröhling
    @jpkrohling
    @owais did anything happen to the release notes for 0.18.0 ?
    2 replies
    Maor Goldberg
    @maorgoldberg
    Hey all, what would you say are essential processors in the collector config. Currently I am using batch, memory limiter, probabilistic sampler and queued retry do you see the need to add more?
    2 replies
    Tigran Najaryan
    @tigrannajaryan
    @/all if you are interested in logs please check out the proposal to contribute Stanza to OpenTelemetry with the goal of using it as the log collection library for OpenTelemetry Collector: open-telemetry/community#605
    1 reply
    Eric Mustin
    @ericmustin
    what's like, the canonical opentelemetry-collector-contrib demo app these days? Or, what's the right dockerr image to point to? the example in example/tracing feels a bit stale
    2 replies
    Julian Fell
    @jtfell

    Hi all. I'm trying to export metrics from a NodeJs app to the open-telemetry-exporter and am getting a 501 - Not Implemented error. Is this the current status for this integration or am I using an outdated version of something? Thanks!

    Versions:

    • Latest docker image of otel/opentelemetry-collector (Published 2 days ago - 3c1ed120c45b)
    • "@opentelemetry/exporter-collector": "0.14.0"

    collector config:

    receivers:
      otlp:
        protocols:
          grpc:
          http:
            cors_allowed_origins:
            - http://*
            - https://*
    
    exporters:
      zipkin:
        endpoint: "http://zipkin:9411/api/v2/spans"
    
    processors:
      batch:
      queued_retry:
    
    service:
      pipelines:
        traces:
          receivers: [otlp]
          exporters: [zipkin]
          processors: [batch, queued_retry]
    Traces are working with my current setup btw!
    Joshua MacDonald
    @jmacd

    The @opentelemetry Metrics Workshop happens tomorrow at 9:30 PST at https://zoom.us/j/8203130519

    9:30 - 9:45am PST: Opening remarks, organization of the day, how we got here, and the many streams of work. We have an API, language SDKs, a Protocol, a Collector, Receivers, Exporters, Semantic Conventions, and a connection to Tracing [organizer: OTel Committee]

    9:45-10:15am PST: Community building: @opentelemetry has first-class @OpenMetricsIO support, and @PrometheusIO users are first-class users. These projects are meant to get along, and committed to it. [organizer: Alolita Sharma]

    10:15 - 11:00am PST: @opentelemetry Collector deployment models (e.g., Daemonset vs. Statefulset), Agents, Sidecars, and first-class support for Prometheus Remote-Write [organizer: Jaana Dogan]

    11:30 - 12:15pm The Metrics API and Data Model, how we integrated the @opencensusio feature set (Tracing and Metrics, combined!) with the @OpenMetricsIO and StatsD data models. Presenting the six @opentelemetry metric instruments [organizer: Bogdan Drutu]

    12:15 - 13:00pm Histograms! How we’ll support high-resolution and variable-boundary histograms and the connection to sampling metric events [organizers: Josh MacDonald, Michael Gerstenhaber]

    13:30 - 15:00pm Questions and answers

    1 reply
    Peter Cabus
    @PCDiver
    What is the best way to install the Otel Collector on Windows as a service? I can't use the MSI package because I have to run two instances of the collector on the same machine (for testing). One as an Agent and one as a collector service. Thanks.
    2 replies
    Albert
    @albertteoh
    Hi all, I would appreciate if this PR could be reviewed: open-telemetry/opentelemetry-collector-contrib#2012. It implements the spanmetrics processor logic.
    Eric Mustin
    @ericmustin
    on lang sdk's should OTEL_EXPORTER_OTLP_ENDPOINT point to host:port or host:port/v1/traces ...if i don't include path should it append v1/traces by default?
    3 replies
    Bogdan Drutu
    @bogdandrutu
    For all vendors who have exporters in the contrib repo (or any other repository), the queue_retry processor was deprecated long time ago. This PR https://github.com/open-telemetry/opentelemetry-collector/pull/2380/ will remove it, so if you do not have the new queue retry enabled for your exporter see an example here on how simple is to add it open-telemetry/opentelemetry-collector#2307
    2 replies
    Rashmi Modhwadia
    @rushminatorr
    I am using the collector, i have zpages setup with defaults, i dont know how to access it? /zpages gives a 404, i know its running but do not know the endpoint. anyone has any tips please?
    6 replies
    Rashmi Modhwadia
    @rushminatorr

    I am using collector and have traces and metrics generated and can see them on console(i used the log exporter), I cant see metrics to prometheus. I have a basic prometheus docker conatiner, scraping from 9090 port. I have a prometheus exporter setup pointing to 9090 port. Unable to see metrics and not sure if the setup is complete or a way to debug.
    Would someone be able to point me to right direction or have any suggestion for me please?

    otel collector config

      prometheus:
        endpoint: "localhost:19090"
        namespace: "default"
        const_labels:
          env: rush
        send_timestamps: true

    Docker-compose:

     prometheus:
        image: prom/prometheus:latest
        container_name: prometheus
        ports:
          - "19090:9090"
        volumes:
        - ./prometheus/prometheus.yaml:/etc/prometheus/prometheus.yaml

    prometheus_config.yml

    global:
      scrape_interval: 10s
    
    scrape_configs:
      - job_name: 'prometheus'
        scrape_interval: 5s
        static_configs:
          - targets: ['localhost:9090']
    McSick
    @McSick
    Anyone have example config for the k8sproccessor in collector-contrib? Documentation is lacking https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sprocessor
    4 replies
    Eric Mustin
    @ericmustin
    dupe from community channel, :wave: is the contrib flavor of the otel-collector packaged in the aws cloudwatch agent now for ec2?
    KingJ
    @KingJ
    Is there a way to measure the queue length of the Exporter Helper? The deprecated queued_retry processor exposed metrics such as otelcol_processor_queued_retry_queue_length as is still documented on the monitoring documentation, but I couldn't find an equivalent metric for the Exporter Helper at a glance.
    Pavol Loffay
    @pavolloffay
    Hi, is there a way to get access to request headers in a processor? I would like to read the tenantID in my custom processor.
    22 replies
    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?