New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exporter/stackdriver: allow credentials file #1734
Comments
from the triage session at the sig mtg today, @dashpole volunteered to be assignee of this issue |
According to the [community charter](https://github.com/open-telemetry/community/blob/main/community-membership.md#responsibilities-and-privileges-2): > Expected to be responsive to review requests (inactivity for more than > 1 month may result in suspension until active again) Given @paivagustavo has returned to an active state, this reinstates their status as an Approver.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This will be fixed by GoogleCloudPlatform/opentelemetry-operations-go#527 |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
This was fixed by GoogleCloudPlatform/opentelemetry-operations-go#527 |
Is your feature request related to a problem? Please describe.
Traces are exported to Google Cloud Trace to the application's project. It is currently impossible (?) to specify another project as the target for these traces, or to use a specific service account.
For example, the traces sent to a collector hosted on GKE cannot easily be exported to Cloud Trace in another project, using another service account.
Describe the solution you'd like
Specifying a credentials file's path in the collector config would solve this issue. This file is the JWT public key specified at https://cloud.google.com/iot/docs/how-tos/credentials/jwts.
Describe alternatives you've considered
The only alternative that I know of is to clone this repo, manually add this ability, and build a new image to deploy.
Additional context
The modified code is essentially
The collector's config file can then contain the following:
If this is considered as an interesting change, I can make a PR with the changes if needed.
The text was updated successfully, but these errors were encountered: