Try our new research platform with insights from 80,000+ expert users

Avada Software Infrared360 vs Sumo Logic Observability comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Jul 24, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Avada Software Infrared360
Ranking in Application Performance Monitoring (APM) and Observability
73rd
Average Rating
8.8
Number of Reviews
13
Ranking in other categories
Business Activity Monitoring (4th), Message Oriented Middleware (MOM) (12th), Server Monitoring (43rd)
Sumo Logic Observability
Ranking in Application Performance Monitoring (APM) and Observability
23rd
Average Rating
7.8
Reviews Sentiment
7.2
Number of Reviews
6
Ranking in other categories
Cloud Monitoring Software (17th), AIOps (11th)
 

Mindshare comparison

As of August 2025, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Avada Software Infrared360 is 0.1%, up from 0.1% compared to the previous year. The mindshare of Sumo Logic Observability is 0.3%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

WK
Role-based access to queues, giving us more insights into problems
* We now have the possibility of getting a central perspective on all tenants. * We have defined access roles for developers. Therefore, they can 'read in' their queues on the development and testing stages. With special roles, they may also write. This improves our development and testing cycle. * For operative systems, we have restricted the access. Still, selected people can react if something is happening in the various BOQs.
Shamshir Nangla - PeerSpot reviewer
Getting up and running is easy, even for a newbie but management of searches definitely needs improvement
Operational effectiveness with regards to when there's an issue, when there's a reactive issue, people are able to, or as well as proactively, actually, because we use their PagerDuty integrations. We use queries in Sumo Logic to trigger alerts based on logging. That allows us to proactively identify issues as they're happening. With those same alerts, obviously, with that platform, you can use it to reactively start looking at troubleshooting issues as they're happening right then and there or incidents. So it's been very, very good for alerting and for troubleshooting issues. For predicting issues before they happen, it is not very good. They have a feature called anomaly detection, but I think it's quite premature compared to other stuff out there. So it's good for alerts and for troubleshooting operational effectiveness. When your operations are down or segregated, it's perfect because it will help you diagnose the issues.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Monitoring that ties into our incident management system"
"It's what we use for monitoring our MQ system, so the features that they provide are just really, really good."
"It has role-based access to queues, giving us more insights into problems."
"The administration piece makes it very easy to do MQ administration. It gives us a lot more flexibility and capabilities."
"We have easily created use case testing harnesses for specific flows that incorporate various message types."
"It allows non-technical users to inspect their individual components within the total infrastructure without disturbing other components and without bothering the technical teams."
"Alerting and consistency are key. We have different tiers with log collectors, and continuous querying provides near-real-time updates. It's almost like instantly when something happens, like pending transactions or error fees. This helps reduce incident resolution time compared to waiting for thresholds on other platforms. We can continue logging in with them seamlessly and quickly get into action."
"The product is easy to learn."
"Sumo Logic Observability presents a range of valuable features, including well-crafted dashboards and a diverse selection of helpful apps. However, personally, I don't hold a favorable opinion of the solution. While I don't struggle with writing queries, my main difficulty lies in recruiting competent individuals and ensuring their proficiency in utilizing the solution. This often leads to additional challenges and complexities. From my perspective, when compared to Microsoft Sentinel or even Splunk, Sumo Logic Observability has a steeper learning curve. One contributing factor to this disparity is the solution's long existence in the market compared to Synlogic. Nevertheless, I acknowledge that there are capable and knowledgeable professionals employed at Sumo Logic Observability. The effectiveness of the solution largely depends on how it is integrated into your internal operations and environment. Its utility and benefits can vary significantly. It is worth noting that organizations like the NSA and, I believe, the CIA used it in the past, primarily for rapidly searching and analyzing large volumes of data. To leverage its capabilities effectively, you must determine how to tailor it to your specific needs."
"I have not seen any stability issues in the product."
"We use queries in Sumo Logic to trigger alerts based on logging. That allows us to proactively identify issues as they're happening."
"The solution allows multiple groups to converge on a unified platform, allowing for different utilization by various teams."
 

Cons

"One area where they could improve is with their documentation. Some sections are not up to date with new release information and providing additional samples in some areas would be very helpful."
"We desire a dashboard that could accumulate BOQ lengths per tenant on one screen for all tenants."
"The UI can be cumbersome - but we are still using the Viper interface and we have not had the time to check out the Alloy interface which is supposed to be much improved."
"The user interface could be sexier and more ergonomic. The competing products have similar problems."
"We are still working with the FTE/MFT subscription monitoring and reporting functionality. That is an area in which we would like to see further development taking place."
"Some of the graphics in the interface could be improved. It's pretty basic. Some interfaces are not up to what you're used to seeing on other, more Windows-like tools."
"The speed of queries could be improved. When using more advanced functions, especially with large datasets like the 90-day log retention we had, queries could be slow, sometimes taking up to five minutes."
"SearchUI.exe is a bit clunky in the product, making it an area where the product needs improvements."
"Documentation could be better. While it's generally good, sometimes finding what you need requires extensive searching. It's not always clear where to look for specific things."
"Fine-grained data can be quite frustrating to work with and should be made easier."
"Implementing a more streamlined enrichment process, and conceptualizing the observability data collection as an ETL pipeline would be helpful."
 

Pricing and Cost Advice

"Because the licensing is at the QMGR level, you need to have at least a small cushion of licenses for occasional enterprise needs."
"Avada Software's licensing metric is very good because the license fees are based on the number of connections (which have not increased for us very much over the years) rather than the CPU processing power (which increases significantly whenever our hardware is upgraded) or the number of users (which has increased for us a lot since our original purchase)."
"Start small, then increase licensing later as per your demand."
"Our internal budget calculation model incorporates the pricing per endpoint for any new projects. However, as our footprint for distributed queue managers shrinks as part of our shared middleware hub deployment, the initial licensing and support costs have been reduced over the last five years."
"Now, they’re not charging by ingests anymore. You should expect the price to be a bit of an unknown and to basically increase as the business increases."
"I started on the free tier to try it out, but because of our usage, we're now paying for it."
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
35%
Manufacturing Company
9%
Printing Company
8%
Performing Arts
6%
Computer Software Company
14%
Financial Services Firm
13%
Manufacturing Company
8%
Transportation Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Questions from the Community

Ask a question
Earn 20 points
What needs improvement with Sumo Logic Observability?
The speed of queries could be improved. When using more advanced functions, especially with large datasets like the 90-day log retention we had, queries could be slow, sometimes taking up to five m...
What is your primary use case for Sumo Logic Observability?
We used it for log observability – log aggregation specifically.
 

Also Known As

Infrared360
No data available
 

Overview

 

Sample Customers

USBank, Southwest Airlines, Visiting Nurse Services of New York, Aon Hewitt, Parker Hannifin,  Cantonal Bank of Zurich (ZKB), Hagemeyer NA, and many others
Information Not Available
Find out what your peers are saying about Avada Software Infrared360 vs. Sumo Logic Observability and other solutions. Updated: July 2025.
865,384 professionals have used our research since 2012.