Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of SolarWinds Loggly, and make your voice heard!
Entry-level set up fee?
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
With environments spanning on-premises, hybrid, and public cloud environments, IT operations and application teams are inundated with unrelated events, issues, and logs. Every outage or slowdown directly impacts the business, either in lost productivity or lost revenue. Issues must be diagnosed rapidly and resolved across all the dynamically changing components underpinning your heterogeneous web applications, services, and infrastructure.
SolarWinds® Loggly® is presented by the vendor as a cost-effective, hosted, and scalable full-stack, multi-source log management solution combining powerful search and analytics with comprehensive alerting, dashboarding, and reporting to proactively identify problems and significantly reduce Mean Time to Repair (MTTR).
- Supported: Highly responsive search at scale
- Supported: Interactive shareable dashboards
- Supported: Anomaly detection and alerts
- Supported: Dynamic Field Explorer™
- Supported: Rapidly pinpoint bottlenecks and failure points
- Supported: Collaborate with all stakeholders
- Supported: New shared agent that collects metrics and logs
- Supported: Add trace context to your logs
Visit https://www.youtube.com/watch?v=n0LwmA0p3AE to watch SolarWinds Loggly video.
|Small Businesses (1-50 employees)||25%|
|Mid-Size Companies (51-500 employees)||50%|
|Enterprises (more than 500 employees)||25%|
|Supported Languages||English, Spanish|
- Multiple sources for the logs, the amount of log sources available in Loggly is amazing! You can log from almost everything you can have running out there.
- The charts and dashboards, it's really easy to find and see the information you need to find problems you might be having without noticing.
- Centralization and aggregation, having multiple auto-scalable microservices running Loggly makes it really easy to centralize and aggregate all the data coming from these microservices.
- The volume pricing scheme is tricky, as usually, you don't need more features but just more volume. I think a big improvement would some per/GB/MB pricing scheme if the volume is so important and not the 200MB, 1GB, and 100GB per day jumps that forces you to be controlling how much you log because, usually in the case of an incident, you can have more than 1GB per day but then on a normal day volume can fall below 200MB.
- User management
- Intuitive step-by-step filtering by message attributes.
- Collapsing/extending log event data.
- Flexible log list presentation with selection of attributes to present.
- Graphical presentation of log events.
- Ability to filter out specific type of messages from the list to focus on important ones. Filter by example.
- Ability to send separate streams with cheaper cost and deeper storage, slower access times on demand only in specific cases.
It helps us to manage from a single point the access to that logs. Thus, we do not have to administer several tools.
- The search engine particularly quick.
- The ability to separate the access to various namespaces.
- Sometimes the filters for the requests fail and we do not know why
- We had issues with the SSO : the users had access to all the namespaces
- Easily takes sys-log connections from an app's standard output.
- Easy to navigate the user interface.
- Begins ingesting logs as soon as the connection to an app is made.
- Having to add users to Loggly after having created them in AppOptics could be improved.
- When search parameters are too specific Loggly often has a hard time filtering for what I'm looking for.
- While it's easy to navigate, the UI isn't very pretty.
- Detailed Information
- Easy enough to set up between our Azure environment and our on-prem.
- Customizable to our needs.
- No noticeable limitations to logging.
- There was once a difficult issue to assess where the logs were occurring/transferring far too often, costing us additional data charges in Azure. Would be nice to have built in alerts for this kind of abnormal behavior.
- Very fast searching capabilities.
- Easily handles huge volumes of logs.
- Searches are not always very intuitive.
- User management is not the best.
- Fast setup and deployment.
- Very customizable.
- Searching and sorting relevant data is intuitive.
- It's not free.
- Won't run stand-alone on-premises.
- Doesn't look as slick as some other alternatives.
- Keeps working!
- Fast searches.
- Easy to configure searches - you don't have to be an expert in RegExp...
- Not all searches are intuitive.
- We have to use a log aggregating device to ship our logs to Loggly as our network devices can not connect on an encrypted protocol. I would prefer if we could use some sort of VPN-based connector to ship logs securely.
- Sometimes when drilled down, it can be difficult to fully reset a search term to back all the way out of a drill down.
After I signed up I was repeatedly contacted by the pre-sales guy to asking if I was going to sign up - he couldn't find our account and questioned me multiple times, multiple times I provided the email address I used to sign up and he still couldn't find the account I was using - seemed a little unprofessional to me...
We are able to log different areas of the business, grouping systems and apps. this allows our searching and history tracing for logs to be much more effective.
- The collection tools for Loggly are very strong and the setup for those tools is incredibly easy.
- Support are fairly quick to respond and super helpful.
- Capturing and interrogating logs is easy across many deployments, platforms and devices.
- Sometimes queries don't work as you think they should.
- Getting data arranged so that everything comes to play is fiddly.
- Daily data limits can be a pain if you have a spike in logging.
The querying system could do with a better FAQ or guidance as when trying to run a structured query, sometimes no data is found even though you can definitely see that data by manual search.
- Vendor-hosted and fully managed.
- It performs reasonably well.
- User management is awful (deleted users are "renamed" and still appear in the system; no SSO).
- Pricing is too high, given the limited features (yes, it's cheaper than many alternatives but they offer much more functionality).
- UI feels clunky and dated.
- Only 2 customer tokens allowed - why?
- Pricing only based on basic ingestion/retention values - what about e.g. retaining ERROR logs for longer than DEBUG logs, or retaining PROD logs longer than DEV logs?
- Loggly is easy to integration. If you can make JSON from your logs you can use it. Adding it to a Python stack was trivial. Standard python logging, Loggly backend.
- Easy user management to allow people see view the logs.
- Documented API to retrieve and query the logs.
- The search interface. It remembers the last time window you chose. So you constantly are looking at the wrong logs.
- Everything is chunked on words. So searching for say an email address does not consistently work be it breaks firstname.lastname@example.org into someone, somewhere, com.
- filtering in the results is quite limited. Copy and paste is often broken by how the results are displayed.
- Finding the link to share a particular log is a process of frustration of finding just the right place to click to make the buttons appear.
- Aggregate logs from different sources.
- Easily sort and filter logs based on ad-hoc parameters.
- Create charts based on logs.
- Can be difficult to send logs to Loggly depending on your source and how much flexibility/control you have over your source system.
We monitor operating system, web server and application logs. This allows us to detect load peaks, issues in the application, attempted attacks or any other anomalies early.
- A key feature for me is drilling down logs, finding what I am looking for quickly.
- Creating graphs and dashboards for important information at a glance.
- Setting alarms in case something unexpected happens.
- Adding log sources is easy.
- Users that want to use Loggly to its full power need to invest some time.
- It's not very cheap.
- I struggled adding logs with dynamic names.
Loggly is also very good to monitor logs from many servers at once, a feature that I don't use but would recommend doing if applicable.
- Great search experience.
- Good buffer to handle one off data volumes exceeding plan limits.
- Awesome alert mechanism with filters & threshold.
- No proper key indexing for logs synced via default lambda blueprint.
- Tag based filtering disappear while looking nearby events.
- Ease of setup
- Intuitive UX
- Response times are fast
- The system seemed to lack the power (AI anomaly detection) of other offerings, but we were only on the free tier.
- No advanced features were evaluated.
* Aggregating all of our logs.
* Deriving metrics from our logs.
* Sending alerts to our team when those metrics change in some way that matters to us.
- Putting our logs in one place and making them searchable. We use AWS, and CloudWatch has always been a little frustrating in this regard (though it has gotten better recently).
- Deriving metrics from our logs. I think log-based metrics is such a good idea because your logs are the ultimate source for truth in regards to what the hell is going on inside your app. I have really loved the simplicity with which I can just count certain statements and call that a metric because just through the normal course of development certain log statements just naturally become a straightforward recording of an event having occurred.
- Alerts. I actually have a few complaints about email alerts, but just the way I was able to set them up so easily has been huge. Since we started using Loggly, there have been at least 3 bugs that Loggly exposed that were frankly very bad. And withoutt Loggly or without a user reporting them, we would have never known they were happening! This is stuff I tried to set up in CloudWatch in various ways, but because of my own ignorance or perhaps the complexity/limitations of CloudWatch (or the complexity of my stack?), I wasn't getting the information that I needed until I was able to just tell Loggly to send me an email whenever the word "error" showed up.
- I would love the ability to able to suppress a particular "event" instead of an entire alert. For example, sometimes an error is caught and handled but the word "error" is still printed to the logs. It would be nice if I could mark an event as "handled" without suppressing the entire alert for n minutes- if I do that then I would miss a real error that happened in that window. Also if I have my alerts set to run every minute checking the last five minutes, I will get 5 emails. It would be nice if there was some de-duplication. I have actually considered setting up webhooks into some API of my own instead of just emails to do this.
- I find the query language to be a little cumbersome. I suspect this is something you guys inherited from whatever index you use, but things like the __exists__ flag are strange. If I just type something into the field I am often surprised that I have to put quotation marks in (instead of it just searching for the term I supplied without any advanced features).
- Derived fields sometimes frustrate me, especially when I am using regex. I will sometimes create regexes that work in a test bed but do not work in Loggly. It is frustrating that I always have to match the beginning and the end of the string.
- The dashboards can be frustrating, especially when I am just trying to put a single number metric in a chart. I should be able to create a chart with multiple metrics: multiple charts with a single metric in each takes up a ton of space and limits the usability of the dashboard
I think the most useful dashboards are just numbers. I have some that show me error counts, average request times, etc. These have helped me identify when I am getting abnormal amounts of unauthorized errors, which helped me identify quickly that someone had used an incorrect CSV to email a bunch of users bad sign-up links. I have created a chart of my common API requests which helped me identify a bug in my client code that was essentially ddosing myself. Lastly, average request times and outliers (max request time) have helped me identify and fix slow queries.
- It can log whatever a developer decides to add information about.
- Zooming in on a particular time frame is helpful.
- The ability to tag/label events.
- Once the logging limit is exceeded, there are no logs period. Unexpectedly noisy logs often correlate with services misbehaving and potentially leading to disruption. An outage is an awful time to lose visibility into the entire system of apps. Some ways to bridge this gap would be appreciated.
- Filtering by tags is not intuitive in the web interface. You may believe that you are performing the same search and filter as last time since the tags entered are the same, however, this is often not the case. The reliable way to know that you have the same filter is to bookmark the URL. This lack of ease in usability results in devs using Loggly less than they could and implementing logs less effectively during development time (since they don't consider themselves likely to view them anyway).
- Would like to see a way to onboard our less experienced devs to using Loggly effectively.
- Creating alerts for specific events is very easy.
- Data visualizations are easy to configure; some are baked in.
- The price of Loggly is well below all other cloud logging tools I reviewed.
- Extra pre-baked dashboards would be useful.
- Searching for multiple conditions sometimes fails even when each of the fields can be found individually within a log message.
- Documentation to configure S3 archives needs to be updated to reflect the current Loggly GUI options.
- Simple search.
- Great visualization.
- Easy to use.
- Very practical.
- Maybe examples of advanced filtering.
- Visually represent event count via bar graphs.
- Statistical function for graphing medium and 95th percentile performance metrics.
- Fast return of search results.
- Supports log streaming via Fluent.
- The price model for the log ingestion rate is rigid and pushes for a higher usage commitment for companies with variable log generation due to weekly or monthly patterns.
- Does not support long term cold storage as an option for uploaded logs.
- Limited to no integration with other Solarwinds MSP product lines.
- Detecting logs messages for alerts
- Log drill-downs through attributes
- Bringing various sources together
- Understanding and adapting to specific formats
- Docker system ingesting
- Centralized logging: having logging for multiples sites (networks) all under one roof was really nice.
- Customer support: the customer support was outstanding when we had issues with our deployment of our first nxlog configuration.
- Ease of use: though there is a small learning curve, once conquered, Loggly becomes a very handy tool when needing to pull up past events or logs.
- nxlog: having to use another piece of software is a bummer
- nxlog configuration: the learning curve for nxlog is monumental and not very intuitive
- 1:1 Alerting: Loggly does not support this which is ultimately why my company is looking elsewhere. The alerting does not mesh well those who want login and logout alerts in real-time
- Makes viewing logs more readable.
- Allows us to pull logs from different sources.
- Search is good, when you know how to use it.
- Support is not the best, it's only email and they won't get on a remote session with you.
- Bit of a learning curve to get started.
- Had issues with getting CloudWatch logs, had to escalate to a higher support rep.