Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    Aman Brar
    @amanbrar1999
    @bogdandrutu can you please follow up on the discussion on this PR? open-telemetry/opentelemetry-collector-contrib#1497
    Endre Karlson
    @ekarlso

    @jpkrohling Have you seen this before with OTEL Colelctor Operator?

    {"level":"error","ts":1605103614.469881,"logger":"controllers.OpenTelemetryCollector","msg":"failed to reconcile daemon sets","error":"failed to reconcile the expected daemon sets: failed to apply changes: DaemonSet.apps \"main-collector\" is invalid: spec.selector: Invalid value: v1.LabelSelector{MatchLabels:map[string]string{\"app.kubernetes.io/component\":\"opentelemetry-collector\", \"app.kubernetes.io/instance\":\"opentelemetry-system.main\", \"app.kubernetes.io/managed-by\":\"opentelemetry-operator\", \"app.kubernetes.io/name\":\"main-collector\", \"app.kubernetes.io/part-of\":\"opentelemetry\", \"fluxcd.io/sync-gc-mark\":\"sha256.S_o66xL9t1DMr3tS8jPOC8WO8DnOZ3mX1Rm3ZtvJS9M\"}, MatchExpressions:[]v1.LabelSelectorRequirement(nil)}: field is immutable","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/go/pkg/mod/github.com/go-logr/zapr@v0.2.0/zapr.go:132\ngithub.com/open-telemetry/opentelemetry-operator/controllers.(*OpenTelemetryCollectorReconciler).RunTasks\n\t/workspace/controllers/opentelemetrycollector_controller.go:145\ngithub.com/open-telemetry/opentelemetry-operator/controllers.(*OpenTelemetryCollectorReconciler).Reconcile\n\t/workspace/controllers/opentelemetrycollector_controller.go:134\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:244\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:218\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\t/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:197\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\t/go/pkg/mod/k8s.io/apimachinery@v0.19.3/pkg/util/wait/wait.go:90"}

    seems to happen after a while
    Juraci Paixão Kröhling
    @jpkrohling
    no, I haven't -- what's this "fluxcd.io" label ?
    in any case, the operator is probably doing the wrong thing , could you open an issue ?
    Endre Karlson
    @ekarlso
    Sure
    @jpkrohling I wonder if it's the Operator taking labels from the CR instance directly which causes a mutation ?
    Juraci Paixão Kröhling
    @jpkrohling
    how does your CR look like? the operator shouldn't take the labels from the CR itself, but it should take labels from inside the spec
    Endre Karlson
    @ekarlso
    It seems that it is this that's happening
    apiVersion: opentelemetry.io/v1alpha1
    kind: OpenTelemetryCollector
    metadata:
      annotations:
        fluxcd.io/sync-checksum: 40380fdc15e6654f514b948ee93ffef45226959a
      creationTimestamp: "2020-11-10T11:46:15Z"
      generation: 6
      labels:
        app.kubernetes.io/managed-by: opentelemetry-operator
        fluxcd.io/sync-gc-mark: sha256.S_o66xL9t1DMr3tS8jPOC8WO8DnOZ3mX1Rm3ZtvJS9M
      name: main
      namespace: opentelemetry-system
      resourceVersion: "87672233"
      selfLink: /apis/opentelemetry.io/v1alpha1/namespaces/opentelemetry-system/opentelemetrycollectors/main
      uid: 953f0d0c-ce61-43ed-a863-7f4ca13b6780
    The DaemonSet doesnt have any flux label on it so is there some update logic going wrong?
    Juraci Paixão Kröhling
    @jpkrohling
    what's fluxcd ? is it possible that it is adding this label automatically, even though the operator isn't setting it ?
    this would explain the message: the operator reconciles a set of labels without this "fluxcd" label, so, when it tries to update to the desired state, it fails
    Endre Karlson
    @ekarlso
    @jpkrohling Weave's gitops oprator
    Andrew Hsu
    @andrewhsu

    i forgot this channel was associated with the https://github.com/open-telemetry/opentelemetry-collector repo, so i’ve neglected to post relevant info here related to collector. instead, i’ve been posting my collector comments to the https://gitter.im/open-telemetry/opentelemetry-specification gitter channel instead over the past few days. (just issue triage logistics comments)

    any chance this channel can be renamed to open-telemetry/opentelemetry-collector?

    3 replies
    Derrick Burns
    @derrickburns

    I am trying to configure the opentelemetry-collector to support prometheus. I am getting this from my client :

    2020/11/12 00:16:26 rpc error: code = Unimplemented desc = unknown service opentelemetry.proto.collector.metrics.v1.MetricsService

    Here is my configuration:

    apiVersion: v1
    data:
      otel-collector-config: |-
        "exporters":
          "jaeger":
            "endpoint": "jaeger-collector.observability:14250"
            "insecure": true
          "prometheus":
            "endpoint": ":8889"
            "namespace": "monitoring"
        "extensions":
          "health_check": {}
          "zpages": {}
        "processors":
          "batch": null
          "memory_limiter":
            "ballast_size_mib": 683
            "check_interval": "5s"
            "limit_mib": 1500
            "spike_limit_mib": 512
          "queued_retry": null
        "receivers":
          "jaeger":
            "protocols":
              "grpc": null
              "thrift_http": null
          "opencensus": null
          "otlp":
            "protocols":
              "grpc": null
              "http": null
        "service":
          "extensions":
          - "health_check"
          - "zpages"
          "pipelines":
            "metrics":
              "exporters":
              - "prometheus"
              "receivers":
              - "opencensus"
            "traces":
              "exporters":
              - "jaeger"
              "processors":
              - "memory_limiter"
              - "batch"
              - "queued_retry"
              "receivers":
              - "otlp"
              - "jaeger"
              - "opencensus"
    kind: ConfigMap
    metadata:
      labels:
        app: otel-collector-conf
      name: otel-collector-conf
      namespace: observability
    3 replies
    Ideas?
    Eric Mustin
    @ericmustin
    Hello friends, is there any processor that allows users to add attributes to a span based on span events? If i understand things correctly, Some vendor exporters drop span events, so i was hoping to able to append details of span events as span attributes within a processor
    2 replies
    sanjaygopinath89
    @sanjaygopinath89
    Hi Team , trying to understand the routing processor . https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/master/processor/routingprocessor. the name that we need to give in from_attribute , is that span attribute name ..?
    Ritick Gautam
    @riticksingh

    hi all I am trying converting proto files to php for OTLP/grpc exporter by

    protoc --proto_path=opentelemetry-proto/ --php_out=proto $(find opentelemetry-proto/opentelemetry -iname "*.proto")

    Is it also require to have --grpc_out= ?

    Endre Karlson
    @ekarlso
    Can I do trace filtering based on path or something in OTEL ?
    3 replies
    Andrey Afoninsky
    @afoninsky
    hello all
    I'm trying to deliver traces into two systems (jaeger / grafana tempo) in order to play with them in parallel, so I use opentelemetry-collector as a receiver
    when I send traces directly to collector - I see them in logs but downstream services don't have them (if I send directly to jaeger everything is ok)
    could you point the way how can I debug it and see where I failed? config and commands I use: https://gist.github.com/afoninsky/7496c4bb89cc461aa33ffeb64318a634
    thank you
    7 replies
    Divya Sharma
    @Div95

    Hi all, I am trying to export traces to Splunk using Splunk HEC exporter and Zipkin receiver for OpenTelemetry Collector.
    Problem: I am not able to see the traces in Splunk. However, logging exporter does show the logs for the traces.
    Could you please help me out with this? Thank you.

    Following is the content of otel-collector-config.yaml file:

    3 replies
    Screen Shot 2020-11-17 at 9.53.18 AM.png
    harini0597
    @harini0597
    Hi everyone. Can I please know the format of OpenTelemetry collector URI? Where can I look for this?
    2 replies
    Tigran Najaryan
    @tigrannajaryan
    I am thinking of cancelling the Collector SIG meeting tomorrow because of Kubecon.
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Hi everyone, I cannot build the opentelemetry-collector-contrib. Something wrong with DataDog dependency. Is it a known issue? I just pulled the latest code.
    make otelcontribcol
    GO111MODULE=on CGO_ENABLED=0 go build -o ./bin/otelcontribcol_darwin_amd64 \
            -ldflags "-X github.com/open-telemetry/opentelemetry-collector-contrib/internal/version.GitHash=c01d3b00  -X go.opentelemetry.io/collector/internal/version.BuildType=release" ./cmd/otelcontribcol
    go: finding module for package github.com/DataDog/datadog-agent/pkg/collector/corechecks/cluster
    go: found github.com/DataDog/datadog-agent/pkg/collector/corechecks/cluster in github.com/DataDog/datadog-agent v0.0.0-20201117210934-a3cba9a8cfd2
    go: github.com/DataDog/datadog-agent@v0.0.0-20201117210934-a3cba9a8cfd2 requires
        github.com/benesch/cgosymbolizer@v0.0.0: reading github.com/benesch/cgosymbolizer/go.mod at revision v0.0.0: unknown revision v0.0.0
    make: *** [otelcontribcol] Error 1
    2 replies
    Tigran Najaryan
    @tigrannajaryan
    @here a lot of people are unable to attend today. Unless I see objections I will cancel Collector SIG meeting today.
    10 replies
    @/all ^^^
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Hi @bogdandrutu @tigrannajaryan can we get this merged please. A small bug fix & readme update. Code was reviewed and approved.
    open-telemetry/opentelemetry-collector-contrib#1626
    Tigran Najaryan
    @tigrannajaryan
    /all SIG meeting is cancelled today due to Kubecon.
    Endre Karlson
    @ekarlso
    What is the meaning typically of this? Adjust - skipping unexpected point
    Endre Karlson
    @ekarlso
    Has there been issues with the OTEL collector dropping metrics?
    14 replies