StatusCake

Slack Support for Downtime Alerts

website monitoring

We have continued to roll out support for great 3rd party apps and today we are happy to announce StatusCake has put live support for the up and coming real time communication platform – Slack.

Slack is an IRC like environment for your team to be able to communicate with each other, we have seen a surge in users who have requested we added support for it and so continuing with our tradition of you speak we listen we have added two new ways to integrate this great piece of software

Notifications from StatusCake to Slack

You can now set-up StatusCake to send notifications to one or more of your Slack Channels. To get started is easy – follow these easy steps:

Inside Slack:

  • In the Slack App menu, scroll down and click the “Customize Slack” option.
  • Next click “Configure Apps” to the left.
  • In the “Manage” menu, select “Custom Integrations”
  • Add a new incoming web hook configuration, if you don’t see this already, you’ll need to create one.
  • Choose a channel to which the alerts should be sent.
  • Copy the URL with the Token that’s provided.

Inside StatusCake:

  • Go to the Integrations section
  • Select Slack in the drop down
  • Insert your Token URL, and optionally type a channel name to send slack to
  • You must add an “Alias” (Name for the integration) – or the integration will not work
  • Save and then add this 3rd party service to any contact group of your choice under the “Push Notifications” field

We’ve also added the ability to query your StatusCake accounts key statistics right from inside Slack. No need to go to StatusCake every time you want to see what sites (if any) are down from your account. To get started with this –

Inside StatusCake:

  • Go to the Integrations section
  • Scroll down and in the Pull Service URLs copy the StatusCake URL for Slack

Inside Slack:

  • Go to “Your Account”
  • In the Slack App menu, scroll down and click the “Customize Slack” option.
  • Next click “Configure Apps” to the left.
  • In the “Manage” menu, select “Custom Integrations.
  • Add a new outgoing web hook configuration, if you don’t see this already, you’ll need to create one.
  • Optionally pick channel (or use “All”)
  • Pick your Trigger Word(s), We’d suggest something like “StatusCake”
  • Put the URL you copied from StatusCake in the URL(s) box

Share this

More from StatusCake

When Code Becomes Cheap: The New Reliability Constraint in Software Engineering

4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,

Buy vs Build in the Age of AI (Part 3)

5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t

Buy vs Build in the Age of AI (Part 2)

6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff

Buy vs Build in the Age of AI (Part 1)

5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything

Alerting Is a Socio-Technical System

3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting

Designing Alerts for Action

3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.