Airbrake vs. Splunk Observability Cloud

Airbrake is very good at what it does, I don’t really have any criticism at all on that front. It’s less well-suited when bugfixing goes beyond the immediate error and means looking at a lot of context (particularly asynchronous context) like logs.

Incentivized

Its great if you need real-time visibility across complex or regulated environments. Also strong for hybrid or multi-cloud setups where uptime, observability and fast IR are required. It’s probably overkill for smaller teams or environments that don’t have constant changes or compliance reporting needs. It's expensive and has a steep learning curve. Also, in my opinion, do not get yourself into a consumption based model. Costs can certainly get out of control quickly.

Incentivized

• Integration with most of languages and frameworks as well support via existing logging configs.
• Aggregations on occurrences which helps to understand and analyse issues better.
• Web UI displays all error related parameters which I never could have figured out in manual debugging.

• The first one is its Kubernetes container monitoring.
• I really like this features because as we know how much K8s is vast and to manually monitor each part of the Kubernetes it takes so much time but Splunk Observability Cloud makes it easier. And even once we integrate K8s with Splunk Observability Cloud it gives us some prebuilt dashboards which gives holistic view of our Cluster and its nodes, pods, etc.
• The dashbaord feature of Splunk Observability Cloud, it gives us full flexibility to customize our dashboard with a wide range of predefined chart types.
• Now it also supports OTEL, which is a plus point for observability. As now everyone is moving towards Otel and in current market there are only few tools who supports OTEL based integrations, Splunk Observability Cloud is one out of them.

Incentivized

• We use Airbrake in conjunction with OpsGenie, but I feel like there could be more room for integration between the two.
• I think it would also be nice if there was a GitHub integration that would comment on recently merged error-prone PRs, currently, we need to dig into the error to find the commit.
• Generally, more integrations would be nice as people often forget about Airbrake when they are stressed out about an issue.

Incentivized

• You can use table-like functionality to generate dashboards, but these queries are heavy on the system.
• It could be easier to give insight into what type of line parsing is used for specific documents in a company-managed environment and/or show ways to gain the insights needed.
• I would like to see ways to anonymize specific data for shared reports without pre-formatting this in a dashboard on which reports could be based.

Incentivized

Good: Stable system with low error rate Easy to use for simple use cases Bad: UI is not very clear for complex usage Mobile view (when logged in from phone) is bad No library for .net

Incentivized

When there is an issue, it’s a win if one can easily identify the root cause. To do the same, it should allow the user to dig deep with multiple data points and compare the data and identify the anomaly. In this use case, it’s good to drive from Splunk 011y.

Incentivized

Splunk support is very quick and efficient. Pre-sale specialists are very skilled and available.

Incentivized

Follow a training before starting.

Incentivized

I love to use Airbrake and New Relic in conjunction. New Relic has better metrics and data that you can really dig into (especially for optimizations), but the error part has always been kinda meh. I fee like Airbrake has done an awesome job at this

Splunk Infrastructure Monitoring provides far superior options for anybody using a complex hybrid multi-cloud environment and allows both your SOC and NOC to work together on the same data while driving their own insights. We found other products are still in the old world view of servers and agents residing together within a single data centre, but modern apps are no longer like this.

Incentivized

• Hugely reduced frontend errors in devices we don’t often test: means more conversions and sales
• Lets us know immediately when there is an error: shorter error durations also means higher sales
• Ultimately once we’ve solved all the most common bugs: more time for developers to focus on other things

Incentivized

• Significantly reduced the MTTR (Mean Time To Recovery), which in turn has improved the end-user experience tremendously.
• Meets compliance requirements of security policies, audit, regulation, and forensics.
• Helps us to track/manage the resource usage on our cloud instances which has a direct implication on the recurring cost.

Incentivized