open-telemetry/community

THIS FORUM IS NO LONGER ACTIVE. Join us on CNCF Slack: https://cloud-native.slack.com/archives/CJFCJHG4Q.

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?

Where communities thrive

People

Repo info

Activity