BugSnag vs. Elastic Observability

It's great for tracking bugs on your app. I don't think I can do anything else besides that...

Incentivized

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.

Incentivized

• The UI/UX is well designed. I have never been confused by any buttons/filters/settings, and everything is laid out in a neat and organized fashion.
• Setup was super easy. I didn't have to do anything but read the documentation, which was well written.
• The information captured by errors has everything I would need to debug an issue.

Incentivized

• Open source code base
• Community support
• Is fast in processing

Incentivized

• For really long bugs, it'd be nice if you hovered over the row and it expanded the text so you didn't have to click on the actual bug to view everything.
• It would be nice if there was a filter for grouping bugs instead of searching by their name.
• Honestly nothing else, I love 99% of Bugsnag.

Incentivized

• Difficult to setup/maintain
• Search pattern bar could be more user-friendly
• Premium subscription features are very expensive

Incentivized

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

Incentivized

• It has caught bugs on the spot, which allows us to quickly fix them.

Incentivized

• Cost management.
• Good customer increment.
• Time management.

Incentivized