StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Log Management
  4. Log Management
  5. Elasticsearch vs Loggly

Elasticsearch vs Loggly

OverviewDecisionsComparisonAlternatives

Overview

Loggly
Loggly
Stacks269
Followers304
Votes168
Elasticsearch
Elasticsearch
Stacks35.5K
Followers27.1K
Votes1.6K

Elasticsearch vs Loggly: What are the differences?

  1. 1. Scalability and Performance: Elasticsearch is designed for horizontal scalability and can handle large amounts of data and traffic. It uses sharding and replication to distribute data across multiple nodes and ensure high availability. On the other hand, Loggly is a cloud-based log management service that does not offer the same scalability and performance as Elasticsearch. It relies on its own infrastructure to process and index logs, which may not be as efficient as Elasticsearch's distributed architecture.

  2. 2. Full-Text Search and Analytics: Elasticsearch is primarily built for full-text search and analytics. It uses inverted indices to provide fast search capabilities across large volumes of structured and unstructured data. Loggly, on the other hand, focuses specifically on log management and analytics. It provides pre-built dashboards and visualizations tailored for log analysis, making it easier for users to monitor and troubleshoot their systems.

  3. 3. Data Retention and Storage: Elasticsearch allows users to define data retention policies and manage the storage of their data through index lifecycle management (ILM). This gives users control over how long data is retained and how it is stored (e.g., in hot, warm, or cold storage). Loggly, on the other hand, provides a fixed retention period based on the user's subscription plan. Users have limited control over how long their logs are retained and cannot customize storage options.

  4. 4. Log Collection Methods: Elasticsearch supports various log collection methods, including agents, plugins, and integrations with external systems. It can ingest logs from different sources and protocols, making it a versatile solution for log management. Loggly, on the other hand, provides a centralized log collection system that relies on log shipping agents. While it supports popular log shipping methods like Syslog and Logstash, it does not offer the same level of flexibility as Elasticsearch.

  5. 5. Querying and Filtering: Elasticsearch provides a powerful query DSL (Domain-Specific Language) that allows users to perform complex searches and aggregations on their data. It supports filtering based on various criteria, such as time range, keyword matching, and numeric ranges. Loggly, on the other hand, offers a simplified query language that is focused on log analysis. It provides predefined search filters and allows users to perform basic search queries but lacks the advanced querying capabilities of Elasticsearch.

  6. 6. Security and Access Control: Elasticsearch offers robust security features, including authentication, authorization, and encryption. It supports role-based access control (RBAC) and integrates with external authentication providers like Active Directory and LDAP. Loggly, on the other hand, provides basic security features like HTTPS encryption and IP whitelisting but does not offer the same level of fine-grained access control as Elasticsearch. It does not support RBAC or integration with external authentication providers.

In Summary, Elasticsearch and Loggly differ in terms of scalability and performance, full-text search and analytics capabilities, data retention and storage options, log collection methods, querying and filtering capabilities, and security and access control features.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Loggly, Elasticsearch

Rana Usman
Rana Usman

Chief Technology Officer at TechAvanza

Jun 4, 2020

Needs adviceonFirebaseFirebaseElasticsearchElasticsearchAlgoliaAlgolia

Hey everybody! (1) I am developing an android application. I have data of around 3 million record (less than a TB). I want to save that data in the cloud. Which company provides the best cloud database services that would suit my scenario? It should be secured, long term useable, and provide better services. I decided to use Firebase Realtime database. Should I stick with Firebase or are there any other companies that provide a better service?

(2) I have the functionality of searching data in my app. Same data (less than a TB). Which search solution should I use in this case? I found Elasticsearch and Algolia search. It should be secure and fast. If any other company provides better services than these, please feel free to suggest them.

Thank you!

408k views408k
Comments
André
André

Nov 20, 2020

Needs adviceonElasticsearchElasticsearchAmazon DynamoDBAmazon DynamoDB

Hi, community, I'm planning to build a web service that will perform a text search in a data set off less than 3k well-structured JSON objects containing config data. I'm expecting no more than 20 MB of data. The general traits I need for this search are:

  • Typo tolerant (fuzzy query), so it has to match the entries even though the query does not match 100% with a word on that JSON
  • Allow a strict match mode
  • Perform the search through all the JSON values (it can reach 6 nesting levels)
  • Ignore all Keys of the JSON; I'm interested only in the values.

The only thing I'm researching at the moment is Elasticsearch, and since the rest of the stack is on AWS the Amazon ElasticSearch is my favorite candidate so far. Although, the only knowledge I have on it was fetched from some articles and Q&A that I read here and there. Is ElasticSearch a good path for this project? I'm also considering Amazon DynamoDB (which I also don't know of), but it does not look to cover the requirements of fuzzy-search and ignore the JSON properties. Thank you in advance for your precious advice!

60.3k views60.3k
Comments

Detailed Comparison

Loggly
Loggly
Elasticsearch
Elasticsearch

It is a SaaS solution to manage your log data. There is nothing to install and updates are automatically applied to your Loggly subdomain.

Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack).

See what your application is doing during development;Catch exceptions and track execution flow;Graph and report on the number of errors generated;Search across multiple deployments;Narrow down on specific issues;Investigate root cause analysis;Monitor for specific events and errors;Trigger alerts based on occurrences and investigate for resolutions;Track site traffic and capacity;Measure application performance;A rich set of RESTful APIs which make data from applications easy to query;Supports oAuth authentication for third-party applications development (View our Chrome Extension with NewRelic);Developer ecosystem provides libraries for Ruby, JavaScript, Python, PHP, .NET and more
Distributed and Highly Available Search Engine;Multi Tenant with Multi Types;Various set of APIs including RESTful;Clients available in many languages including Java, Python, .NET, C#, Groovy, and more;Document oriented;Reliable, Asynchronous Write Behind for long term persistency;(Near) Real Time Search;Built on top of Apache Lucene;Per operation consistency;Inverted indices with finite state transducers for full-text querying;BKD trees for storing numeric and geo data;Column store for analytics;Compatible with Hadoop using the ES-Hadoop connector;Open Source under Apache 2 and Elastic License
Statistics
Stacks
269
Stacks
35.5K
Followers
304
Followers
27.1K
Votes
168
Votes
1.6K
Pros & Cons
Pros
  • 37
    Centralized log management
  • 25
    Easy to setup
  • 21
    Great filtering
  • 16
    Live logging
  • 15
    Json log support
Cons
  • 3
    Pricey after free plan
Pros
  • 329
    Powerful api
  • 315
    Great search engine
  • 231
    Open source
  • 214
    Restful
  • 200
    Near real-time search
Cons
  • 7
    Resource hungry
  • 6
    Diffecult to get started
  • 5
    Expensive
  • 4
    Hard to keep stable at large scale
Integrations
Heroku
Heroku
Amazon S3
Amazon S3
New Relic
New Relic
AWS CloudTrail
AWS CloudTrail
Engine Yard Cloud
Engine Yard Cloud
Cloudability
Cloudability
Kibana
Kibana
Beats
Beats
Logstash
Logstash

What are some alternatives to Loggly, Elasticsearch?

Algolia

Algolia

Our mission is to make you a search expert. Push data to our API to make it searchable in real time. Build your dream front end with one of our web or mobile UI libraries. Tune relevance and get analytics right from your dashboard.

Papertrail

Papertrail

Papertrail helps detect, resolve, and avoid infrastructure problems using log messages. Papertrail's practicality comes from our own experience as sysadmins, developers, and entrepreneurs.

Logmatic

Logmatic

Get a clear overview of what is happening across your distributed environments, and spot the needle in the haystack in no time. Build dynamic analyses and identify improvements for your software, your user experience and your business.

Logentries

Logentries

Logentries makes machine-generated log data easily accessible to IT operations, development, and business analysis teams of all sizes. With the broadest platform support and an open API, Logentries brings the value of log-level data to any system, to any team member, and to a community of more than 25,000 worldwide users.

Logstash

Logstash

Logstash is a tool for managing events and logs. You can use it to collect logs, parse them, and store them for later use (like, for searching). If you store them in Elasticsearch, you can view and analyze them with Kibana.

Graylog

Graylog

Centralize and aggregate all your log files for 100% visibility. Use our powerful query language to search through terabytes of log data to discover and analyze important information.

Sematext

Sematext

Sematext pulls together performance monitoring, logs, user experience and synthetic monitoring that tools organizations need to troubleshoot performance issues faster.

Fluentd

Fluentd

Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. Fluentd helps you unify your logging infrastructure.

Typesense

Typesense

It is an open source, typo tolerant search engine that delivers fast and relevant results out-of-the-box. has been built from scratch to offer a delightful, out-of-the-box search experience. From instant search to autosuggest, to faceted search, it has got you covered.

Amazon CloudSearch

Amazon CloudSearch

Amazon CloudSearch enables you to search large collections of data such as web pages, document files, forum posts, or product information. With a few clicks in the AWS Management Console, you can create a search domain, upload the data you want to make searchable to Amazon CloudSearch, and the search service automatically provisions the required technology resources and deploys a highly tuned search index.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

Postman
Swagger UI

Postman vs Swagger UI

gulp
Grunt

Grunt vs Webpack vs gulp