Closed DazWilkin closed 1 year ago
DazWilkin
commented
5 years ago I tried shipping traces to Jaeger directly and also did not appear to receive traces in Jaeger.
So, it's probably not the OpenCensus Agent but my code and|or the Jaeger Exporter.
I'm going to try another configuration.
DazWilkin
commented
5 years ago I was able to ship traces to Jaeger directly using a mash-up of OpenCensus documentation:
This E2E example for tracing with Zipking: https://opencensus.io/quickstart/go/tracing/
With this -- insuffiicient (!?) -- Jaeger example: https://opencensus.io/exporters/supported-exporters/go/jaeger/
I remain unable to export traces using ocgrpc. Evidently it's something I'm not doing but it remains unclear to me what I'm doing incorrectly and why this doesn't work.
One additional "Aha!" is that the Jaeger configuration is inconsistent and must be configured as such. Evidently the protocol (http) is required for the collector but not the agent:
agentEndpointURI := "localhost:6831"
collectorEndpointURI := "http://localhost:14268/api/traces"Curiously, the Agent's configuration for Jaeger uses only the collectorEndpointURI so -- if the Jaeger Agent endpoint (6831) is required by the Jaeger Exporter it's unclear how this works when its used by the OpenCensus Agent:
https://github.com/census-instrumentation/opencensus-service#exporters
jaeger:
collector_endpoint: "http://127.0.0.1:14268/api/traces"
flands
commented
5 years ago @DazWilkin nice find -- yes the agent/collector configuration is known to be inconsistent. This will be addressed in the OpenTelemetry Service.
ChrisCoe
commented
5 years ago @DazWilkin I ran into the same problem when I tried using the agent to send to jaeger . @flands If this is not going to be addressed in OpenCensus Service, is there a work around?
I get a similar error here where my traces don't send, but instead some internal agent traces are generated. I am running the example/main.go
I am trying to incorporate an exporter I created for Azure Monitor to be used in the OpenCensus agent for my internship project. I don't think the error is comming from my exporter code.
Result on Azure Monitor:
What my exporter is exporting on ExportSpan, but they don't all apear on Azure Monitor
pjanotti
commented
5 years ago @ChrisCoe these spans that you see seem like the ones generated for z-pages by gRPC. The issue mentioned above is a inconsistency for the Jaeger exporter if it applies to your exporter is not clear. Perhaps if you can share your code we can take a look to see if that is the case or not.
ChrisCoe
commented
5 years ago @pjanotti Sorry for the late reply, and thank you for your offer. I was able to find my error to eliminate these extra spans. I accidentally registered my custom exporter right after creating it when the OC agent exporter already registered it. By having only the OC agent register, I eliminated this problem.
SergeyKanzhelev
commented
5 years ago @ChrisCoe I know it's a very old issue. Curious, did you manage to make Azure exporter work? Do you plan to merge it?
dashpole
commented
1 year ago This repository is now archived, and is succeeded by https://github.com/open-telemetry/opentelemetry-collector.
I tried routing traces through the Agent to Zipkin. When it didn't (appear) to work, I added Jaeger. Neither appear to work. I think I'm missing something obvious :-(
ocagent.yaml
and a subset of docker-compose.yaml:
Here's the /tracez for one of the service's exporting to the Agent:
These traces don't appear to be reflected in the Agent's /tracez. So that's one problem. The Agent is generating its own gRPCs though so I would expect to at least see these:
Jaeger is reporting data but it appears to be reporting just traces of its own services:
Zipkin shows nothing:
The logs show nothing obvious: Jaeger:
Zipkin: