New issue
Advanced search Search tips

Issue 610540 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

chrome-internal.googlesource.com using Sheriff-o-Matic's GA tracking code

Project Member Reported by seanmccullough@google.com, May 10 2016

Issue description

view-source:https://chrome-internal.googlesource.com/infra/infra_internal/+/master/doc/troopers/playbook.md

Search for "UA-55762617-1" and you'll see it's using the same GA tracking code as Sheriff-o-Matic.

This muddies up the GA dashboard because requests for non-existent SoM paths show up in the top 10 requests.
 
Status: Available (was: Untriaged)
Hmm... Where is the GA ID defined for the playbook.md page? I can't find it anywhere in infra.git or infra_internal.git - only SoM seems to produce a hit.
It's not in the playbook.md source, it's probably in the gitiles source running on chrome-internal.googlesource.com, wherever that lives.
Project Member

Comment 3 by sheriffbot@chromium.org, Jun 2 2016

Labels: Hotlist-Google
Labels: Pri-3
Stale, dropping priority.

Comment 5 by efoo@chromium.org, Apr 26 2017

Components: -Infra>Monitoring Infra>Sheriffing>SheriffOMatic
Reassigning back to Sheriff-o-matic team to triage since this is NOT a monitoring specific issue. 
Labels: Milestone-Reliabiltiy
It looks like now the tracking code is UA-55762617-23 

Is this still a problem? I don't think I actually have access to the analytics for Sheriff-o-Matic yet. 
Cc: zhangtiff@chromium.org seanmccullough@chromium.org
Status: Fixed (was: Available)
This appears to be fixed. Taking your access issue separately off-thread.

Sign in to add a comment