by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Austin Parker
    @austinlparker
    there's a k8s operator for it
    Naseem
    @naseemkullah
    k8s operator to sidecar inject or deploy as ds?
    Austin Parker
    @austinlparker
    not sure about the details, I'd start here -> https://github.com/open-telemetry/opentelemetry-collector
    I know it supports both sidecar and daemonset
    Naseem
    @naseemkullah
    Great! So, in a setup where sampling is done at the collector level, do you set sampling rate to 1 everywhere else (in the apps)
    Austin Parker
    @austinlparker
    generally yes
    Naseem
    @naseemkullah
    :thumbsup:
    HugoMRAmaro
    @HugoMRAmaro
    Hello, does anyone know if open-telemetry works well with micro payara. I mean, instead of using jaeger for example, I just need to run open-telemetry and then I start collecting traces?
    HugoMRAmaro
    @HugoMRAmaro
    or does anyone can recommend a good article about how to start with open-telemetry
    Tristan Sloughter
    @tsloughter
    HugoMRAmaro
    @HugoMRAmaro
    thank you
    Paulo Janotti
    @pjanotti
    Naseem
    @naseemkullah
    Is there a docker image for the collector hosted somewhere? opentelemetry/collector?
    or no, this is up now https://hub.docker.com/u/otel
    Naseem
    @naseemkullah
    Thanks @tsloughter, no tags for https://hub.docker.com/r/otel/opentelemetry-collector it seems, is that because there is no stable release of the collector yet?
    BTW it feels like prepending the image names with "opentelemetry-" could be skipped seeing that the repo name is "otel" which entails that already. If anything the https://hub.docker.com/u/opentelemetry repo could be used instead, if opentelemetry indeed owns it.
    Tristan Sloughter
    @tsloughter
    oh, I guess they haven't started publishing yet
    didn't realize you could have names of images without published tags..
    maybe supposed to use the -dev images for now https://hub.docker.com/r/otel/opentelemetry-collector-dev/tags
    Austin Parker
    @austinlparker
    I think you just use the :latest tag to get whatever is most current
    so docker pull otel/opentelemetry-collector-contrib:latest
    we unfortunately do not control the opentelemetry namespace on docker hub
    Tristan Sloughter
    @tsloughter
    na, latest would show up in the tags list on docker hub
    there are no images for those non -dev ones
    Austin Parker
    @austinlparker
    oh, weird. I guess it's not in sync yet
    Naseem
    @naseemkullah

    we unfortunately do not control the opentelemetry namespace on docker hub

    Ah too bad. Regardless, what about dropping the preceding opentelemetry- in the image names? And in fact just have 1 image for the collector with various tags. e.g.: otel/collector and tags such as latest, stable, contrib, dev and such? Pardon the nitpicking :)

    Naseem
    @naseemkullah
    Also, I'd like to propose a helm chart for the collector, any chance we could create an opentelemetry/helm-charts repo?
    Austin Parker
    @austinlparker
    I know there's a Kubernetes operator for the collector already, but I'm not sure if there's a helm chart. These are good questions! I'd open an issue for them on the collector repo.
    Naseem
    @naseemkullah
    WIll do, thanks!
    Steve Flanders
    @flands
    No helm chart yet — PRs welcomed!
    Naseem
    @naseemkullah
    sounds good! I've created an issue open-telemetry/opentelemetry-collector#752 asking for a helm-charts repo.
    Naseem
    @naseemkullah
    I'm having issues chaining spans together, nginx ingress is using jaeger client to instrument, and can chain to another jaeger instrumented service, but it does not seem to chain with otel instrumented services that also emit spans. Any ideas?
    2 replies
    neith00
    @neith00
    I'm actively trying to better monitor a distributed system which has a message broker between its component. My idea, is to provide a tool to component developers to track the messages that goes through the system. For instance, sometimes during development we (hardly) notice that some messages are lost/dropped/whatever during the process. Could OpenTelemetry help me to build a tool which would give us the status/location of each messages going through our system?
    Austin Parker
    @austinlparker
    @neith00 yes, this would be a good use case for tracing.
    neith00
    @neith00
    @austinlparker I was thinbking using prometheus as backend.
    Austin Parker
    @austinlparker
    ehh... probably? you'd have really high cardinality because you'd need a separate bucket per message.
    neith00
    @neith00
    well I don't think creating a bucket per message is worth unless I delete the bucket right after get rid of the message though
    In this case I should push the metrics to prometheus rather beeing scraped
    13217 Amasia
    @13217amasia
    Where can I find information on OT overhead/throughput loss over different sampling ratios? I understand this might be difficult question to answer but maybe there are some existing benchmarks...
    I also would like to learn if it's possible to control sampling ratio, when an application is just instrumented without any intrusive code changes? E.g. possibly by injecting a sampling ratio parameter to instrumentation parameters?
    Thank you!
    Naseem
    @naseemkullah
    This message was deleted
    2 replies
    Naseem
    @naseemkullah
    @13217amasia regarding sampling rate control: if using opentelemetry collector, sampling could be configured there (see https://github.com/open-telemetry/opentelemetry-collector/tree/master/processor#sampling-processor). If not it would be nice that a sampling rate be able to be passed as env var, I have a PR open for this in the js implementation: open-telemetry/opentelemetry-js#1069
    Ayushi Singh
    @ayusheesingh
    I'm trying to use the azuremonitorexporter but am getting an "invalid instrumentation key" error even though it matches the one I see for my Application Insights resource on Azure Portal - any recommendations on how to fix?
    Nicolas MacBeth
    @Nicolas-MacBeth
    Hey, not sure if this is where should ask this but here goes: It's my understanding that the Prometheus receiver for the OTel collector should just work with any Prometheus exporter, but I'm having issues with https://github.com/prometheus/mysqld_exporter . I get this message logged in the collector: {"level":"info","ts":1591373779.4030387,"caller":"internal/metrics_adjuster.go:357","msg":"Adjust - skipping unexpected point","type":"UNSPECIFIED"}, followed by (i think this is just Stackdriver exporter not happy with the prior error^) {"level":"info","ts":1591373782.0302048,"caller":"scrape/scrape.go:930","msg":"","level":"warn","scrape_pool":"mysql_exporter_otel","target":"http://localhost:9104/metrics","msg":"append failed","err":"[rpc error: code = ResourceExhausted desc = Your metric descriptor quota has been exhausted.; rpc error: code = ResourceExhausted desc = Your metric descriptor quota has been exhausted.; rpc error: code = ResourceExhausted desc = Your metric descriptor quota has been exhausted.; rpc error: code = ResourceExhausted desc = Your metric descriptor quota has been exhausted.; rpc error: code = ResourceExhausted desc = Your metric descriptor quota has been exhausted.]"}
    4 replies
    Does the mysql exporter need to be modified to format the metrics according to the collector, or is there something I'm missing in the collector config?
    dcwangmit01
    @dcwangmit01_twitter

    Hi. I've got comments/questions after a few days of playing with OTel.

    1) Why is UpDownCounter instrument not called Gauge? The six instrument types all have very similar naming components (Counter, UpDownCounter, ValueRecorder, SumObserver, UpDownSumObserver, ValueObserver). I'm sure I'll get used to this over time, but as a newb the naming pattern is hard to spot and requires a lot of spec checking while coding.

    2) The UpDownCounter instrument, which is equivalent to Gauge, is updated via an Add() function. How do I update this counter when I already have the final value? Right now it appears to me that I need to track the prior value, do the math to find the delta, and then call the Add() function with the delta as the value. I would rather just update the metric with the current value. Is there a way to directly set the value for an UpDownCounter instrument?

    3) It took me a while to realize that ValueRecorder and ValueObserver instruments were summary metrics that had multiple values (MinMaxSumCount), and thus would be dropped by the OTel exporter for Prometheus. To me, "Value" suggests a single scalar value. I would have expected the exporter for Prometheus to export the LastValue and just work for Value* instruments. This burned at least a day of debugging for me.

    Thanks all, for this amazing project. I've read some of the spec discussions and the decisions made have all been well considered.

    John Watson
    @jkwatson
    @dcwangmit01_twitter I'm not sure I get why you say that UpDownCounter is the same as a Gauge. From what I know of gauges, they generally only aggregate as the LastValue, not as a sum.
    23 replies
    Mouliksoni
    @Mouliksoni
    Hi, I have a quick question about exporter config (agent side). I'm looking to specify certain attributes to the exporter, I see that there is an way to specify attributes when I create a new instance of the exporter (in my case new new CollectorExporter for nodejs). I was looking for a way to specify the attributes via a config file instead, like how it's possible to do it on the collector side?
    Austin Parker
    @austinlparker
    @Mouliksoni not at this time, although I think there's some interest in such a thing
    3 replies