FAQs

Why do I need Loggly when I already have grep/awk/sed/logstash?
Loggly can easily index terabytes of data and return query results to you within seconds, which just isn’t possible with grep. We offer built-in point-and-click filtering and grouping, flexible event presentation (including grid), automated parsing, alerting, automatically saved workspaces so you never lose work and more. Because Loggly indexes log events in both full-text and by-field formats, you get great field precision that isn’t possible without complicated awk/sed expressions. Open source tools are great if you need only basic searching capabilities and you have the resources to manage/update the installation. The point is that if you value your time in terms of the speed of troubleshooting operational problems and the time to develop and manage a logging solution then Loggly is a great value.
How does Loggly compare to other cloud-based log management tools?
If you operate a cloud-based business, your logs are the key to keeping your applications healthy and generating revenue. The Loggly service takes a new approach to log management: navigable log summaries as the entry point to log analysis, coupled with powerful search and visualization.

A Bird’s-Eye View of Your Logs

Loggly is the only log management solution that reads and summarizes your logs as they are ingested, turning them into navigable summaries. As a result, you always have a bird’s-eye view of what’s happening across distributed environments and know where to dive into the details. You can quickly find the sources of the problems you know about and explore questions that you didn’t know to ask, because those are the issues that often hurt the most.

Data-Guided Search

Until now, finding operational problems has always started with guesswork followed by hard work. You make a hypothesis about the most likely trouble spots and then search your logs for clues by trial and error. Loggly is different because it crunches through your logs for you and lets your data guide you on where to look for answers.

Agent-free Deployment

Loggly collects your log data using existing open standards like syslog and HTTP instead of forcing you to install proprietary collection agents on every machine.

What’s the difference between Loggly and an Application Performance Management system?
Companies and teams that create cloud-based applications and services like e-commerce, advertising, gaming, or mobile apps know that the best way to deliver a great user experience is to know what's going on with their applications and why. APM solutions provide valuable insights into application performance. Log management solutions provide complementary metrics based on log data along with deep-dive capabilities so that you can answer the "why" questions.

Many companies start out with their own in-house log management system. But as the business grows, the complexity of scaling the log management solution and the need for additional functionality quickly outpaces the cost of Loggly.
What kind of logs can I send? How do I get them to Loggly?
If it logs, it can log to Loggly. We’ll take any text-based data, including logs from Ruby, Java, Python, C/C++, Javascript, PHP, Apache server, Nginx, Tomcat, MySQL, syslog-ng, rsyslog, logstash, nxlog, Snare, routers, switches, and more. Logs can be sent over Syslog TCP, Syslog UDP, Syslog TCP w/ TLS, or HTTP/S. Any system or process that has access to the Internet can forward log data. For systems that don’t have Internet access, you can simply set up a proxy to forward the logs.
What platforms does Loggly work with?
If your platform has access to the Internet, it’s possible to log to Loggly. We have logs coming from all flavors of Linux, Windows, mobile devices, and client applications. We’ve also worked with various PaaS providers, such as Heroku, Engine Yard, and others to get your logs drained and captured in Loggly.
Is Loggly use limited to applications running on Amazon Web Services?
Not at all. Logs can come from anywhere, whether it’s your own data center, a public cloud, a colocation facility, a user’s browser or mobile phone, etc.
Do you have a collector agent that I need to install?
No, Loggly is completely agent-free. We work with existing standards like syslog and HTTP so you can use the software you already have.
How much bandwidth will I need to send events to Loggly?
It depends on how much log data you have, but a good rule of thumb is that sending 100GB of log data per day would use around 10Mbps of bandwidth.
How long does it take before an event sent to Loggly shows up in my account? How real-time are you?
Log events will generally show up within 15 seconds. We consider ourselves near-real-time.
Does Loggly have an API?
Yes indeed. Key Loggly functions are available via the web interface or via our RESTful API. You can use the API to make Loggly an integral part of your operations monitoring and management function. Read more about Loggly’s API on our handy dandy wiki. Or, take advantage of the work we have already done on an out-of-the-box integration with PagerDuty.
When does Loggly parse logs, and how?
Loggly parses many standard event types during the pre-index analysis phase, immediately after it ingests your log data. You can view the link of standard event types here. The parsing process identifies different fields depending on the type of log. For example, an Apache log would include parsing on referring URL and status code, while a JSON log would include parsing on serialized data and common key-value pairs.
What browsers does Loggly support?
Loggly works with all modern browsers including Chrome, Firefox, Internet Explorer 10+, and Safari.
Top