Skip to content
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

Write up what we do related to site cookies #372

Closed
8 tasks done
davidjoy opened this issue Jul 26, 2023 · 4 comments
Closed
8 tasks done

Write up what we do related to site cookies #372

davidjoy opened this issue Jul 26, 2023 · 4 comments
Assignees

Comments

@davidjoy
Copy link

davidjoy commented Jul 26, 2023

Background

Amber Dorst over in Marketplace was willing to explore whether one of her teams (or adjacent teams) would be able to take over ownership of site cookie monitoring.

She asked us to write up what we do related to site cookies, how we monitor, etc., so she can help figure out where it should go.

Current State

Initial draft of the ownership transfer document is here: Site Cookie Size Monitoring - Ownership Transfer

Open Questions/Subtasks

  • Where are the cookie size alerts configured in New Relic? Link them into this document.
  • What is the name of the alert(s)? Update the runbook name to match, clarify that “xyz” is referring to whatever environment the alert came from.
  • What else is missing from the transfer process/are there other systems involved beside NR and OpsGenie?
  • Any other related documents we’ve missed?
  • Does the ownership transfer process below look correct? Update with details (particularly for the NR and OpsGenie transfers). What additional knowledge would we want to transfer in person, if anything? If nothing, assume that a transfer session will be done only if the receiving team wants it.

Acceptance Criteria

  • A document describing how we would transfer ownership of site cookie monitoring.
  • Send the document to Amber Dorst
  • Determine next steps/timeline for ownership transfer

Existing docs linked in standup

@davidjoy davidjoy converted this from a draft issue Jul 26, 2023
@davidjoy davidjoy self-assigned this Jul 27, 2023
@robrap
Copy link
Contributor

robrap commented Jul 27, 2023

Moving this to Blocked while assigned to @davidjoy. David - please let us know when you are done with this ticket.

@robrap robrap moved this to Blocked in Arch-BOM Jul 27, 2023
@davidjoy davidjoy removed their assignment Jul 31, 2023
@davidjoy davidjoy moved this from Blocked to Prioritized in Arch-BOM Jul 31, 2023
@robrap robrap removed the status in Arch-BOM Aug 1, 2023
@jmbowman jmbowman moved this to Prioritized in Arch-BOM Aug 1, 2023
@rgraber rgraber moved this from Prioritized to Groomed in Arch-BOM Aug 3, 2023
@rgraber rgraber moved this from Groomed to On-Call in Arch-BOM Aug 3, 2023
@dianakhuang dianakhuang self-assigned this Aug 7, 2023
@dianakhuang dianakhuang moved this from On-Call to In Progress in Arch-BOM Aug 7, 2023
@dianakhuang
Copy link
Member

i have updated the doc. I don't think we need to do a synchronous transfer session unless the receiving team wants it.

@dianakhuang dianakhuang moved this from In Progress to In Code Review in Arch-BOM Aug 8, 2023
@robrap
Copy link
Contributor

robrap commented Aug 15, 2023

@dianakhuang: I'm not sure that "in code review" is the best status. The open AC is to determine next step and timeline. Is that blocked or in-progress, or other? Regarding Amber's review, I don't think we need to really track that on our board. Thoughts?

@dianakhuang dianakhuang moved this from In Code Review to Blocked in Arch-BOM Aug 17, 2023
@github-project-automation github-project-automation bot moved this from Blocked to Done in Arch-BOM Aug 23, 2023
@dianakhuang
Copy link
Member

Closed because we have acknowledgement from the new team, and if there needs to be any followup work that results from their review, we can make a new ticket with those action items.

@jristau1984 jristau1984 moved this from Done to Done - Long Term Storage in Arch-BOM Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done - Long Term Storage
Development

No branches or pull requests

3 participants