search

SigNoz / signoz

SigNoz is an open-source observability platform native to OpenTelemetry with logs, traces and metrics in a single application. An open-source alternative to DataDog, NewRelic, etc. 🔥 🖥. 👉 Open source Application Performance Monitoring (APM) & Observability tool
https://signoz.io
Other
18.92k stars 1.23k forks source link

.NET Core app fails to send otlp data to otel collector #254

Closed tonyqus closed 2 years ago

tonyqus commented 3 years ago

Hi Team,

I'm working on making tracing of .NET core app work on Signoz. I've added the code of OpenTelemetry with OTLP exporter here

And I started the docker-compose on a Windows laptop as below: image

I setup the EndPoint of otel receiver as http://:55681/v1/trace. Is this correct?

I figure this out by the following settings in docker-compose.yaml

    ports:
      - "1777:1777"   # pprof extension
      - "8887:8888"   # Prometheus metrics exposed by the agent
      - "14268:14268"       # Jaeger receiver
      - "55678"       # OpenCensus receiver
      - "55680:55680"       # OTLP HTTP/2.0 legacy port
      - "55681:55681"       # OTLP HTTP/1.0 receiver
      - "4317:4317"       # OTLP GRPC receiver
      - "55679:55679" # zpages extension
      - "13133"       # health_check

However, I still cannot make it work.

The otel collector always returns me HTTP 501 code with Json data {code=12, message='Not Implemented'}.

Any idea?

ankitnayan commented 3 years ago

@tonyqus try updating url to http://<SigNoz_IP>:4317. OTLP exporter only supports grpc as mentioned in this.

prashant-shahi commented 2 years ago

OTLP HTTP Exporter is released in v0.43.0 on port 4318 but still marked as "Beta".

Here is the sample configuration to enable it:

exporters:
  otlphttp:
    endpoint: https://example.com:4318/v1/traces