chore(jira slos): Record APIError as a halt#89133
chore(jira slos): Record APIError as a halt#89133Christinarlong wants to merge 1 commit intomasterfrom
Conversation
❌ 1 Tests Failed:
View the top 1 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
iamrajjoshi
left a comment
There was a problem hiding this comment.
changes lgtm, could we add a test?
for ur 2nd point, i agree it a bug. we probably need to consume some webhook if we don't already
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
|
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
While digging into
status_sync_outboundon rotation, I saw our Jira SLOs forsync_status_outboundare kinda sus. For this one, we're recording failure in the case whereFixes: https://sentry.sentry.io/issues/5681104673/events/latest/?project=1&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D%20sync_status_outbound%20integration%3Ajira&referrer=latest-event&sort=date&statsPeriod=24h&stream_index=0
I have a followup for the
ApiInvalidRequesterrors (which I also think are halt), but I want to wait a bit to collect some more data before classifying that case officially.