Closed Bug 1531521 Opened 6 years ago Closed 6 years ago

GCP service account with access to stackdriver api r/o

Categories

(Cloud Services :: General, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dhouse, Assigned: oremj)

Details

I would like to access stackdriver data from Grafana running in aws. I can add stackdriver as a datasource with a service account key file. Can this be created and provided to me, or can I get access to create it?

I think the service account can be limited to firefox.gcp.mozilla.com/relops

Thanks!

I created a project within this folder and I was able to create a service account for that project.

Can I get a service account for the full folder? (I want viewer/read-only access to stackdriver monitoring.)
If not, I can find the creator/owner for test-worker/taskcluster projects and ask them to create the service accounts for me.

Looks like some of us don't have access to stackdriver, or maybe I'm missing something. Jeremy, can you check and also handle dave's request? thanks!

Flags: needinfo?(oremj)

What you'll want to do is:

  1. Create a new project (or use an existing one).
  2. Go to IAM -> Service accounts in that project.
  3. Click "Create Service Account" and follow steps creating a key at the end.
  4. Copy the service account "Email".
  5. Go to the relops folder then IAM on that folder. https://console.cloud.google.com/iam-admin/iam?folder=723902893592
  6. Click "ADD".
  7. Under "New Members" add the Email address from step 4.
  8. Give it the "Monitoring Viewer" role.
  9. Add the service account key generated in step 3 to grafana.

(In reply to Kendall Libby [:fubar] (he/him) from comment #2)

Looks like some of us don't have access to stackdriver, or maybe I'm missing something.

Want to ping me on slack and I can help you debug?

Assignee: nobody → oremj
Flags: needinfo?(oremj)
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED

Please reopen if you need further assistance.

You need to log in before you can comment on or make changes to this bug.