TrustRadius Insights
Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. …
Starting at $79 per month/billed annually
View PricingOverview
What is SolarWinds Loggly?
Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.
Recent Reviews
Awards
Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards
Pricing
Standard
$79
Cloud
per month/billed annually
Pro
$159
Cloud
per month/billed annually
Enterprise
$279
Cloud
per month/billed annually
Entry-level set up fee?
- No setup fee
For the latest information on pricing, visithttps://www.loggly.com/plans-and-pricing
Offerings
- Free Trial
- Free/Freemium Version
- Premium Consulting/Integration Services
Product Details
- About
- Integrations
- Competitors
- Tech Details
- FAQs
What is SolarWinds Loggly?
Unified Log Analysis and Log Monitoring
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).
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).
SolarWinds Loggly Features
- 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
SolarWinds Loggly Screenshots
SolarWinds Loggly Integrations
- Mirantis Kubernetes Engine
- Node.js
- Linux
- Amazon S3
- Python
- NGiX
- Apache
SolarWinds Loggly Competitors
SolarWinds Loggly Technical Details
| Deployment Types | Software as a Service (SaaS), Cloud, or Web-Based |
|---|---|
| Operating Systems | Unspecified |
| Mobile Application | No |
| Supported Countries | All |
| Supported Languages | English, Spanish |
Frequently Asked Questions
Loggly is a cloud-based log management service provider. It does not require the use of proprietary software agents to collect log data. The service uses open source technologies, including ElasticSearch, Apache Lucene 4 and Apache Kafka.
Reviewers rate Usability highest, with a score of 7.8.
The most common users of SolarWinds Loggly are from Mid-sized Companies (51-1,000 employees).
SolarWinds Loggly Customer Size Distribution
| Consumers | 0% |
|---|---|
| Small Businesses (1-50 employees) | 25% |
| Mid-Size Companies (51-500 employees) | 50% |
| Enterprises (more than 500 employees) | 25% |
Comparisons
Compare with
Reviews and Ratings
(79)
Community Insights
TrustRadius Insights are summaries of user sentiment data from TrustRadius reviews and, when necessary, 3rd-party data sources. Have feedback on this content? Let us know!
- Business Problems Solved
- Pros
- Cons
- Recommendations
Loggly has proven to be an invaluable tool for a wide range of use cases, allowing users to effectively troubleshoot and prevent issues. With its syslog digest capabilities, users can sift through logs to identify the root cause of outages and errors, creating alerts for future prevention. By serving as an aggregation point for streaming logs from network access switches and core routers, Loggly efficiently manages large volumes of data. This makes it a valuable tool for support and engineering teams, providing alerting, monitoring, and issue triage solutions. Additionally, Loggly acts as a central repository for logs from PHP-based apps and servers, offering reports, analysis, and aggregation from different sources. Its flexibility extends to monitoring and debugging large-scale application platforms leveraging multiple microservices. By providing detailed information across different environments, Loggly enables efficient issue tracking and resolution. It also aids in meeting auditing requirements by logging network activity and providing proof of network monitoring. Furthermore, Loggly is widely used to troubleshoot systems, gain insights into performance and health, and visualize trends through its dashboard and alarm capabilities. Whether it's monitoring web traffic, capturing logs to identify security threats on internal and external websites, or monitoring integrations between websites and APIs, Loggly proves to be an essential tool in enhancing monitoring capabilities. Its ability to capture the behavior of software applications during development allows for easier investigation and setting up alerts to prevent service disruptions. Loggly is considered a modern platform for log-file analysis due to its compatibility with Linux systems, plaintext config files, utilization of web standards, and open-source friendly nature. Overall, Loggly plays a crucial role in troubleshooting server and application issues by providing effective solutions for resolving problems.
Intuitive and Easy to Use Interface: Users consistently praise Loggly's intuitive and easy-to-use interface, stating that it simplifies tasks and makes them easier to perform. The user-friendly design allows for quick navigation and access to log data, enhancing overall usability.
Highly Effective Alerting System: Many users appreciate the flexibility and effectiveness of Loggly's alerting system, finding it easy to set up alerts for specific events. Notifications can be received through email or Slack, ensuring that users stay informed about critical issues in their applications.
Comprehensive Integration Options: Reviewers value the extensive integration options provided by Loggly, which support a wide range of log sources and platforms. This feature enables users to consolidate logs from different sources into a centralized location for monitoring and analyzing data effectively.
Confusing User Interface: Many users have expressed frustration with Loggly's user interface, stating that it is confusing and difficult to navigate. They find it challenging to perform tasks effectively due to this issue, which negatively impacts their overall experience with the platform.
Cumbersome Query Language: Some users have found Loggly's query language to be cumbersome and unintuitive. They believe that using the query language adds unnecessary complexity to their log analysis process, making it more time-consuming and challenging to extract meaningful insights from their logs.
Difficulty in Sending Logs: Several users have encountered difficulties when trying to send logs to Loggly, particularly depending on the source system they are using and the level of control they have over it. This has caused inconvenience for these users as they face challenges in seamlessly integrating their logs into Loggly for effective analysis and monitoring.
Users commonly recommend considering alternatives and exploring other options in addition to Loggly. They suggest looking into different logging and monitoring solutions before making a decision.
Another common recommendation is to ensure the correct data is inputted and to tweak the data sending process if necessary. Users advise being careful with the data that is being sent to Loggly and making any necessary adjustments to improve the accuracy of the logs.
Integrations and tools are also mentioned as important factors to consider. Users suggest looking into the available integrations and using tools to build the desired structure for log management and analysis.
It is worth noting that some users recommend spending time reducing log noise and standardizing the log entry process. They emphasize the importance of streamlining the logs to avoid unnecessary clutter and confusion.
Additionally, users suggest using Fluentd as an adapter to ensure Loggly receives all the necessary information. They find it helpful for ensuring smooth communication between systems.
Having someone knowledgeable who can provide training on Loggly is also recommended by users. They believe that having assistance from an expert can greatly enhance the user experience.
Organizing requests and their results is another recommendation made by users. They find Loggly useful in this regard, as it helps them keep track of their requests and easily access the corresponding results.
While many users find Loggly to be a good initial solution, some mention that costs can increase as usage grows. It is advised to keep this in mind when considering long-term usage of the platform.
Overall, users describe Loggly as an excellent solution for debug log management and analysis. They appreciate its functionality, especially with the addition of the live-tail client. Some users compare Loggly to LogEntries and note that they find Loggly to have better polish.
Attribute Ratings
Reviews
(26-48 of 48)Companies can't remove reviews or game the system. Here's why
September 29, 2020
Loggly: we needed something fast and it worked well.
Loggly was used by a particular department/product line. It was used only at the free tier and by a team with minimal operations experience. The setup and configuration were very simple and straight-forward. It enabled centralized log management for a team that otherwise wouldn't have had this in place. Ease of use and free tier were the primary factors in the decision to use this service.
- 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.
September 29, 2020
Loggly is good
We are a small startup that makes training and marketing software. Our platform is our entire business, and we use Loggly for a few things:
* 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.
* 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
September 19, 2020
Use it if your devs can log effectively or you'll end up in a jam when you hit your cap
Loggly is one of the ways that allow us to possibly capture the behavior of our software applications both during development and when they are running live. Our Development Teams can add logging to their code and they and site reliability engineers can investigate when the information is logged. Incident management has set up some alerts against particular messages to possibly warn before potential service disruptions occur.
- 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.
September 16, 2020
Loggly's price and ease of deployment compared to many alternatives make it a no-brainer.
We use Loggly to satisfy a compliance requirement for centralized logging. Loggly is used on every PC across the whole organization to aggregate logs for auditing, analytic, and alert purposes. We also push logs from firewalls, switches, and wireless access points for network log visibility. Loggly helps identify patterns and anomalies that may otherwise be undetected.
- 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.
September 10, 2020
Great tool, love it!
We are using Loggly to troubleshoot our systems and getting better understanding about our overall performance and health. This tool helps us visualize simply trends by using its dashboard, tracks occurrences and even as monitoring tool by leveraging its alarms capabilities. As of today Loggly is being used in many LivePerson business units however some are using different tools like Kibana for example.
- Simple search.
- Great visualization.
- Easy to use.
- Very practical.
- Maybe examples of advanced filtering.
September 08, 2020
A great cloud-based managed log aggregation and search solution.
SolarWinds Loggly is used for centralized application logging, search, and graphing. It is used by Engineering, Quality Assurance, Tech Operations, Tech Support, and Services Org to quickly search and locate application errors, metadata and event count. Loggly built-in features enable trending and performance tracking of the full application stack.
- 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.
September 07, 2020
Loggly gets the job done, every time.
SolarWinds Loggly is used by the IT department. The chief focus is logging application errors and warnings to be able to detect problems with our system, as well as understand informational messages surrounding those warnings and errors.
- Detecting logs messages for alerts
- Log drill-downs through attributes
- Bringing various sources together
- Charts/metrics
- Understanding and adapting to specific formats
- Docker system ingesting
September 06, 2020
Testing Loggly for a New Centralized Logging Platform
My company was looking for a centralized logging platform so we tested with Loggly. It was being used by our IT team to monitor network devices as well as security and by our developers to monitor certain Windows event logs, as well as database logs.
- 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
September 06, 2020
Loggly: Pleasantly surprised!
SolarWinds Loggly is used by our IT Operations as well as the Engineering department. We use it to troubleshoot and monitor our application. It's used to notify the proper people for certain errors and issues.
- 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.
August 29, 2020
A startup engineer's review on Loggly
We used it to aggregate logs from all our servers, mostly for DevOps and debugging purposes. I didn't do the initial setup so I don't know how much effort it takes. But it sure is easy to maintain.
- Quick customer supports. I found an issue and the customer service provided some workarounds before the final fix.
- Easy HTTP integration. I integrated into my own Lambda function so I can process logs with my own logic.
- Speedy (majority of the time).
- Clean UI.
- Cooler Charts/Dashboard.
- More intelligent input prompts.
Loggly is being used across the support and engineering organization to provide us with an alerting, monitoring, and issue triage solution. It allows the company to have a more flexible approach to issue triage where we don't have to custom code a solution for every possible issue initially. We instrument the calls as the flow through the system so that we can look at the data after the fact. When we find common issues worth monitoring more actively we add alerts and charts to let us keep tighter tabs on the issue and if it makes sense we eventually code point solutions around that issue. With this approach we allow real-world issues to dictate where we spend our time with a "lazy load" approach to the solution.
- Quick filtering of data
- Effective and flexible alerting system
- Simple user interface
- The charting feature takes some time to figure out how to use effectively.
- It takes some time and effort to figure out best practices for how to use the product. It is actually so easy to use initially that it is easy to make poor decisions in logging schema.
July 14, 2020
Easy to setup.
We wanted to do log centralization for enterprise networking product.
- Capturing Django Logs
- Easy to install
- Capturing system logs
- The main concern was that the agent that installed the software was sending data to the cloud. We didn't know what all the data was being sent.
March 27, 2019
Loggly: a great Commercially-Oriented Log Shipping / Filter Pipeline, that will add value to your Company DevOps Department
While Loggly is not technically open-source, it is a modern platform for log-file analysis. Oftentimes, in our projects we will acquire competing DevOps stacks, in order to evaluate their effectiveness for us. Our criteria is usually very simple: 1. Does it work? 2.) Does it work on Linux? 3.) Does it use .config file format, or similar plaintext config files? (we generally try to stay away from XML-based file formats, or proprietary formats (think: binary), due to the overhead, and complexity that we feel does not work for us) 4.) is it modern? (i.e. if there is a UX component to the project, does it employ web-standards, such as NodeJS, HTML5, Angular, et. al) 5. It is open-source friendly? (i.e. is it built with Open Source tools, or is the Licensing less restrictive than Microsoft EULA?) Technical difficulty is almost never a concern for my team.
- Modern: Loggly is modern: Dashboards, realtime information and the ability speak many different data sources and environments makes it an attractive choice
- Configurability: Loggly gets log parsing right: by allowing you to in real time- filtering of log data, tagging and identifying data sources
- DevOps friendly: Loggly is very Componentized: You can have an instance of Loggly running that will Monitor your Linux instance, in addition to all of it's services, as an example. Also, you can start/stop Loggly, without affecting your other components
- Commodity: Loggly is protected by the company's need to convert Loggly into a retail product. While this is fine for the Company, it may limit individual developers from having immediate access to a product they would otherwise adopt. Therefore, Loggly really is geared towards Companies and Commercial Entities
- Feature creep: Loggly stands in competition with other packages that are open-sourced. And while this is not bad from a Commercial view point (every needs to eat, right?), it almost automatically makes it a 2nd place package, without adding in a killer feature that adds additional value to Developers and DevOps Analysts
- Parsing: Sometimes, when working with other packages, you get used to a configuration format. Loggly is not so dissimilar that it's hard to read / write, but it's not a one-to-one with say, Logstash. This is more of an annoyance than a real problem, and if you include putting your files into a Repo, then this is even less an annoyance.
March 22, 2019
A very good service but a little bit pricey
We tried Loggly in some of our servers for the monitoring and alerting of log files. We used it with Nginx on Ubuntu Linux. The problem was that it was too painful to monitor logs and find the necessary information without an app because logs are huge and you must log in every day with SSH and inspect all logs
- Implementation. The implementation was pretty straight forward and worked very well. Also, it has a Laravel package.
- Alerting. Creating alerts with emails or Slack was a piece of cake.
- Filtering. Filter your logs was very easy and fast.
- UI is very simple and easy to use.
- Price. If you compare it to other similar apps it is very pricey. Especially for storage and user limitations.
- Amazon S3 archiving is only for the pro package. Other apps give it for free.
March 11, 2019
Loggly simply works
We use Loggly to monitor and secure our servers across our portfolio of satellite setups. It is used primarily to manage the typical maintenance of our systems, but has also evolved to become part of our security workflow.
- Flexible dashboards
- Ease of initial installation
- Live feed is useful and allows for quick exploration of incoming issues
- Initial setup of dashboards has a steep learning curve.
- I find help and guides to be lacking.
- I find the subscription offers are not accomodating for all use cases, and should be finer grained to allow for a better price/need match.
March 06, 2019
Perfect for home usage
I use Loggly at my home for monitoring the logs from around 10 services. It saves me time by reviewing logs online. Loggly also helped me solve a problem with one of my services I wasn't even aware of. Currently, Loggly works on one of my machines which produces around 500 logs daily so I can't say much about performance. Search windows recommend names of the indexed fields so you don't have to know the structure by heart. You can easily install file monitoring by running a prepared script from SolarWinds, which will update your rsyslog configuration, which is nice. In my current company, we use a similar tool 'Kibana ' and I don't see much differences.
- Runs in the cloud. You don't have to install it on premise.
- Has a prepared script for rsyslog updates. You don't have to know your rsyslog configuration, the prepared script will do all the work for you.
- I can't change the order of the tabs (saved searches).
February 28, 2019
Loggly Review
I used it for application logging only. It has addressed the areas that I needed it to and has all of the functionality required for the simple use I require it for.
- It is a cheap option which suits me well.
- It is cross-platform.
- Improvements on the JavaScript side.
- Filters should not log duplicate errors.
- Chat should provide immediate answers for free users.
February 27, 2019
Loggly Review
It is being used by the IT team to log APIs and service logs.
- It provides a flexible dashboard where we can aggregate and surface meaningful data for our technical team.
- We can search for logs.
- They provide prompt support and were helpful.
- Searching for logs can be difficult at times.
- It is not very intuitive and takes some time to learn before getting used to it.
February 26, 2019
Loggly is quick, easy, and full-featured at a reasonable price
Loggly is used to easily manage centralized logging needs in a best-practice way for a new development effort. Best case scenario, it begins to be used across the company to ease the problem of debugging and proactively monitoring installations for any issues, or to implement improvements and fixes before they become a fire to be put out.
- JSON parsing.
- Quick start-up time.
- Filtering and Alerts.
- Libraries to support logging from different places, e.g. java. We found one that works for us, but many are not very well maintained, or not full featured. It'd be nice if Loggly actually created and maintained their own instead of referring to others' creations.
- Supporting permissions on Live Tail log viewing.
January 11, 2019
A solid solution to log overload
Our organization uses Loggly both for our own internal systems as well as for the websites and services that we provide our clients. We funnel all log-type output from every conceivable place into Loggly, and it allows us to search, filter, correlate events, and receive alerts when bad things start to happen. It's become one of our most valuable troubleshooting tools, as well as an increasingly-preventative measure before or as problems arise.
- Collects logs from pretty much any place you can imagine. Many applications have Loggly integration, many programming languages have Loggly libraries, and pushing other logs into Loggly is easily scriptable and automatable.
- Searching and filtering is incredibly deep, and often very intuitive. You can drill down through any data set, filtering or searching on any value within that data set.
- Saved graphs and dashboards are a great way to visualize what's happening without having to read through each log entry.
- Loggly has a significant learning curve to figure out how to use it. At first, it can be daunting staring at a collection of thousands and thousands of logs wondering how you're supposed to make sense of any of it. The initial onboarding and training experience could be better in my opinion.
- Loggly's user interface is adequate but does have some room for improvement in my opinion. It is a collection of tools which work well on their own, and which do tie into each other in many ways, but it doesn't feel like there is a good, cohesive, overall workflow to the application. This is a bit vague, but I feel like it needs more of a concept of a "user dashboard" when you log in providing an overview of things like important/flagged recent log entries, detected anomalies, recently tripped alerts, perhaps links to your favorite or most common/recent graph dashboards.
- There is always room for more integrations and more ways to pull/collect logs. I would love to see Loggly offer a service which periodically pulls updated logs via SFTP, without the need for me to set up an intermediate shell script on a timer.
July 06, 2018
Loggly made my logging simple & fast
Loggly is being used by our technical team to manage the tracks of our cloud infrastructure. It provides real-time monitoring of all our systems and helps us to figure out errors and bugs.
- Free Plan suitable for majority of Startups
- Easy to integrate
- Majority of Platforms and services are supported
- Live debugging mode
- Easy dashboard and search
- Haven't found much yet!
April 20, 2017
Best cloud service logger
[It's used as a] cloud logger for cloud service, so we can have one platform to check all logs from different servers. Loggly also provides an alert service, so you can define when you can get alerts based on your customized log query.
- easy to integrate into your code
- easy to query log
- can customize log query as alert
September 06, 2016
Loggly. A great solution.
We use Loggly to aggregate all of our log files from all of our different servers, allowing us to have one location where we can go to see everything that is happening. It is being used primarily by the operations department. It allows us to have a centralized place that we don't have to manage that stores and files away all of our logs.
- Centralized location of logs
- Great graphs
- Detailed information
- Steeper learning curve
- Many other competitors