Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    Primarely when using the PRometheus receiver
    Endre Karlson
    @ekarlso
    @jpkrohling @flands How much memory is typically needed for a "small" deployment? I've only setup the OTEL collectors as a DaemonSet and limited the Targets to target only what runs on the Node it is running on basically in my Kubernetes SD config which is / should be very few pods
    4 replies
    Endre Karlson
    @ekarlso
    image.png
    Steve ^
    Endre Karlson
    @ekarlso
    And CPU usage atm is basically idle ref ^
    Iris Grace Endozo
    @irisgve
    Hi there! Question about doing validations: I'm thinking of doing payload validations within the metrics/spans in a processor and if a metric/span does not have specific attributes, I want to reject them and propagate that error to the client with a 400. Currently, I think if the data has gone thru the receiver and the first processor rejects them, the client will only receive a 500. Are there any thoughts on supporting something like synchronous validations as a processor or is it not part of the intended design within the collector?
    6 replies
    ZhengHe
    @ZhengHe-MD
    Hi Team,
    I’d like to sample spans by internal span status, e.g. the status code, any suggestion? The original need is to sample all spans with error tag set to true.
    2 replies
    Eric Mustin
    @ericmustin
    can someone confirm my mental model here... the semantically correct way to check if a span is an 'Error' , once it's been converted to pdata, is via Span.Status()...is that correct?
    2 replies
    lashukla
    @lashukla
    Hi All, can we have otel-collector running on MacOS as a native process ?
    5 replies
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    @bogdandrutu @tigrannajaryan can any of you please help me to get this reviewed and merged today. Its a one line bug fix which replaces {{ }} with { }. Will highly appreciate. Thanks.
    open-telemetry/opentelemetry-collector-contrib#1661
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Anybody who has the power- please help me out. Can any of you please help me to get this reviewed and merged today. Its a one line bug fix which replaces {{ }} with { }. Will highly appreciate. Thanks. @bogdandrutu @tigrannajaryan @andrewhsu
    open-telemetry/opentelemetry-collector-contrib#1661
    2 replies
    Endre Karlson
    @ekarlso
    To the person that fixed the open-telemetry/opentelemetry-collector#2121 this fixed my issue with vanished metrics and dirty workaround to continously restart OTEL Collectors! thnx @kohrapha
    2 replies
    Juraci Paixão Kröhling
    @jpkrohling
    @ZhengHe-MD would you like to get on a live call, to try to sort out the easy CLA issue ?
    5 replies
    Eric Mustin
    @ericmustin
    Could I get a quick overview of the changes that were made here? https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/1489/files I think due to some timing issues the vendor exporter i'm maintaining got missed in this PR, and starting to see some bug reports now (open-telemetry/opentelemetry-collector-contrib#1684). Is the idea that, for vendor exporters, instead of attempting to match statusCode against a range (400/500 errors), you just see if status.Code() == pdata.StatusCodeError? I'd be happy to update the datadog exporter to match whatever the current spec is
    1 reply
    Pablo Baeyens
    @mx-psi
    Hi all, the hostmetrics receiver from the OpenTelemetry Collector reports metrics namespaced under system.swap. (see here) that are similar in meaning but different in naming to the system.paging. metrics that feature in the spec (see here). Is this expected? If not, what should be changed (spec/implementation)? Should I open an issue for this?
    1 reply
    Naga
    @tannaga
    Hi All, In custom processors/receivers/exporters is there a provision to send custom app metrics via the stats or obsrreport package or any other means?
    For ex> in my custom processor, there is a cache of metadata which gets refreshed periodically.. if there is any problem reloading the cache I would like to emit a metric, so that i can set up the necessary monitoring..
    Anmol Dubey
    @anmoldubey-collibra
    Hello All, I am getting following error while trying to make otel collector
    make otelcol;
    go generate ./...
    receiver/hostmetricsreceiver/codegen.go:17: running "mdatagen": exec: "mdatagen": executable file not found in $PATH
    service/internal/gen.go:18: running "addlicense": exec: "addlicense": executable file not found in $PATH
    make: * [otelcol] Error 1
    I tried sunning ''go get -u github.com/mjibson/esc'' making sure $GOPATH and PATH are set
    I installed go via homebrew
    This is how my zshrc looks like - cat ~/.zshrc
    export GOPATH=/usr/local/Cellar/go/1.15.5
    export PATH=$PATH:$(go env GOPATH)/bin
    Juraci Paixão Kröhling
    @jpkrohling
    @anmldubey try make install-tools first
    1 reply
    Eric Mustin
    @ericmustin
    I opened an issue in opentelemetry-collector core that is a continuation of a discussion i was having in contrib, it involves a number of vendors, clients, and formats, and input from maintainers is appreciated open-telemetry/opentelemetry-collector#2214 . I will try to attend mtg today to sync on this as well. cheers
    Mats Taraldsvik
    @meastp
    does the opentelemetry-collector-contrib Azure Monitor exporter also export logs (opentelemetry-dotnet exports logs as well as traces)?
    Andrew Hsu
    @andrewhsu

    cross-posting from opentelemetry-specification

    Friendly reminder we have otel spec issue scrub 🧽 mtg tomorrow, Friday morning 8:30a PST.
    Not many spec issues to triage, so if we have quorum with collector maintainers, we’ll also continue triaging collector and collector-contrib issues.

    Jason Liu
    @JasonXZLiu
    Shovnik Bhattacharya
    @shovnik
    I have been working on migrating the CircleCI CI/CD workflows and noticed the collector build is currently failing. Is this currently being looked at?
    1 reply
    Juraci Paixão Kröhling
    @jpkrohling
    @bogdandrutu you might have missed the notifications on github, so, wanted to ping you here about this: https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/1736#discussion_r534010815
    Juraci Paixão Kröhling
    @jpkrohling
    anyone available for a review?
    Azfaar Qureshi
    @AzfaarQureshi

    @bogdandrutu (pinging you because you worked on the FluentBit loadtests)

    I've been working on migrating the CircleCI workflows to GitHub Actions and there is just 1 job left to do; loadtest. In loadtest all the tests are passing except TestLog10kDPS/FluentBitToOTLPwhich I think might have an error in the implementation. I'll attach the logs of the run in thread but the main issue im running into is that im getting conflicting messages from the logs on whether the FluentBItWriter can connect to the NewOTLPDataReceiver or not. On one hand, the logs are filled with a whole bunch of Sent: X items| Received: 0)

    2020/12/15 00:07:48 Agent RAM (RES):  49 MiB, CPU: 1.3% | Sent:     59600 items | Received:         0 items (0/sec)
    2020/12/15 00:07:51 Agent RAM (RES):  49 MiB, CPU: 0.3% | Sent:     89600 items | Received:         0 items (0/sec)
    2020/12/15 00:07:54 Agent RAM (RES):  49 MiB, CPU: 0.0% | Sent:    119600 items | Received:         0 items (0/sec)
    2020/12/15 00:07:57 Agent RAM (RES):  49 MiB, CPU: 0.0% | Sent:    149600 items | Received:         0 items (0/sec)
    ...
         validator.go:46: 
                Error Trace:    validator.go:46
                                        test_case.go:273
                                        scenarios.go:190
                                        log_test.go:78
                Error:          Not equal: 
                                expected: 0x249f0
                                actual  : 0x0
                Test:           TestLog10kDPS/FluentBitToOTLP
                Messages:       Received and sent counters do not match.

    but then I also get the following error message:

    test_case.go:312: Time out waiting for [all data items received]

    This is weird because test_case.go:312 is tc.t.Error("Time out waiting for", errMsg) meaning the errMsg in the log is saying all data items were received (which is isn't really an error 🤔).

    Every other writer for every other test is able to connect to the NewOTLPDataReceiverthough but I dont know enough about the fluentBit exporter to know why this fails.

    Any help would be appreciated, thanks!

    6 replies
    Azfaar Qureshi
    @AzfaarQureshi
    ah nvm, turns out the issue was this over here: https://github.com/open-telemetry/opentelemetry-collector/blob/master/testbed/testbed/receivers.go#L63. Works with 127.0.0.1 instead
    Mats Taraldsvik
    @meastp
    hi - I thought I would start testing hostmetrics as a first opentelemetry test, but it seems like exporting metrics to Azure Monitor / Application Insights isn't supported (in -contrib). Is this planned? Are Microsoft planning to officially support an exporter, like many other commercial product owners?
    Azfaar Qureshi
    @AzfaarQureshi
    hey @bogdandrutu open-telemetry/opentelemetry-collector#2291 is ready for another review.
    Rayhan Hossain (Mukla.C)
    @hossain-rayhan
    Hi @bogdandrutu could you have another look on this PR- open-telemetry/opentelemetry-collector#2251
    Tigran Najaryan
    @tigrannajaryan
    @/all I will be on PTO starting from tomorrow until Jan 4. I will attend today's SIG meeting and then will be out for the next 2 meetings. I am not sure what the attendance is going to look like given the holidays, but I will keep the meetings on the calendar in case there is people who want to meet.