Squadcast

My main use case for Squadcast  is to handle incident production incidents that we are facing in the applications, and to assign it to the users who are the relevant use case for that particular incident. We assign that alert to that user, monitor how the alert is acknowledged, when it was acknowledged, and the resolution part as well.

For instance, in recent days, we got an alert from Squadcast  that the CPU of one of our applications is experiencing a sudden spike, and the application was restarted. It was a production server, so we quickly analyzed what went wrong, and due to the incident, we were able to reduce the downtime of our application and solve it on time.

Squadcast helps us manage all our applications, monitor how each of our applications are working in production, and how we are triggering the alerts on time so that we can mitigate the risk. This is the major use case we use Squadcast for.

The best features Squadcast offers include reports and filtration, as well as the user summary which we get at the end of the week, daily, and monthly report. That is the best thing I can see in Squadcast.

The reports and filtration features help me analyze how many alerts were triggered, how much the SLA was hit, and how much actual time my team and I took to resolve that particular issue.

The notes and the takings section in Squadcast is really nice; we can tag the users there and notify them. Another feature is about adding predefined notes so that the assigned user can review them and take necessary actions if the service owner is not available.

Squadcast has positively impacted my organization by significantly limiting production incidents compared to before; after using Squadcast, we are much more aware of particular incidents happening with the production server. I do not have the exact numbers with me, but Squadcast has helped us reduce production incidents by around 25 to 30%.

One feature I think Squadcast must improve is the message quality and call quality we get; currently, the proper message is not being clearly heard on the calls we receive. Also, the acknowledge incident beep function does not work properly and it only works some of the time.

Call quality and response acknowledgment are the major things that would enhance my experience using Squadcast.

I have been using Squadcast for four and a half years.

Squadcast is stable.

As of now, I am not facing any issues regarding the scalability of Squadcast; it is handling the number of incidents we receive very well.

I have personally never reached out to Squadcast's customer team.

Earlier, we were managing incidents manually with an internal system, which presented major challenges we resolved by using Squadcast.

My experience with pricing, setup cost, and licensing was smooth, and the pricing was genuine.

Using Squadcast, we have reduced the number of employees needed to oversee production incidents, which has saved us money and especially time, and it has helped us maintain the confidence our customers have in us.

My experience with pricing, setup cost, and licensing was smooth, and the pricing was genuine.

I did not evaluate other options for Squadcast, but perhaps the management decided to do so.

I advise others looking into using Squadcast that it is a great tool and we can totally rely on Squadcast to trigger the alert on time. I would rate Squadcast a nine on a scale of one to ten. I choose nine because it is helping us manage production incidents proactively, which has helped the organization mitigate issues earlier so our clients are not hampered anymore, and I give it a nine, not a ten, because of the improvements I mentioned earlier.

My main use case for Squadcast  is for monitoring. In our team, we have a group of engineers and developers, so we usually schedule monitoring with Squadcast  turn by turn. Each person goes to Squadcast to monitor what is happening, take a look at the logs, information, and if there is anything that needs addressing, we do it.

It is mainly for monitoring and if necessary, taking action.

For our use case, Squadcast has what we needed; probably they could have more, but for our use case, we got what we need.

It depends on the project; I have worked with other companies that use other products too, but for this particular company where we use Squadcast, I think Squadcast was our main, our primary product for monitoring. So there was not a switch per se, but in other companies, I have worked with different, similar tools too.

I could say a lot about the best features Squadcast offers. In our use case, the features that stand out to me the most are the alerting and incident reporting because with that, we are able to know there is an issue. We go there, take a look, and if necessary, we adjust or we fix it.

I think Squadcast helps us to build a better product because of the alerting. Squadcast helped us build a better product by improving both response time and reliability.

Response time improved by up to 50%, and reliability improved too because we are able to identify something and fix it. That improves a lot too, let us say up to 60%, because our product became more scalable.

Squadcast does the job, especially alerting, reliability, and monitoring, so we can reliably use Squadcast for those things.

I think the areas where Squadcast can be improved include the alerting, the integration part, and especially the documentation while we are integrating.

The documentation and integration should be improved. I remember when we were working on the integration, the documentation was not great, and we found it difficult to understand what the document was saying in some parts. So I believe that both should be improved, especially the documentation.

I do not think there are any other improvements needed for Squadcast that I have not mentioned yet, or if there are, I do not remember for now.

Managing permissions and access control with Squadcast is not 100% straightforward; I remember our manager has to configure that to give access to each team member. I thought even that could be improved a little bit, but from my point of view, access control was pretty cool, and it was fine too because you are sure that you have the needed permission you need to do your job.

It is mainly for monitoring; that is how we use it.

Squadcast is stable.

I think Squadcast is scalable; I believe it is stable, scalable, and stable, but in our use case, we do not really go far in terms of scalability.

It was fine; but in our case, I do not think we have a lot of communication with customer support because it was not necessary. Most of the time, the integrations and everything was going well, so we did not have a reason to escalate any complaints. But for customer support, I would say it was good, although I do not have a lot of interaction with them personally.

This was more for evaluating options before choosing Squadcast.

It was not difficult for our team to onboard and start using Squadcast; I think it is mainly because the people involved are engineers who are used to that. So it was easy.

The learning curve for Squadcast for new team members is easy; I remember in my own case when I started using it, having not used it before, I did not find it difficult to use or even do the integration, so it was straightforward.

It was seamless how Squadcast integrates with our existing tools or systems, and we did not face any real challenges.

For collaboration during incidents, we use Slack for communication among the teams. Usually, in some cases when we receive an alert, someone responsible, like the developer, will call or most of the time go to the dashboard, take a look, investigate, and if necessary, create a ticket for that, so it depends. Mostly what we use in collaboration with Squadcast was Slack.

I think money was saved since we have seen a return on investment. Another thing is fewer employees are needed to do things because after the integration, a lot of work has been reduced; you just go there, check, monitor, and if action is needed, we take the action.

I did not do those things directly in terms of pricing, setup cost, and licensing; my manager handled those things, so I was not worried about this. My main concern was more like integration and monitoring, doing the main job, in terms of pricing, which was the responsibility of my manager and other team members.

I cannot say for sure if we purchased Squadcast through the AWS Marketplace  because it was our manager that handled that part. Our part is more like integration and monitoring using it.

On a scale of 1 to 10, I would say Squadcast deserves a seven, which is my overall review rating for the product.

My advice for others looking into using Squadcast is to go ahead and use it because it is a good product.

Squadcast is a good product for monitoring, alerting, and observation. So it is a good thing, and if you have a need for that, you can go for it.