Last month, we announced Logz.io Security Analytics — a security app built on top of the ELK Stack, offering out-of-the-box security features such as threat intelligence, correlation, and premade integrations and dashboards. In this article, I’d like to show an example of using both the ELK Stack and Logz.io Security Analytics to secure an AWS environment.

We recently had a presentation at Activate 2018 about entity extraction in the context of a product search. For example: how to tell, when the user typed in Activate 2018, that the intent was to run conference:Activate AND date:201

Servers take a lot of requests daily, we know that…We also know that the server responds instantly. But who makes the request? What do they want, and what exactly are they looking for? Where do these visitors come from? How often they are making a request: once a month, once a day, almost every minute? Well, answers to these, and potentially a lot more questions, can be found in a single place - the server log file.

We’re excited to announce that LogDNA’s built-in log parser offers custom parsing, now available in beta. This means you can now use our step-by-step wizard to wrangle non-standard log formats and run custom transformations on your logs, allowing you to easily search and graph log lines that were previously off limits. The best part is, it’s a simple three step process: search, extract, validate… done!

One of the most important aspects of developing an efficient system is to have clean, helpful logs that will help you understand what errors are being triggered, and what information is being processed. When you are first creating an application, you might not know what logging framework will be most suitable for your future needs, or you could simply want your system to remain agnostic regarding the logging implementation to be used.

One of the greatest threats to a log management solution is load. As log volume increases, the ability for a solution to process each event decreases. Given enough load, this will result in dropped messages and data loss.

We are very excited to announce a new capability for our Amazon S3 sources. Until recently, the only method Sumo Logic used for discovering new data in an S3 bucket was periodic polling. However, with our new notification-based approach, users can now configure S3 sources such that Sumo Logic is notified immediately (via AWS SNS) whenever a new item is added to an S3 bucket, eliminating the need to wait for new objects to be discovered via periodic polling.

We’re excited to announce the general availability of our new On-Prem, Self-Hosted, and Multi-Cloud logging platforms. Our customers will have the capability to log data in their infrastructure of choice. Whether across multiple public/private clouds or within a customer’s own data center, logs can be viewed through a unified interface while addressing any data locality and performance requirements.

Recently, we held a webinar where Chris Nguyen, our CEO and Co-Founder and Norman Hsieh, our Head of Business Development talked about the ever increasing production of data, the shift from monitoring to observability, and the evolution of production infrastructure into multi-cloud. LogDNA is uniquely positioned to have enabled thousands of customers to gain deep insights into their evolving DevOps infrastructure.

As any business running microservices, containerized applications, networking devices, or multiple servers knows, it’s important to get a centralized log management system that fits your company’s unique needs. The best log management solution should empower your business to gain insights, resolve production issues quickly, streamline your DevOps and IT teams, and allow you to work more efficiently.