Skip to content

gcloud alpha trace sinks #15590

Open
Open
@ensonic

Description

@ensonic

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

In order to use trace ingestion on a GCP project one needs to fall back to gcloud commands, e.g.

gcloud alpha trace sinks create spans bigquery.googleapis.com/projects/${data.google_project.project.number}/datasets/traces --project ${var.project}
gcloud alpha trace sinks describe spans --project=${var.project} --format='value(writer_identity)' | xargs -I {} gcloud projects add-iam-policy-binding ${var.project} --member serviceAccount:{} --role roles/bigquery.dataEditor --condition=None

New or Affected Resource(s)

  • google_trace_sink

https://cloud.google.com/trace/docs/trace-export-configure

Potential Terraform Configuration

# Propose what you think the configuration to take advantage of this feature should look like.
# We may not use it verbatim, but it's helpful in understanding your intent.

References

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions