Elastic Observability, from Elastic, the makers of Elasticsearch, is a solution that aims to bring logs, metrics, and APM based on the former Opbeat (acquired by Elastic in 2017) traces together at scale in a single stack so users can monitor and react to events happening anywhere in an IT environment. It's free and open to start, and adds the Logs, Metrics, APM (formerly Opbeat), and Uptime modules to the Elastic (ELK) Stack.
N/A
PagerDuty
Score 8.6 out of 10
N/A
PagerDuty, Inc. (NYSE:PD) provides digital operations management. Serving organizations of all sizes, PagerDuty aims to help them deliver a perfect digital experience to their customers, every time.
We can use this Elastic Observability in our business problems such as Creating internal/operational efficiencies issues, customer relations/service, and business process outcomes issues. This product has a lot of features for the above problems. But this product may be having some issues when charting purposes. But it can adjust for that purpose.
PagerDuty is well-suited for teams or companies that need immediate response, such as production outages, server downtime, failed deployments, API failures, or critical infrastructure alerts. For example, if any company is doing work that requires immediate attention to any problem that arises due to a delay, it means the company loses money; PagerDuty would be the best fit for that company.
PagerDuty feels like something you can absolutely rely on... because in the rarest case where an alert is not acknowledged by the relevant agent, the alert automatically is escalated to our TL, which saves any possible errors or misses.
In terms of integration, I would rate it a 9.4 as it's absolutely seamless with Microsoft Teams or emails, ultimately resulting in a reduction of errors in work, which I greatly appreciate about PagerDuty.
In some cases, when an account requires input from multiple agents, PagerDuty makes sure to notify each of the relevant ones.
Other than this, sometimes when we have new joinings, it becomes easy for us to train them because every alert or response is recorded or logged. Because of this feature, we are able to check our past actions as well, so that a good feature about PagerDuty.
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.
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.
Splunk is a very good product but the licensing costs are high; we utilise the best of both worlds by using both products for slightly different purposes. We put the voluminous data with simple use cases in Elastic where it doesn't cost too much and can be searched quickly while putting the less voluminous data with more complex use cases in Splunk so we can take advantage of Splunk's very comprehensive but often much slower SPL search query language
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.
![Screenshot of Similar Incidents [Apple iPad], Open Incidents [iPhone 8], On-Call Schedule Menu [Apple Watch])](https://media.trustradius.com/product-screenshots/kf/M5/L6SIK3HGD31M.png)
