IBM Event Automation enables businesses to accelerate their event-driven efforts. The event streams, event endpoint management and event processing capabilities help lay the foundation of an event-driven architecture for unlocking the value of events.
N/A
PagerDuty
Score 8.7 out of 10
N/A
PagerDuty is an IT alert and incident management application from the company of the same name in San Francisco.
IBM Event Streams is well suited for companies developing event driven Microservices. One of the biggest challenger with microservices is that your data gets distributed into little silos - event streaming (or better known as event sourcing) allows you to get a central source of truth in your event store. We are taking this approach with IBM Event Streams and it is well suited for building an event streaming / sourcing architecture.
I think PagerDuty works great for medical practices. I have used other platforms through other companies, and PagerDuty is by far the best platform. It is because of the different features it has to communicate to other staff members how the call is being handled. It is easy to learn how to use.
When getting a phone call, PagerDuty doesn't seem to allow acknowledgments of alerts through the phone, which it says it does. I constantly receive a message that it was updated by another person - when in reality, it wasn't.
Smarter notifications. If an alert was snoozed for a time, when it comes back, it sends out another alert. It should, I think, send a message asking if the alert is still an issue and give the option to close.
The product was very user friendly and extremely easy to get started with. The documentation is excellent and the free tier makes it very easy to get started with without having to make deep or long term financial commitments.
The UI is more complex than I would like. Part of the challenge is that most users use PagerDuty infrequently; I don't remember how I changed a policy last time. Another part of the challenge is that some users expect alerting to be a trivial feature, and are reluctant to invest any time in reading the documentation.
I met with the support team and they have deep technical and development understanding of the needs and the problems which IBM Event Streams addresses. If you are looking for a product backed by a highly technical support team then IBM Event Streams is probably the best choice. I was specifically impressed by the level of technical understanding my support team demonstrated.
PagerDuty is reliable and easy to set up. It gives an effective way to notify the team about critical incidents which results in a faster turnaround time on issues. users can customize their alerts rules based on their preferences. Overall it's effective and easy to use which adds great business value.
In Event Streams, applications send data by creating a message and sending it to a topic. To receive messages, applications subscribe to a topic. High availability and reliability. Event Streams offers a highly available and reliable Apache Kafka service running on IBM Cloud. Event Streams. Event Streams stores three replicas of your data to ensure the highest level of resilience across three availability zones.
I have not use the 2 technologies for as long as I have used PagerDuty but in my opinion PagerDuty makes things a lot easier. The other tools got the job done and got alerts out but PagerDuty just seemed to make the setup for on-call alert schedules and integrations easier than the others. This isn't to say the others are difficult, just that PagerDuty was slightly better. I also have noticed that more tools have options to integrate to PagerDuty over the other tools.
In using downstreams, the minimal features and the rate of releases were slow, makes us feel that there's no upgrades and other than that there's poor marketing of the product.
The adoption around the service is low, requires focused marketing.
Lack of visibility into topic depth , Monitoring capabilities