Functionality Clarification
lukemauldinks opened this issue · comments
Could you please more clearly document how your crate relates to https://github.com/abdolence/opentelemetry-gcloud-trace-rs
My use case is that I want to use opentelemetry and the tracing crate and have both traces and log data sent to GCP for collection. Do I need to use both the tracing-stackdriver crate and the opentelemetry-gcloud-trace-rs crate or can I configure the tracing-stackdriver crate to accomplish all of that functionality?
Thanks for the question @lukemauldinks!
I'm not super familiar with opentelemetry-gcloud-trace-rs, but it looks like an exporter of traces, specifically, to Cloud Trace through the API/SDK. tracing-stackdriver is for formatting tracing spans as structured logs that GCP can parse and recognize.
One of the fields that tracing-stackdriver can add to your structured logs are span and trace IDs that are then automatically ingested in Cloud Trace, too. So for my projects, just using tracing-stackdriver with the opentelemetry feature is good enough to populate traces in Cloud Trace. But if you wanted to export those traces directly to Cloud Trace instead of relying on the log aggregator, then there's no reason you couldn't use both tracing-stackdriver and opentelemetry-gcloud-trace-rs to accomplish that.
Does that answer your question?
Yes, your response along with abdolence/opentelemetry-gcloud-trace-rs#31 helped me to get a working configuration. I think it would be nice to update the documentation with the summary from this issue.
I'd welcome a pull request of a documentation change that you'd like to see, if you have something specific in mind. But in the meantime, I'm going to close this issue as an answered question!