Incidents/2022-07-03 shellbox request spike

document status: in-review

Summary

Incident metadata (see Incident Scorecard)
Incident ID	2022-07-03 shellbox request spike	Start	2022-07-03 11:17:00
Task	T310557	End	2022-07-03 11:33:00
People paged	26 (twice)	Responder count	10
Coordinators	lsobanski	Affected metrics/SLOs
Impact	Increased number of (musical) score requests coming from parsoid, overwhelming shellbox.

Increased number of (musical) score requests coming from parsoid, overwhelming shellbox. This was mitigated by adding more K8s pods to Shellbox

Documentation:

Incident Engagement™ ScoreCard
	Question	Answer (yes/no)
People	Were the people responding to this incident sufficiently different than the previous five incidents?	no
	Were the people who responded prepared enough to respond effectively	yes
	Were fewer than five people paged?	no
	Were pages routed to the correct sub-team(s)?	no
	Were pages routed to online (business hours) engineers? Answer “no” if engineers were paged after business hours.	yes
Process	Was the incident status section actively updated during the incident?	yes
	Was the public status page updated?	no
	Is there a phabricator task for the incident?	yes
	Are the documented action items assigned?	no
	Is this incident sufficiently different from earlier incidents so as not to be a repeat occurrence?	no
Tooling	To the best of your knowledge was the open task queue free of any tasks that would have prevented this incident? Answer “no” if there are open tasks that would prevent this incident or make mitigation easier if implemented.	no
	Were the people responding able to communicate effectively during the incident with the existing tooling?	yes
	Did existing monitoring notify the initial responders?	yes
	Were the engineering tools that were to be used during the incident, available and in service?	yes
	Were the steps taken to mitigate guided by an existing runbook?	no
Total score (count of all “yes” answers above)		7