Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Zaheer Shaik
    @zaheershaik

    Hi. Could somebody advice on how to setup “trace ID aware load balancing”? I’m trying to setup OTel collector cluster which can sample successful traces, but not sample a trace with atleast one erroneous spaan.

    I see this note on tail sampling processor repo “Technically, trace ID aware load balancing could be used to support multiple collector instances, but this configuration has not been tested. “.

    supriya mahajan
    @supriya
    Hi, can someone help me understand if an open-telemetry collector be deployed just as a gateway service for multiple applications? Or is it always mandatory to run the collector as an agent on the host container?
    supriya mahajan
    @supriya
    I keep reading that it is recommended to run collector as an agent on the host container and additionally we can run collector as a gateway service as well. It tells me that running the collector as an agent is a must and running the collector as a gateway service is optional?
    sunfuze
    @sunfuze

    I keep reading that it is recommended to run collector as an agent on the host container and additionally we can run collector as a gateway service as well. It tells me that running the collector as an agent is a must and running the collector as a gateway service is optional?

    Design doc. Imo, if your all ready have old collector agents in system, like jaeger agents, probably run collector as standalone service is better, you needn’t change every applications

    I keep reading that it is recommended to run collector as an agent on the host container and additionally we can run collector as a gateway service as well. It tells me that running the collector as an agent is a must and running the collector as a gateway service is optional?

    Design doc. Imo, if your all ready have old collector agents in system, like jaeger agents, probably run collector as standalone service is better, you needn’t change every applications

    If you just introduct opentelemetry first time run collector as an agent maybe better, application can report data to nearest collector.

    Brad Frost
    @bradfrosty

    Hey all, looking for some advice on how to structure spans that we have implemented at the transport layer as opposed to application layer. We have TCP load balancer in our edge network that manages incoming connections/certs. We recently implemented 3 different spans: one for the connection establishment (a parent span), another for fetching the cert (child), and finally one for how long to proxy to the corresponding backend service (child).

    Given the connection establishment span is at the TCP layer, this makes it difficult to extract context from a client side span since we don't have access to HTTP headers (at least in that moment). Ideally, our client side spans would be the parent of the connection establishment span.

    I'm wondering if this is possible, or if our spans should be setup differently. There aren't too many examples online of running distributed traces below the application layer.

    2 replies
    aniand
    @aniand
    Hello, opentelemetry has been introduced as observability framework for cloud native software. Can opentelemetry also be used for client desktop applications (considering casses like being offline, buffering etc.)?
    2 replies
    Daniel Gorlovetsky
    @DanielGorlo
    Hey I was wondering if there are any plans to fix protobuf exporter support in client-side based opentelemetry-js implementations
    4 replies
    Kavindu Ariyasinghe
    @kavndu

    Hi all, I'm trying to dynamically turn on/off traces in opentelemetry agent level. I used Dotel.traces.sampler.

       java -javaagent:opentelemetry-javaagent-all.jar
 -Dotel.traces.exporter=otlp \
 -Dotel.exporter.otlp.endpoint=http://localhost:4317 \
 -Dotel.otlp.span.timeout=4000 \
 -Dotel.resource.attributes=service.name=pet-clinic \
 -Dotel.traces.sampler="always_off" \
 -jar target/spring-petclinic-2.4.5.jar

    But the problem is when I need to turn on(Dotel.traces.sampler="always_on") traces I should stop the process and rerun the command by changing the environment variable. It means I need to restart my application too. Is there any alternative solution to turn on/off traces without restarting the application.

    2 replies
    sumitm-iiit
    @sumitm-iiit
    Hi All, I could see OTEL instrumentation libraries available for specific framework in case of java. I was wondering how can I use those libraries in my application? Example of one of the libraries - https://mvnrepository.com/artifact/io.opentelemetry.instrumentation/opentelemetry-auto-servlet
    Stephen Hong
    @stephenhong
    Hello team, I'm trying to forward metrics from one otel collector to another otel collector. These collectors are running on two different ec2 instances. I configured otlp receiver on one collector and otlp and otlp http exporter on the other. However, I get context deadline exceeded error from the collector that's trying to export metrics. Any suggestions on how to resolve this? Also, is there a better receiver/exporter pair for this particular use case? Thank you.
    2 replies
    xinnjie
    @xinnjie

    Hello team, I'm wondering how to make use of Link in grafana query
    As current description of Link

    A Span may be linked to zero or more other Spans (defined by SpanContext) that are causally related. Links can point to Spans inside a single Trace or across different Traces. Links can be used to represent batched operations where a Span was initiated by multiple initiating Spans, each representing a single incoming item being processed in the batch.

    Once we attach Link to span, how do we make use of it in grafana query?
    Suppose I attach a Link to span A (in traceA ) to spanB (in traceB), can I get result of traceB when querying traceA in grafana?

    Yotam loewenbach
    @yotamloe

    Hello team we have an issue with our logzio exporter users are getting errors using it from opentelemetry-collector-contrib image version >= 0.24

    otel-agent    | Error: cannot build pipelines: cannot build builtExporters: error creating logzio exporter: mkdir /tmp: permission denied
otel-agent    | 2021/06/07 10:20:51 application run finished with error: cannot build pipelines: cannot build builtExporters: error creating logzio exporter: mkdir /tmp: permission denied

    The exporter works fine with version <=0.23.
    Does anyone know what could cause those errors from version 0.24? And what can we do to solve it?

    3 replies
    shailesh
    @shaileshppatil_twitter
    is there an example of a scala project for instrumentation using opentelemetry-javaagent-all.jar
    5 replies
    csuzhang
    @zhyChesterCheung

    Hey guys, when I submit PR with #1973 and running the workflows, something wrong happened with test-coverage: 

    {'detail': ErrorDetail(string='Unable to locate build via Github Actions API. Please upload with the Codecov repository upload token to resolve issue.', code='not_found’)}

    How should I solve this problem?

    1 reply
    genemat
    @genemat
    Hello I've just discovered Opentelemerty. Is there a tutorial that shows how to run a sample test, by sending a metric via CURL and viewing the output in a file. Just want to confirm that I've installed OTEL correctly and that it is running.
    mhack1
    @mhack1
    hi can any body help me in .net core
    Paulo Janotti
    @pjanotti
    @mhack1 all discussion has moved to the CNCF slack. Ask your question on the #otel-dotnet channel.
    moenzuel
    @moenzuel:matrix.org
    [m]
    Well not going to join slack over matrix
    Leonardo
    @leonardotorresaltez
    Hello all, are there some openTelemetry instrumentation for pure java script ? . I mean there are many but all of them are using nodejs (https://opentelemetry.io/docs/js/getting-started/browser/ ) , what if the application is not using nodejs ?
    Haytham Mohamed
    @Haybu
    prometheus configuration does not allow rule_files configuration. what is the alternative configuration to set that up and point to rule files ?
    matthewgrima
    @matthewgrima
    hello, is there a way I can add tags to all spans (dotnet)? We have multiple environments shipping to the same jaeger and we'd like to be able to filter and identify environments
    Mats Taraldsvik
    @meastp
    @matthewgrima all discussion has moved to the CNCF slack.
    Ask your question on the #otel-dotnet channel.
    Alpesh Jamgade
    @jam99:matrix.org
    [m]
    otelcol.service: Failed to load environment files: No such file or directory
    hi can anyone help me with this
    i have freshly installed otelcol_0.44.0_linux_amd64.deb in ubuntu 20.03
    and it is failing to read env variables file 
    $ cat /etc/otelcol/otelcol.conf 
# Systemd environment file for the otelcol service

# Command-line options for the otelcol service.
# Run `/usr/bin/otelcol --help` to see all available options.
OTELCOL_OPTIONS="--config=/etc/otelcol/config.yaml"
    $ cat /etc/otelcol/config.yaml
extensions:
  health_check:
  pprof:
    endpoint: 0.0.0.0:1777
  zpages:
    endpoint: 0.0.0.0:55679

receivers:
  otlp:
    protocols:
      grpc:
      http:

  opencensus:

  # Collect own metrics
  prometheus:
    config:
      scrape_configs:
      - job_name: 'otel-collector'
        scrape_interval: 10s
        static_configs:
        - targets: ['0.0.0.0:8888']

  jaeger:
    protocols:
      grpc:
      thrift_binary:
      thrift_compact:
      thrift_http:

  zipkin:

processors:
  batch:

exporters:
  logging:
    logLevel: debug

service:

  pipelines:

    traces:
      receivers: [otlp, opencensus, jaeger, zipkin]
      processors: [batch]
      exporters: [logging]

    metrics:
      receivers: [otlp, opencensus, prometheus]
      processors: [batch]
      exporters: [logging]

  extensions: [health_check, pprof, zpages]
    $ sudo dpkg -i otelcol_0.44.0_linux_amd64.deb
Selecting previously unselected package otelcol.
(Reading database ... 347245 files and directories currently installed.)
Preparing to unpack otelcol_0.44.0_linux_amd64.deb ...
Unpacking otelcol (0.44.0) ...
Setting up otelcol (0.44.0) ...
Created symlink /etc/systemd/system/multi-user.target.wants/otelcol.service → /lib/systemd/system/otelcol.service.
    Alpesh Jamgade
    @jam99:matrix.org
    [m] 
    $ systemctl  restart otelcol.service 
$ journalctl -u otelcol.service 
-- Logs begin at Thu 2022-02-17 13:45:25 IST, end at Thu 2022-02-24 11:28:02 IST. --
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to load environment files: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to run 'start' task: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed with result 'resources'.
Feb 19 18:00:41 voyager2 systemd[1]: Failed to start OpenTelemetry Collector.
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Scheduled restart job, restart counter is at 1.
Feb 19 18:00:41 voyager2 systemd[1]: Stopped OpenTelemetry Collector.
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to load environment files: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to run 'start' task: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed with result 'resources'.
Feb 19 18:00:41 voyager2 systemd[1]: Failed to start OpenTelemetry Collector.
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Scheduled restart job, restart counter is at 2.
Feb 19 18:00:41 voyager2 systemd[1]: Stopped OpenTelemetry Collector.
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to load environment files: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to run 'start' task: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed with result 'resources'.
Feb 19 18:00:41 voyager2 systemd[1]: Failed to start OpenTelemetry Collector.
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Scheduled restart job, restart counter is at 3.
Feb 19 18:00:41 voyager2 systemd[1]: Stopped OpenTelemetry Collector.
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to load environment files: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed to run 'start' task: No such file or directory
Feb 19 18:00:41 voyager2 systemd[1]: otelcol.service: Failed with result 'resources'.
Feb 19 18:00:41 voyager2 systemd[1]: Failed to start OpenTelemetry Collector.
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Scheduled restart job, restart counter is at 4.
Feb 19 18:00:42 voyager2 systemd[1]: Stopped OpenTelemetry Collector.
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Failed to load environment files: No such file or directory
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Failed to run 'start' task: No such file or directory
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Failed with result 'resources'.
Feb 19 18:00:42 voyager2 systemd[1]: Failed to start OpenTelemetry Collector.
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Scheduled restart job, restart counter is at 5.
Feb 19 18:00:42 voyager2 systemd[1]: Stopped OpenTelemetry Collector.
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Start request repeated too quickly.
Feb 19 18:00:42 voyager2 systemd[1]: otelcol.service: Failed with result 'resources'.
Feb 19 18:00:42 voyager2 systemd[1]: Failed to start OpenTelemetry Collector.
lines 1-34
    Inner Insight
    @insight_inner_twitter
    Hi there,
    I'm trying to send metrics to prometheus using otel collector, but errors out as below
    2022/02/28 17:12:07 collector server run finished with error: cannot start exporters: listen tcp 34.125.177.249:9090: bind: cannot assign requested address
    Michael Murphy
    @mrblonde91
    Hi all, I'm currently digging into coupling datadog with otlp. However the built-in metrics from dotnet around things like garbage collection etc don't seem to work when running just the otlp collector, are these not possible to capture ATM?
    Kenny Long
    @kennethlong
    Reminder, all discussion has moved to the CNCF slack. Ask your question on the #otel-dotnet channel.
    Bruno Baptista
    @brunobat__twitter
    Hi All. There is a terminology inconsistency that I would like to clarify.
    On the protocol spec: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/protocol/otlp.md
    The server side is referenced as a Collector.
    However, in the public documentation here: https://opentelemetry.io/docs/concepts/components/#collector
    Collector has the role of receiver, processor and exporter.
    I assume the protocol readme is older and when they mention collector, they are in fact talking about a receiver. Am I correct?