Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Slack – Degraded service affecting multiple features

status.slack.com

Post reply on HN
Print view View original

41–50 of 246 posts

Re: Slack – Degraded service affecting multiple features

#41

Post by pmlnr »

ibero wrote: post #35
pmlnr wrote: post #25

Earlier quoted context omitted.

This is part of the problem - we all need to ask too many questions. We should be working on pre-defined tasks most of the time, where it doesn't matter if it's waterfall pre-defined or scrum time allocated.

The commenter above said they had to "solve live production problems", how exactly would "pre-defined tasks" help them?

I slipped over the "live" word, but I still stand by what I said. I most probably work in a similar environment, with tonnes of live production issues, and I believe it's a result of not being allowed to proactively plan for situations - most of the issues are a result of cost savings, systems driven to their absolute maximum capacity, etc. Live production issues are a byproduct of moving too fast, breaking too many things.

Re: Slack – Degraded service affecting multiple features

#43

Post by ratsimihah »

pennaMan wrote: post #21
darkwater wrote: post #13

Earlier quoted context omitted.

Or not. I'm remote and I cannot ask questions nor coordinate action to solve live production problems due to this outage. Slack is becoming a SPOF for many organizations, especially distributed.

Having a single communication medium is a SPOF no matter what name it has

Isn't internet a single communication medium anyway?

Re: Slack – Degraded service affecting multiple features

#44

Post by wil421 »

jt2190 wrote: post #24
majewsky wrote: post #17

Earlier quoted context omitted.

Same here. I'm on support duty and have my own outage to attend to, and that's really really hard when you cannot communicate with your experts.

Forgive me, but just to clarify... There is no “fallback” communication channel for your team to use?

There’s email, phone, whats app, group SMS, some form of WebEx or Zoom, or even a shared google doc spreadsheet with tasks for each outage.

If Slack is your only forum of communication with your team it’s time to rethink your support structure and DR plans.

Edit: It’s very unhelpful if I point out issues and don’t provide solutions. PagerDuty has a great article about Incident Response[1].

[1]https://response.pagerduty.com/

Re: Slack – Degraded service affecting multiple features

#46

Post by StreamBright »

darkwater wrote: post #13
TelmoMenezes wrote: post #9

In other news: an unexplained productivity spike has been recorded today across the tech industry.

Or not. I'm remote and I cannot ask questions nor coordinate action to solve live production problems due to this outage. Slack is becoming a SPOF for many organizations, especially distributed.

That is rather unfortunate if there is only a single channel that an organization can use in a production outage situation.

Re: Slack – Degraded service affecting multiple features

#47

Post by dpcx »

ratsimihah wrote: post #43
pennaMan wrote: post #21

Earlier quoted context omitted.

Having a single communication medium is a SPOF no matter what name it has

Isn't internet a single communication medium anyway?

It is, technically. Good thing there's also phones and SMS.

Re: Slack – Degraded service affecting multiple features

#48

Post by wastedhours »

pmlnr wrote: post #41
ibero wrote: post #35

Earlier quoted context omitted.

The commenter above said they had to "solve live production problems", how exactly would "pre-defined tasks" help them?

I slipped over the "live" word, but I still stand by what I said. I most probably work in a similar environment, with tonnes of live production issues, and I believe it's a result of not being allowed to proactively plan for situations - most of the issues are a result of cost savings, systems driven to their absolute maximum capacity, etc. Live production issues are a byproduct of moving too fast, breaking too many…

I'd style my way out of that argument by saying out reliance on tools like Slack rather than other pre-planned work builds a reliance on that one tool for all tasks being done "in the moment", which then means it's relied on as the medium in live production issues.

If there was a lower reliance on IM for all tasks, other solutions for crisis management would be utilised (potentially).

Post reply on HN