Logstash can parse CSV and JSON files easily, but that’s because data in those formats are perfectly organized and ready for Elasticsearch analysis. Sometimes, though, we need to work with unstructured data, like plain-text logs for example. In these cases, we’ll need to parse the data to make it structured data using Logstash Grok. This tutorial will enable you to take full advantage of Elasticsearch’s analysis and querying capabilities by parsing with Logstash Grok.

Serverless computing has taken off in recent years with more efficient cloud services. AWS Lambda is a great example of this, where provisioning and management of resources happens from the service’s end. You only have to deal with the code. This article will give a brief overview of AWS Lambda in contrast to EC2 instances, then walk through shipping AWS Lambda metrics to Logz.io.

TL;DR note: if you want the bzip2 -9 version of this post, scroll down to the very last section for some quick pointers. If you want to learn a bit about Linux system logs, please continue, as we’ll talk about all these and more.

This post will show you how Coralogix can provide analytics and insights for your Okta logs, both performance, and security. Okta is one of the leading Identity provider platforms in the world, offering a variety of cloud services including a Single Sign-On solution to manage and secure company user authentication with 3rd party applications.

Amazon EC2 offers a flexible and convenient way to run virtual machines in the cloud. With dozens of EC2 instance types available, as well as multiple pricing options, it’s easy to use EC2 to configure the best cloud-based virtual machines for your needs and budget. One thing that EC2 doesn’t make very easy on its own, however, is monitoring.

This week we are excited to officially announce the launch of our new Splunk Community with a re-imagined experience! The Splunk Community first launched nearly eleven years ago and today over 12,000 monthly active members visit our site to engage, learn, answer questions and give back!

To understand what’s going on in their environment, DevOps teams usually ship some combination of logs, metrics and traces—depending on which signals they’re hoping to monitor. Each data type will expose different information about what is happening in a system. However, not all of that information will be helpful on a day-to-day basis, which can rack up unnecessary data storage costs. That should require users start to filter telemetry data across their observability stacks.