Rootly

My main use case for Rootly  is incident management, and I really appreciate how it enables a seamless Slack-based incident management process through its custom workflows and actions.

Rootly  is an all-in-one incident management product that not only helps with scheduling but also running planned maintenance windows, which I find very valuable.

Rootly has helped us standardize our incident management practices within Slack, which is our primary means of communication. It reduces context switching and lets operation engineers stay focused on actual issues rather than bouncing between multiple tabs trying to find the right one.

Slack-based workflow in Rootly helps my team during incidents by simplifying incident management and workflows, easing writing post-mortems, supporting planned maintenance, and offering valuable team support for migration and training. It's streamlining our incident management process overall, and having everything automated and flexible is extremely valuable through automations.

The best features Rootly offers are all-in-one incident management and an intuitive user-friendly GUI.

I find the user interface highly intuitive because it's very easy to customize and navigate, even for new users, hence making the learning curve very comfortable and smooth.

Rootly is very valuable, especially because it's very cost-effective. It's also very easy to use, and it has a very proactive and supportive customer support team.

I have seen a return on investment as Rootly has made interactions smoother and more efficient. The speed of Rootly makes my work more productive.

Rootly can be improved as it's slightly buggy for new features. However, this is not a detriment; while it does have some slight implications, the team listens to feedback and acts on it with incredible speed.

Although Rootly doesn't have as many integrations as I would like it to have, it integrates very well and seamlessly with other AWS  services I use.

I have been using Rootly for about two and a half years.

Rootly is very stable.

Rootly's scalability is impressive as it scales with my organization's growth, so it's very scalable.

Rootly team has been very proactive and extremely helpful regarding a specific bug or feature issue I've experienced. They're also quick to respond and offer a solution to us to resolve issues instantly. The learning curve and the initial setup might be time-consuming, but it is worth it.

Customer support for Rootly is very quick to respond to any of our queries and they offer instant solutions, so they are very helpful.

I previously used incident.io  and also PagerDuty.

I switched from incident.io  and PagerDuty to Rootly because of its pocket-friendly price. It's also very easy to learn and use, especially because of the online content. Additionally, support was one of the major issues I encountered, and the support of Rootly is very proactive and responsive, so it's able to handle a lot of issues instantly.

It was very easy to deploy Rootly in my environment.

My experience with the configuration process for Rootly was straightforward, but the initial setup was a bit time-consuming. However, thanks to Rootly team's significant assistance, it was made easy.

I have seen a return on investment as Rootly has made interactions smoother and more efficient. The speed of Rootly makes my work more productive. Rootly has helped us standardize our incident management practices within Slack, which is our primary means of communication.

My experience with pricing, setup cost, and licensing for Rootly has always been very competitive and affordable. The licensing cost is also very affordable and pocket-friendly.

Before choosing Rootly, I evaluated other options, including FireHydrant  and incident.io.

My advice for others looking into using Rootly is that it's a good tool because I use it for logging issues, which creates a separate space and a Slack channel for interacting with multiple stakeholders and team members across teams. Rootly has helped us standardize our incident management practice within Slack, which is a great means of communication. It also helps us to stay very focused, and it's easy to use and enables quick, reliable escalation when we need them.

Rootly is a good tool because I use it for logging issues, which creates a separate space and a Slack channel for interacting with multiple stakeholders and team members across teams. Rootly helps us to stay very focused, and it enables quick, reliable escalation when we need them.

I have additional thoughts about Rootly; I appreciate that everything is stored in one place and integrates easily with all our existing tools. The workflow feature enables the automation of many tasks, eliminating manual steps, helping ensure consistency of our processes, and allowing us to quickly respond to changes.

I would rate this review an 8 out of 10.

My main use case for Rootly  is configuring it to follow up on all incidents inside the company, especially because Farmatodo has an e-commerce platform and we definitely have a lot of technical issues, both internal and client-related.

The main use case for Rootly  was the visibility it provides, enabling us to create numerous dashboards with information related to the incident state, such as how many incidents we handled during a week or a month and the overall trends within the company.

Everyone in the company has access to Rootly via a public URL, so all people are aware of the number of incidents by each area, which I believe is the main use case.

Rootly helps me handle those issues by using a predefined template to define roles inside the workflow and utilizing a basic flow, which is very short in its lifecycle.

The most powerful feature of Rootly is its visibility; we can create a dashboard and integrate with Slack and Jira , for example, automating many steps in the follow-up process, which helps to centralize all communications around issues.

The best features Rootly offers include communication capabilities, particularly the integration with Slack, which stands out for me because it allows for very clean and direct communication with all clients and even with the resolution area.

The Slack integration helps my team by creating a specific resolution group and an automation channel inside Slack once an incident is opened in Rootly, ensuring that everyone knows when a new incident arises.

It is not just a notification; we create a group where all the relevant people can help solve the issue quickly.

The workflow capability of Rootly to create flows is another key feature for our operation, allowing us to establish specific rules for incidents in Jira  or manage the metrics we need during the incident lifecycle, effectively automating many manual processes.

Rootly has positively impacted my organization, and we have measured its impact by analyzing the number of incidents we handle over a period.

With the strategic approach of putting everyone in a Slack group to resolve incidents, we have reduced the percentage of incidents created in a month by thirty percent during the first three months of using Rootly.

Other positive outcomes include time savings and improvements in collaboration; the groups inside Slack enable people to communicate across different areas and work directly with client operations, creating synergy and a strong integration between teams.

The integration process could be easier, perhaps with the addition of AI to facilitate smoother integrations with other applications, especially since those who manage integrations often need technical knowledge about web services and single sign-on processes, which can be challenging for non-technical users.

I would like to see an easier way to integrate Rootly with other applications, and if we can pay for a larger package that includes more integrations, that would be better.

I have been using Rootly for almost two years in my last job, which was with Farmatodo, a retail company.

Currently, I do not see any improvements needed for Rootly; I believe I have mentioned the most important features it provides for our company.

I chose a rating of eight out of ten because applications always have room for improvement and can offer new features over time, and in my personal opinion, it is a realistic assessment.

I did not have the opportunity to work with the AI capabilities inside Rootly, so I cannot comment on that aspect.

Regarding the accuracy and reliability of Rootly's AI output, I provide the same response; I have never used the AI capabilities within Rootly.

Rootly is deployed in my organization on a public cloud, specifically as a tenant in a public organization, allowing all technical team members access to their dashboards and performance, showing how many incidents occur over time.

I am not sure which cloud provider we use because we purchased a tenant directly from Rootly.

The communication capabilities of Rootly are its strongest point, and I believe this feature significantly improves our work by centralizing communication channels. I provided a rating of eight out of ten for this review.

Rootly  is our central system for on-call and alert management. We route alerts from Alertmanager to Rootly , and after that, we route alerts from Rootly to different teams that are in charge of the services they maintain.

The best features Rootly offers include a very neat alert routine with quite precise rules and great entities. The precise rules and entities help me route alerts very specifically to the exact persons who are in charge and to rotate this person using on-call policies. This is implemented very comfortably in Rootly.

Rootly has positively impacted our organization because, in comparison to ObsGenie, the tool we used before Rootly, it is much more user-friendly, including the user interface and the whole approach to alerting and routing these alerts. Every maintainer is happy using Rootly after ObsGenie.

Since switching to Rootly, it has improved response time, and developers started really using the on-call system. Before, when we were using ObsGenie, developers did not like to use the on-call system, probably because of the user interface, as ObsGenie is not user friendly at all.

Regarding improvements for Rootly, first of all, it would be great to make comfortable maintenance mode, as it does not let me silence alerting comfortably. This is one of a very small list of points which were better in ObsGenie. The maintenance mode could be improved. The second point is a mobile application; if I have it on two devices, it does not send the notification to both of them. It sends the notification to only one.

It would also be great to improve the regular expression configuration in alert rules.

Regarding Rootly's AI capabilities, we had one incident when we lost alerting generally because Rootly crashed, and we did not like it. This happened because Rootly does not have a multi-cloud environment. I do not know how it is implemented currently, but it was a very bad experience.

I have used Rootly for about one year.

Rootly is stable.

Rootly's scalability is great; it goes under the hood and my colleagues and I as users do not think about it generally.

The customer support is quite good; I can write to Rootly specialists in Slack, and that is very useful.

We previously used ObsGenie, and we switched because ObsGenie is going out of service next year.

Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing which is not comfortable is the change process for adding new users and licenses for them. It is not comfortable, so we decided to avoid it.

My company does not have a business relationship with this vendor other than being a customer.

I have not seen a return on investment.

Regarding my experience with pricing, setup cost, and licensing, we got a license for one year. Generally, it is great and the price is great, and that is the reason we chose Rootly. The only thing which is not comfortable is the change process for adding new users and licenses for them. It is not comfortable, so we decided to avoid it.

Before choosing Rootly, we considered PagerDuty and iLert.

Rootly is a great solution for alerting, and I would recommend it. I gave this review a rating of 7.