The on-call experience has been broken for too long—from hideous, confusing user interfaces to noisy alerts and exorbitant pricing. We've had enough. Introducing Rootly On-Call: A modern on-call solution built by incident experts.
📯 We're excited to announce V2 of our wildly popular and native Rootly Status Page!
› Show impacted 3rd party components like
@awscloud
› Automate publishing via workflows
› Integrates directly with
@Statuspage
› Publish directly from
@SlackHQ
🏆 Thank you to
@InfoSec_Awards
for recognizing Rootly as the Overall SOAR (Security Orchestration, Automation, Response) Solution Provider of the Year!
When there's a problem that might be an incident, do you investigate before declaring and risk prolonging time to assemble? Or declare and risk sounding alarm bells for a false alarm?
Here's how to eliminate this dilemma entirely with a triage phase:
⬆️ Announcing the ability for Rootly users to request missing user permissions directly in
@SlackHQ
!
Users with roles without sufficient privileges (e.g. Observer or Read-Only) now have a streamlined way to request permission upgrades from their admin.
🗓️ Prepping for Black Friday? Save the date Oct 3!
We're partnering with
@VoidIncidents
to bring you a webinar analyzing past incidents and dissecting why complex systems fail.
(FREE) Registration is open now at the link below!
☁️ Rootly is now available on the
@awscloud
Marketplace, providing the fastest and most streamlined way to procure Rootly in a few clicks!
Learn more on AWS:
🤓 Launching our most advanced
@SlackHQ
customization feature, Slack Blocks, that enables power users to custom code their own Slack messages sent during incidents!
Control everything from fonts, clickable action buttons, formatting, links, and more.
🎧 Our Reliability Advocate
@AshleyOnCall
recently sat down with SRE legend
@niallm
and
@software_daily
to discuss the technical and non-technical elements of incident response, and how they all work together. Check out the podcast episode here!
🤝 Incident management is a multiplayer game.
SREs need support from across the business to do their jobs well. Here are 4 ways to de-silo SREs from the rest of the organization.
#SRE
#DevOps
#IncidentManagement
#SaaS
#Software
📞 View who's on-call directly from
@SlackHQ
! Finally retire any manual workarounds.
Supports
@pagerduty
,
@Opsgenie
, and
@VictorOps
with the ability to directly escalate if needed.
🔀 We’re excited to introduce the ability to create sub-incidents from parent incidents!
Large scale incidents often impact multiple product areas and teams to varying degrees.
Being able to break the incident into different workstreams can often help
🔐 Announcing that Rootly has officially become a
@github
Secret Scanning partner!
Enabling Rootly tokens to be protected by GitHub’s secret scanning process and help users identify and remediate secrets that may have been inadvertently exposed.
🗃️ Excited to officially partner with
@NotionHQ
on the on our integration with Notion Projects!
Customers already leverage our Notion integration to automatically generate retrospectives but now they can do the same for tracking incident action items!
Good morning from
@SREcon
EMEA! If you're here in Dublin, make sure you swing by the Rootly booth to chat incident management and get some super fun and nostalgic swag 🔥
📊 We are excited to launch automated dashboard reports that regularly send snapshots of your metrics directly to your inbox (e.g. monthly executive summary)!
🔐 We are excited to announce our integration with
@HashiCorp
Vault as a premier partner on their marketplace!
Customers using HCP Vault can now leverage the secrets defined in Vault within their Rootly workflows safely and securely.
🔐 Launching the ability to set custom Google Doc permissions for your retrospectives!
Why? Provide security teams with greater control who can access sensitive data either automatically via workflows (e.g. only infosec team can view) or on the fly.
@nathenharvey
(of
@googlesre
) has the following
#SRE
advice for startups:
1. Don't view SRE as a non-functional requirement but instead an operational one.
2. Understand what your users need and work backwards. They are likely more tolerant of worse reliability early on.
For the 6th time in a row,
@rootlyhq
wins
#1
Best Support across Enterprise and Mid-Market as ranked by
@G2dotcom
for Incident Management.
Thank you to our customers that continue to trust us!
📈 We are excited to announce our
@getsentry
integration!
✅ Ingest Sentry alerts with all relevant metadata
✅ Create human-in-the-loop incidents from Sentry alerts
✅ Automatically create incidents when Sentry alerts exceed a defined threshold
We are excited to sponsor
@usenix
@SREcon
APAC 2023 here in Singapore!
Drop by the booth to jam on all things incident management or ask us about our private reliability leaders dinner we are hosting!
Thank you to
@G2dotcom
for recognizing us as a High Performer and Enterprise Leader in Incident Management for the sixth consecutive quarter in the Summer 2023 Report!
Our CEO
@jjrichardtang
shared this thank you note with customers on our blog:
🥳 Exciting update today: You can now assign multiple users to the same incident role!
This setting is customizable on a role-by-role basis so you have control over which of your roles allow multiple users.
Learn more and see the demo here:
To celebrate our
@G2dotcom
wins, we're dropping a fresh batch of Rootly swag and giving it away for FREE 🤩
🛍️ Head to and use the discount code G2WINNERS for two free items (free shipping included).
Ever wonder what an
#SLO
is, what it's for, and how it intersects with incident management?
PS. We are sponsoring
@SLOconf
on May 17th with our partners at
@nobl9inc
, it's free to register! Expect giveaways!
Illustration:
@MindsEyeCCF
#SRE
#DevOps
🔭 Excited to announce our partnership with
@sleuth_io
!
When failures occur, Sleuth’s native Rootly integration enables development teams to immediately pinpoint which specific changes caused those incidents.
🧵(1/2)
We're all smiles as we prep for a packed house at tonight's
@googlesre
+
@rootlyhq
meetup! Huge thanks to our friends at Google for such a warm welcome today 🥰
PS: See the photos for our attendee gifts—because you never know when an incident will strike 😉
If you've read the famous
@Google
SRE Book, don't miss this post on the Rootly blog from
@strongL0L
. He applies his 16+ years of experience at Google, Uber, Affirm and more to make the Google principles clearer and more actionable.
On the Rootly blog:
💀 We are renaming Postmortem to Retrospective within Rootly.
The term postmortem comes with the unwanted negative connotation of death and implies a single root cause.
Rather should be viewed as an opportunity to learn and continuously improve.
Slack forms create an easy, consistent intake for information during the incident management process. Now you can use Rootly to create your own completely custom forms in minutes - no code needed!
It might look too good to be true, but it's the real deal 😉 Here's a highly requested live demo of some of our new on-call features from
@AshleyOnCall
!
Watch on Loom:
When something breaks, your status page is likely the first place customers expect to see an update.
Save valuable time with our latest
@Statuspage
integration upgrade, which allows you to update component-specific status automatically, right from Slack.
We are proud to be sponsoring
@SREcon
Americas 2023 again next week from March 21-23 in Santa Clara.
Come say hi to the team at booth K9 🐶. Ask us about the private dinner we are hosting for reliability leaders!
We have a few spare tickets left if you
🔴 In the
@CircleCI
security incident of January 2023, critical CI/CD pipelines were compromised.
In this blog, we break down what happened and key reliability lessons we can all learn from.
Our Triage feature is officially live! Triage status ensures your investigation is tracked and automated before you officially start the incident—perfect for those murky problems that might not be true incidents.
📁 We’re excited to introduce audit logging capabilities to Rootly as part of our enterprise-readiness!
No more guessing “hmm…when was this change made?” or asking “who changed this?”.
🎉 A first for me... doing a video with a newly crowned Forbes 30 Under 30!
⭐️ I caught up with
@jjrichardtang
, Co-Founder and CEO of
@rootlyhq
. Rootly handles incident management which is ever so important given how complex issues can become when you've built out platforms
🎟️ We are excited to formally launch our integration and partnership with our friends at
@linear
!
Customers will be able to automatically create and track tickets such as incident action items in Linear and ensure they bi-directionally sync.
💬 Our
@WhatsApp
integration that plugs in seamlessly with workflows allows you to notify your responders via WhatsApp!
Especially helpful in non-North American regions where WhatsApp is the gold standard for communication and not SMS or
@SlackHQ
.
🎟 Automatically declare incidents from
@Jira
!
For teams that have existing processes that require issues to be reported directly in Jira first, but would still like to leverage Rootly to automatically spin up the necessary incident response process.
🐛 We are excited to launch our Debug Workflows capability!
› No more manually cross-checking if workflow conditions were met
› Drill down into specific workflows on a per incident basis
› Used for incidents, postmortems, action items, and alerts
We recently spoke with our customers at
@SurveyMonkey
about the new SEC reporting requirements and what they mean for teams responding to security incidents—even if you're not a public company. Check out the article on
@SecurToday
!
📜 We are excited to partner with our friends at
@NotionHQ
and be featured in their integration marketplace!
Customers can now enjoy automatically generated postmortems and incident timelines in Notion.
@glossgenius
and others are using it today!
👋 We are excited to sponsor
@SREcon
EMEA in beautiful Amsterdam from Oct 25-27 😊.
Come find us and learn more about
@rootlyhq
and pick up some sweet custom incident management-inspired legos 🧯!
We are thrilled to welcome Zarina Mamedaliyeva to the team as an Associate Account Executive 👋
Building genuine partnerships with customers and help them navigate the toughest problems stood out to us immediately 🍾.
SRECon EMEA is just around the corner. Don't miss
@AshleyOnCall
's lightning talk with tips for nailing your Status Page. Plus we're cooking up some fun booth merch you'll definitely want to check out 🎮 See you there!
@SREcon
👯 We are launching the ability to merge duplicate incidents together!
With everyone working concurrently, its not uncommon to run into duplicate entries.
Especially when the incident has a broad surface area potentially impacting multiple teams.
We're proud to be part of
#AsanaPartners
to help connect our customers to the world's most essential tools. Together with
@asana
, customers on Rootly can ensure incident action items are never lost or out of sync.
Check it out:
#SRE
#DevOps
#Productivity
Q: What do all these emojis have in common?📌💾⭐️💖😇🥳💃🐸💀🌈🐟
A: You can use any of them to automate actions like pinning events to the timeline, creating a task, or marking a message as a follow-up action item with your Rootly Slack integration!
Check out our latest
We are excited to sponsor this year's
@GremlinInc
#FailoverConf
on April 27th!
Expect all things
#SRE
,
#ChaosEngineering
, and incident management!
👋 Stop by our virtual booth for fun giveaways and if you sign up for a demo, coffee is on us ☕!
Should you be using Twitter (Xwitter?) to communicate with your customers during incidents? Do you really need a status page? Our new blog post breaks down the basics of incident communication channels.
🏘 Launching the ability to have multiple organizations of Rootly under the same roof and license!
› Use same Slack workspace across all Rootly orgs
› Switch between multiple organizations seamlessly
› Multiple domain support
But why?
🧵 (1/3)
🌟 Heading to
#KubeConEU
in Paris? Don't miss our top picks for SREs! Dive into AI, security, and Kubernetes with talks that promise to revamp your approach to reliability. Catch us at Rootly's booth (D36) for more insights! 🚀
#SRE
#CloudNative
⚡️ New Feature - Advanced Search ⚡️
Looking for a past
#incident
or
#postmortem
? Take your search beyond just incident title but look for services, key:value pairs, keywords, and more.
Try the most powerful search of any incident response solution free!
#SRE
#DevOps
#Software
If you're on call for Black Friday and feeling anxious, you're not alone! We're rooting for you and sending plenty of
#hugops
your way. No matter what this weekend throws at you, you can handle it! 💪
☁️ Managing your Rootly setup with Terraform by
@HashiCorp
is now easier than ever thanks to the Rootly Terraformer, which auto-generates Terraform files from your Rootly configuration—no need to manually code .tf files!
Learn more:
The first Reliability Roundtable of 2024 is happening Feb 13! Save your spot! We'll be talking about how the world's leading companies set their incident commanders up for success - think training, gamedays, and more.
Save your spot 👉
Thank you to
@freeshreeda
for taking the time to speak with our CEO & Co-founder
@jjrichardtang
about his childhood in Mongolia and how it shaped his outlook as a founder. If you want to get to know JJ a bit better, check out the piece on the
@mercury
blog!
"I find myself thinking about my childhood in Mongolia a lot as a founder. It was a tough time, and you couldn't pay me to live that again. But when I was living it, I enjoyed it.
Building a company isn't that different in some ways. Every day building Rootly is about tackling a
🏢 Customers using the self-hosted version of
@Atlassian
can integrate Rootly directly with
@Jira
and
@Confluence
.
No compromises for enterprises or organizations with strict regulatory requirements.
We are excited to sponsor the first-ever
@SLOconf
with our friends at
@nobl9inc
on May 17-20th!
✅ Designed for while you work
✅ SLO tracks from beginner to expert
✅ Memes, Puns, New friends
Register free here: .
#SRE
#DevOps
#Reliability
😵💫 When a provider goes down and takes you with them, it really sucks. But you're not totally helpless—here are some tips for when outages outside of your control affect your customers.
"By prioritizing simplicity and accessibility, Rootly ensures teams can navigate the platform seamlessly, even during the most stressful circumstances."
Thank you
@USATODAY
for highlighting how we're transforming enterprise incident response! 🙏
Your status page is an opportunity to extend your brand and voice to your customers during incidents. Our latest update allows you to add an extra level of polish by customizing the incident title displayed on your status page. 💅
Check it out!
If you break out in a cold sweat when you see your senior executives join the incident channel, this one's for you. Our latest blog post demystifies how to keep your execs happy during incidents:
✨ Accelerate response with Rootly AI!
Say goodbye to hassle and uncertainty with our cutting-edge AI-powered solutions. It’s like having a seasoned engineer on your team 24/7, ready with context and next steps.
Get proactive troubleshooting tips, accurate incident summaries,
Save the date! 📆 We're teaming up with
@harnessio
to bring you a webinar on December 12 diving into how how global enterprises are implementing their SRE programs.
RSVP here:
⚗️ Hot on the heels of our API and
@HashiCorp
Terraform provider, we are excited to launch our support for
@PulumiCorp
!
Engineering teams can now manage Rootly directly in code making distributed ownership of their service ownership even easier.