run_eada30493144e068

input

{
  "request": "Triage Jira ticket SREIN-1652: Yardstick's access to our fastly logs has been lost",
  "references": [
    "https://mozilla-hub.atlassian.net/browse/SREIN-1652"
  ],
  "sourceContext": {
    "issue": "SREIN-1652"
  }
}

summary

SREIN-1652 reports that Yardstick has lost access to Fastly logs, with graphs that were working "yesterday or late last week" now broken. The ticket is in Backlog status with no comments, description text only, and no linked runbook/Confluence doc to consult. Triage requires confirming what changed (credentials, IAM/API token, Fastly log-streaming endpoint config, or Yardstick-side ingestion) and reproducing/verifying scope of the outage before assigning an owner.

findings

• none

proposed actions

Thanks for flagging this. To triage the Yardstick/Fastly logs access issue, could you help confirm a few things:

1. Which specific Fastly service(s) and log destination (e.g., S3 bucket, GCS, BigQuery, Splunk, etc.) are involved, and can you share the exact dashboard/graph link that stopped updating?
2. Any error messages Yardstick is surfacing when it tries to pull the logs (auth failure, 403, empty results, etc.)?
3. Approximate timestamp of the last successful data point, to help narrow down when access broke.

On our side we'll check for:
- Recent credential/API token rotations or expirations for the Fastly service account used by Yardstick.
- Any recent changes to the Fastly logging endpoint configuration (removed/edited log streaming endpoint) via Fastly config history/audit log.
- IAM/bucket-policy changes on the log storage destination that could have revoked Yardstick's read access.

Will update this ticket once we've identified the cause. Please also link any relevant runbook/Confluence doc for this integration if one exists, since none is currently referenced here.

tool calls

[
  {
    "capability": "jira.issue.read",
    "args": {
      "key": "SREIN-1652"
    },
    "result": {
      "key": "SREIN-1652",
      "summary": "Yardstick's access to our fastly logs has been lost",
      "status": "Backlog",
      "description_text": "It looks like something has mistakenly removed yardstick\u2019s access to our fastly logs.  Example graph .  These graphs were working fine recently, I think I last looked at them yesterday (possibly late last week).",
      "comment_count": 0,
      "comments": []
    }
  }
]

log