Technical skills & knowledge to help you feel more confident in your tech career.

Stay tuned

Don’t miss out on the latest issues. Sign up now to get access to the library of members-only issues.

jamie@example.com
The Skiplevel Newsletter

The Data Lifecycle Lowdown: Data Processing

Hey y'all, it's Irene here with your monthly dose of tech know-howπŸ‘©β€πŸ’»

Here's a question: how familiar are you with the data lifecycle?

If the answer is not familiar at all, or a little, you don't want to miss this issue. I'm going to give you an intro to the data lifecycle along with its stages and I'll dig a bit deeper into stage 3: data processing.

You'll also learn about LogStash–the L of the ELK stack we've been covering in previous newsletters (see the Elasticsearch article here).

.. and I'll also share a pro-tip on how to make a great first impression and kick off your relationship with your dev team the right way πŸ˜‰

Visit Skiplevel to learn more or connect with me on LinkedIn and Twitter and follow Skiplevel on LinkedIn!


Here's a pro-tip for making a great first impression with your dev team πŸ‘‡


Data Processing & the Data Lifecycle

This is part of a series of 3 newsletters dedicated to learning the ELK stack (Elasticsearch, LogStash, and Kibana). Read the first newsletter on Search in programming and ElasticSearch here.

Intro to the Data Lifecycle

We collect data for many reasons, but one of the most important reasons is to extract important business insights from it–a key part of data analytics and data science.

This process of extracting important insights from raw datasets is called the data lifecycle, and the structure set up to monitor this process is known as the data management lifecycle.

The lifecycle of data takes us from planning what data to collect all the way to storing data. Depending on your company and which data expert you ask, there can be anywhere from 5-8 lifecycle stages, but here are 6 broad stages:

πŸ‘‰ Stage 1 Planning: Decide what data to collect ↓
πŸ‘‰ Stage 2 Acquire: Collect the raw data ↓
πŸ‘‰ Stage 3 Process: Clean and manipulate the data to get ready for analysis ↓
πŸ‘‰ Stage 4 Storing: Organize and copy data into DB(s) for access and retrieval ↓
πŸ‘‰ Stage 5 Analyze: Extract useful insights from processed data ↓
πŸ‘‰ Stage 6 Visualizing: Create graphical representations of information

There's lots to learn about each stage in the data lifecycle but in this issue we're just going to dig a bit more into stage 3: data processing.

What is data processing and why is it important?

Data processing is critical for any organization looking to create better business strategies and increase their competitive edge.

When we first collect data, it's known as raw data, or data that's directly collected from the source and has not been cleaned, processed, or transformed. In order for us to extract utility from a raw dataset, all data in the dataset has to:

  • πŸ‘‰ Be uniform: Data follows a predictable pattern/structure (i.e. Β  Β  MM/DD/YYYY for dates)
  • πŸ‘‰ Have Integrity: Inaccurate or fake data is removed to preserve data integrity (i.e. fake addresses or fake names)
  • πŸ‘‰ Be Searchable: How do we organize and quickly search through large data sets? (i.e. Organize datasets based on last name, location, etc..)

This is where data processing comes in. In data processing, raw data is collected, filtered, and sorted in order to achieve the above characteristics before moving on to the next stage for analysis.

Data processing engines to the rescue: Introducing LogStash

Data processing can be quite complex depending on the size of the dataset and the type/format of the raw data.

Let's take log data as an example. In the last post on logging I included some examples of what log data looks like. Here's a refresher on access logs:

[Exhibit 1] Access log example

Notice how unstructured the raw access log data is. In order to extract any value from it, we need to process it in order to extract out the info we want into their own separate fields (i.e. visitor IP address, visitor device, etc..) while also cleaning and formatting the data.

To do this, teams and companies use a pipeline tool called data processing engines or data collection engines to pipe in raw data, run some rules/ algorithms on it, and spit out the final processed data before storing it somewhere.

Introducing LogStash

LogStash is a powerful open source data collection engine with real-time pipelining capabilities. Logstash has capabilities that extend well beyond just processing log data. However, it is known for originally driving innovation in log collection, hence the name LogStash. Regardless, LogStash is a popular data processing engine used by data and software teams everywhere to process all types of data.

How does LogStash work?

All data processing engines uses a pipeline structure with multiple stages to process data.

The LogStash events processing pipeline has 3 stages: input β†’ filter β†’ output. Inputs generate events, filters modify them, and outputs ship them elsewhere. LogStash defines these stages in a configuration file called logstash.conf.

Below is a very simple code example of a Logstash configuration file. This file is defined by an engineering team and uploaded your LogStash account.

[Exhibit 2] Example of a logstash configuration file

Notice how the file is sectioned out into the 3 stages of input, filter, and output. Logstash supports various operations within each stage that you can read more about here if you're curious.

Take a step back for the big picture

If you've been paying attention to each Skiplevel newsletter issue, you'll notice just how much we've covered.. and we've covered a lot. In the last post we covered software logs. This issue we talked about data processing, data processing engines, and LogStash in particular as part of the popular ELK stack. Skiplevel's December issue also covered Elasticsearch as part of the ELK stack.

Remember as a non-engineering tech person working with engineers, the depth of detail is not as important as a breadth of knowledge.

So if there's one visualization in your mind you should be walking away with from all 3 issues, it's this flow diagram below:

[Exhibit 3] Log data –> Parsed and collected –> Search Indexing

In the next issue, we'll round out the ELK stack with Kibana for the last stage of the data pipeline: visualizing.


As always, visit Skiplevel to learn more or connect with me on LinkedIn and Twitter and follow Skiplevel on LinkedIn!

Latest issue