Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Endre Karlson
    @ekarlso
    @markcartertm_twitter You got any clue ?
    Endre Karlson
    @ekarlso
    I'm about to give up :) Spent the last 2 days on this stuff without getting anywhere sadly :)
    Endre Karlson
    @ekarlso
    so after lots of adventure in Go + Delve land I've managed to dig up the cause open-telemetry/opentelemetry-collector-contrib#1367 it seems that there's basically no "Collector" present in the list which is iterates to get the metrics to serve
    Endre Karlson
    @ekarlso
    @jpkrohling do you know how from the contrib code I can say I wanna use a local version of the core repo ?
    1 reply
    I tried with a "replace go.opentelemetry.io/exporter/prometheusexporter => ../opentelemetry-collector/exporter/prometheusexporter" but that didnt fair too well
    Juraci Paixão Kröhling
    @jpkrohling
    that's indeed how it would work
    what happened when you did that ?
    oh, wait, no -- you should replace the entire otelcol core repo, not just the exporter
    in the otelcol contrib repo, each component is a go module, but the whole core repo is a single go module
    so: replace go.opentelemetry.io/collector => ../opentelemetry-collector/
    Endre Karlson
    @ekarlso
    Yeah I tried that but got some build errors @jpkrohling
    Juraci Paixão Kröhling
    @jpkrohling
    make sure you are at the latest version of both -- there was a change yesterday in the collector repo that broke the contrib components
    Endre Karlson
    @ekarlso
    ah
    @jpkrohling could we add some kind of metricsd or debuggability to see what targets are scraped by prometheus?
    Ritick Gautam
    @riticksingh
    Can anyone know how to check if collector is receiving span ?
    Juraci Paixão Kröhling
    @jpkrohling
    @riticksingh if you add the logging exporter to your pipeline, it will print out how many spans were in the batch
    2 replies
    that's the easiest way
    Endre Karlson
    @ekarlso
    Is there any typical reason for having the prometheus receiver having to be a daemonset with env vars ?
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Screen Shot 2020-10-29 at 8.00.06 AM.png
    Does anybody know how to resolve this? I need to use common.StringKeyValue .
    could not import go.opentelemetry.io/collector/internal/data/opentelemetry-proto-gen/common/v1 (invalid use of internal package go.opentelemetry.io/collector/internal/data/opentelemetry-proto-gen/common/v1)
    2 replies
    Aman Brar
    @amanbrar1999
    @bogdandrutu Anuraag has approved this PR after you requested his review, is it good to merge now? open-telemetry/opentelemetry-collector#2000
    Eric Mustin
    @ericmustin
    just curious what the release schedule is like? bi-weekly? i recally vaguely a doc floating around but i cant seem to find it
    5 replies
    Endre Karlson
    @ekarlso

    HEy peeps! Are any of you running the prometheus receiver and getting

    Discovery receiver's channel was full so will retry the next cycle?

    Endre Karlson
    @ekarlso
    @alolita @JasonXZLiu do you have any updates here? open-telemetry/opentelemetry-collector#1909
    8 replies
    Gavin Zhang (Kunyuan Zhang)
    @gavindoudou
    Does anyone have any suggestion on this? open-telemetry/opentelemetry-collector-contrib#1426
    It says: bind: An attempt was made to access a socket in a way forbidden by its access permissions
    We did not change the code for that part for 2 months and it just got that error now
    harini0597
    @harini0597
    Hi. I have a question. What does unit='1' imply while creating metrics?
    2 replies
    Jason Liu
    @JasonXZLiu
    @bogdandrutu We were wondering if it would be possible to merge open-telemetry/opentelemetry-proto#227. I don't believe we're going to be making anymore changes to the PR and it seems like everyone's approved it. It's currently blocking some other PRs that we have. Thank you!
    Juraci Paixão Kröhling
    @jpkrohling
    @tigrannajaryan did something change regarding the SIG meeting docs ? when I try to open it, it tells me that I need to request access
    I believe it was public before
    I'm leaving for the day, but I wanted to add an item to the agenda: "Request review -- open-telemetry/opentelemetry-collector-contrib#1412"
    Kevin Brockhoff
    @kbrockhoff
    I am seeing the same message
    Tigran Najaryan
    @tigrannajaryan
    The meeting doc permissions should be fine now, not sure why it was changed.
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Hi @bogdandrutu will highly appreciate your guidance regarding the next step on this PR [Resource_Attributes_To_Labels]. open-telemetry/opentelemetry-collector#2060
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    I think we removed the IsNil() func from pdata.Resource? What is the replacement of it?
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    PR on opentelemetry-collector repo is failing because of contrib-repo test. I cannot think it's happening because of my changes. any clue?
    @bogdandrutu will appreciate a final look on this PR. open-telemetry/opentelemetry-collector#2060
    Aaron Tye
    @atye
    Hello. I'm trying to configure the OpenTelemetry Collector (v0.4.0) with TLS with the configuration below but I see the error below in the logs. From what I see in the Change Log, 0.4.0 should support TLS. What am I doing wrong?
    receivers:
      otlp:
        protocols:
          grpc:
            tls_settings:
              key_file: /root/test-keys/test-key
              cert_file: /root/test-keys/test-key.pub
    Error: cannot load configuration: error reading settings for receiver type "otlp": 1 error(s) decoding:
    
    * '' has invalid keys: protocols
    Iris Grace Endozo
    @irisgve
    Hi @bogdandrutu wondering if we can get some guidance on this issue: open-telemetry/opentelemetry-collector-contrib#1305 we could get started on the new PR for the proposed changed if all is good.
    Juraci Paixão Kröhling
    @jpkrohling
    @atye that's an old version of the collector -- I just tested your configuration on 1.14.0 and it does work
    Juraci Paixão Kröhling
    @jpkrohling
    0.14.0, not 1.14.0 -)
    ChrisSmith
    @ChrisSmith
    @jpkrohling is it possible to add a custom auth processor? I see you were woking on OIDC support but I was wondering about being able to add custom logic in our build of the collector
    Juraci Paixão Kröhling
    @jpkrohling
    @ChrisSmith processor? or did you mean, to extend the current configauth ?
    I've been thinking about this since I first designed the current authenticator, and it does have a pluggable architecture but I don't think it would work with downstream distributions
    I'm yet to try it out though
    if you want to give it a try and need a quick overview of how it works, let me know
    Juraci Paixão Kröhling
    @jpkrohling
    in any case, please do open an issue and cc me, so that we can discuss what can be done to allow downstream authenticators, if it's not supported out of the box (I think some interfaces might be private)
    ChrisSmith
    @ChrisSmith

    I opened an issue here open-telemetry/opentelemetry-collector#2101

    Looking over the code I didn't see where I could register new auth modules

    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Hi @bogdandrutu and @tigrannajaryan would you please have a look to see if we can get this merged. We are migrating to OTLP (pdata.Metrics) from OpenCensus type. It was reviewed and approved.
    open-telemetry/opentelemetry-collector-contrib#1536
    1 reply
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan

    open question for Go experts related to go.mod(maybe a pretty basic one). Any lead is appreciated. Thanks.
    I pushed an update to opentelemetry-collector core repo. Now, from the opentelemetry-collector-contrib repo, I need to use a module (exporterhelper module) from that specific commit hash. I tried the following ways- but couldn't make it work. What's the right way to do it.

    Approach-1:

    require (
        // go.opentelemetry.io/collector v0.14.1-0.20201106183657-c6b8f28c60b5
        github.com/open-telemetry/opentelemetry-collector 5f60c7232abd6e1d3af94f8860c006f062d1c1f0
    )

    Approach-2:

    require (
        go.opentelemetry.io/collector v0.14.1-0.20201106183657-c6b8f28c60b5
    )
    replace go.opentelemetry.io/collector/exporter/exporterhelper v0.14.1-0.20201106183657-c6b8f28c60b5 => github.com/open-telemetry/opentelemetry-collector/exporter/exporterhelper 5f60c7232abd6e1d3af94f8860c006f062d1c1f0
    3 replies