SolarWinds Observability SaaS
SolarWindsReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
793 reviews
from
and
External reviews are not included in the AWS star rating for the product.
SRM - much improved from STM
What do you like best about the product?
It integrates with the other Orion products. So that the alert engine and reporting is in the same interface.
What do you dislike about the product?
The migration from STM to SRM took some doing and wasn't an easy transition.
What problems is the product solving and how is that benefiting you?
Managing storage arrays. Knowing when the disk are off the array or are having any sort of issues.
Recommendations to others considering the product:
GIves complete view of the appstack. From the server down to the array and disk level. It will help in diagnoising the slowing of applications - is it the netwqork or the storage.
My job is, in equal parts, challenging, refreshing, interesting and frustrating
What do you like best about the product?
Simply awesome that I can easily track the bad boy at the office and what is he doing?
What do you dislike about the product?
there is always a dark side of every product, I am happy with everything whatever I have.
What problems is the product solving and how is that benefiting you?
We have a multitude of remote sites with very little bandwidth to spare. So finding who is taking up the bandwidth is a short period of time gets everyone back to work.
An excellent VM management tool. Highly recommended.
What do you like best about the product?
There are several things that Virtualisation manager offers and helps us every day. It brings all your VM’s in to one neat overview and can help you spot things a lot quicker. The alerting helps us greatly and the customisation is very helpful to our environment. It often highlights CPU overload, storage issues etc. and provides a further insight with the historical data. It can helps you see potential problems so you can keep your VM’s performing well.
What do you dislike about the product?
For smaller companies it’s not cheap and doesn’t really have a smaller scale version. It seems to rely on other solarwinds modules for maximum utilisation which can be daunting when you rack up the cost.
What problems is the product solving and how is that benefiting you?
It is simply helping us manage our VMs in a more efficient way. It keeps us on top of performance issues with alerts and historical information. It has most definitely prevented downtime and continues to impress.
Recommendations to others considering the product:
If cost isn’t too much of an issue then this is a great product especially if you are a larger firm. It really is a good tool for managing and giving further insight into your VM performance.
Overall a very good experience. Fits our need very well
What do you like best about the product?
Ability to monitor and optimise all virtual machines from one dashboard.
The dashboard UI is very easy to understand and navigate.
The dashboard UI is very easy to understand and navigate.
What do you dislike about the product?
The dashboard can at times seem very busy with information.
What problems is the product solving and how is that benefiting you?
As the IT world continues to go virtual this helps us to manage all of our virtual networks very well.
VMAN gives you insight
What do you like best about the product?
The ability to see high cpu and disk usage. It is also nice to see orphaned virtual machines.
What do you dislike about the product?
Nothing. Does what we need with vsphere.
What problems is the product solving and how is that benefiting you?
Finding small performance issues before they become a big deal.
NTA For ISP
What do you like best about the product?
NetFlow Analyzer has helped us reduce the time taken to isolate and contain threats like worms and virus attacks. It has also helped us to solve network incidents faster, and do better capacity planning
What do you dislike about the product?
Dashboard can be little alter will be helpfull for Data analyzer
What problems is the product solving and how is that benefiting you?
Better investment decisions
Managing and minimizing bandwidth costs
Network optimized for critical applications
Proactive detection and prevention of network incidents
Better capacity planning decisions
Ensuring minimum downtime and continuous availability
Better QoS and SLA management
Reinforced network security
Network fine tuned for optimum performance
Managing and minimizing bandwidth costs
Network optimized for critical applications
Proactive detection and prevention of network incidents
Better capacity planning decisions
Ensuring minimum downtime and continuous availability
Better QoS and SLA management
Reinforced network security
Network fine tuned for optimum performance
Good detailed product--at a price
What do you like best about the product?
Full range of features, alerting capabilities, the breath of supported devices
What do you dislike about the product?
The cost mostly, and their sales force--very, very pushy
What problems is the product solving and how is that benefiting you?
Instant notifications of downed devices, hardware or application issues--through a single interface
Recommendations to others considering the product:
If you have the budget, SW is a wonderful product. We don't use it for many of our devices (especially Cisco netflows) just because of the costs. If you use the app monitoring tools, it can give you great insight into your applications, ie VMware and Windows. And the Virtualization Manager is a great add-in with a deep-dive into your hypervisor, but again, it's oppressively expensive.
Master of Performance Recommendations and Monitoring
What do you like best about the product?
Proactive alerts helped me reduce downtime. PerfStack allows me to drag, drop, and overlay performance metrics from our systems data and multiple sources and data types on a single chart.
What do you dislike about the product?
I can't say any dislike about the product.
What problems is the product solving and how is that benefiting you?
Analyzed storage I/O performance and made forward plans according to these reports.
VMAN - Excellent Manager
What do you like best about the product?
I like the way it helps me optimize performance in vSphere. Also I can solve some issues with it. It works great as a capacity planning tool. Nowadays the capacity of the platforma is everything so having this tool helps me control expansions that i need in my infrastructure.
What do you dislike about the product?
I don't like the reports. It should have more opening with the customized reports. The predictive recommendations didn't work as planned. The alerts didn't have enugh information. Also didn't work with some applications in my VM
What problems is the product solving and how is that benefiting you?
Infrastructure. Virtualization clusters
Recommendations to others considering the product:
Its a great tool. Its a great capacity planning tool, needs some needs some improvement
Minimal setup, Reasonable cost, excellent utility
What do you like best about the product?
I like that with Loggly and some software(Winston, Fluentd) I can capture, interrogate and analyze my application's log output across a variety of deployment platforms and arrangements.
I can log both my development and live servers to the same system and either join or separate their content at will. The existing collection tools for Loggly are very strong and the setup for those tools is incredibly easy. Beyond that they offer the necessary endpoints and formats to receive logs from a wide variety of candidates.
Everything from system logs on various servers to application and routing logs from custom solutions is available.
Loggly essentially runs an Elastic Stack on behalf of the user, and having set up some similar solutions to test, I can declare with confidence that the time and energy saved by *not* rolling my own logging solution(and thereby having to maintain my maintenance tools) is beyond measure.
Support is quick and helpful within reason, I've had nothing resembling a technical difficult caused by failure on Loggly's part.
I can log both my development and live servers to the same system and either join or separate their content at will. The existing collection tools for Loggly are very strong and the setup for those tools is incredibly easy. Beyond that they offer the necessary endpoints and formats to receive logs from a wide variety of candidates.
Everything from system logs on various servers to application and routing logs from custom solutions is available.
Loggly essentially runs an Elastic Stack on behalf of the user, and having set up some similar solutions to test, I can declare with confidence that the time and energy saved by *not* rolling my own logging solution(and thereby having to maintain my maintenance tools) is beyond measure.
Support is quick and helpful within reason, I've had nothing resembling a technical difficult caused by failure on Loggly's part.
What do you dislike about the product?
Cos:, While I think the price is reasonable for the amount of work saved, and at $99 a month it pays for itself immediately, placing things like the LiveTail feature(emulating tail -f) at a $250 a month price point is disappointing. Features like that are excellent at every level and I'm simply never gonna convince my superiors to spend more on our log solution than on the live servers it monitors.
Finicky: It's a pain to get your log data arranged so that the various features of the system come into play correctly. I still periodically get unparsed log entries because 2 consecutive log entries had different object signatures for the same field(including single objects vs arrays).
Query Language: There are a few ways to filter/limit data for display and analysis with Loggly, but sometimes things don't work like you think they will and it's not always clear why. Somtimes a query for field:'2' finds objects with field=2, but sometimes it finds nothing whatsoever. When this happens there's always doubt as to whether you structured your query wrong or if there's literally no data meeting the criteria to be found.
Finicky: It's a pain to get your log data arranged so that the various features of the system come into play correctly. I still periodically get unparsed log entries because 2 consecutive log entries had different object signatures for the same field(including single objects vs arrays).
Query Language: There are a few ways to filter/limit data for display and analysis with Loggly, but sometimes things don't work like you think they will and it's not always clear why. Somtimes a query for field:'2' finds objects with field=2, but sometimes it finds nothing whatsoever. When this happens there's always doubt as to whether you structured your query wrong or if there's literally no data meeting the criteria to be found.
What problems is the product solving and how is that benefiting you?
Logs for server-side code are a right pain. Parsing and analyzing logs from a cluster of containers all outputting logs directly to console.log is a nightmare.
Simply put Loggly offers a robust system with simple inputs that allows you to funnel log data to a common, web-accessible location where it can be stored and interacted with in a number of robust ways. Before Loggly our hands were often tied if a user complaint fell into server code, there was simply not an easy way to parse logs from several servers, some of which may have been drained and terminated, and meaningfully determine what was going on.
Loggly gave me the ability to search and sort log data to find the source of problems.
Within a week of completing our integration of Loggly we were discovering the source and profile of bugs that had eluded us for 6 months.
With further adaptation of our web app to the new logging approach, we can start to see traffic patterns and analyse user behavior from the logs as well.
Lastly, Loggly prevents us from taking on a new maintenance and development project in order to analyze our main maintenance and development project. Loggly lets us break the potentially infinite chain of working on tools to work on tools.
Simply put Loggly offers a robust system with simple inputs that allows you to funnel log data to a common, web-accessible location where it can be stored and interacted with in a number of robust ways. Before Loggly our hands were often tied if a user complaint fell into server code, there was simply not an easy way to parse logs from several servers, some of which may have been drained and terminated, and meaningfully determine what was going on.
Loggly gave me the ability to search and sort log data to find the source of problems.
Within a week of completing our integration of Loggly we were discovering the source and profile of bugs that had eluded us for 6 months.
With further adaptation of our web app to the new logging approach, we can start to see traffic patterns and analyse user behavior from the logs as well.
Lastly, Loggly prevents us from taking on a new maintenance and development project in order to analyze our main maintenance and development project. Loggly lets us break the potentially infinite chain of working on tools to work on tools.
Recommendations to others considering the product:
Look at their integrations, determine if you can use their tools to build the sort of structure you need.
Spend some real dev time reducing log noise(we ran a search for "console.log" and removed all of them, then went back and started adding calls to our logger explicitly and carefully) and building in the necessary components to standardize the log entry process.
Look into Fluentd, it's excellent for routing, filtering and translating logs, it can help as an adapter to make sure Loggly gets what it needs from where it needs.
Spend some real dev time reducing log noise(we ran a search for "console.log" and removed all of them, then went back and started adding calls to our logger explicitly and carefully) and building in the necessary components to standardize the log entry process.
Look into Fluentd, it's excellent for routing, filtering and translating logs, it can help as an adapter to make sure Loggly gets what it needs from where it needs.
showing 581 - 590