Metrics Practice

Alright, we walked you through the process for the first set of data. Now it's your turn to play with the functions. A fictional set of AWS accounts provides us with another set of data, VPC Flow Logs.

Components

We already have these components partially pre-configured, and your challenge is to build out the Pipeline (and change the Routing Destination accordingly).

Component Type	Component Name	Description	Initial State
Stream Route	flowlog-metrics	Route that directs flow log traffic through the pipeline.	Routes to the DevNull output (hint, you'll need to change this to see any output)
Stream Pipeline	flowlog_metrics	The pipeline to extract and transform flow log data	Has the field extraction functions already, but you'll need to add the rest.
Stream Sample File	vpc-flowlog-sample.log	A sample file of events to use when building out the pipeline	Complete
InfluxDB Dashboard	FlowLog Metrics	A dashboard already created in the InfluxDB instance to view the eventual output	Configured in the InfluxDB instance, but with no data (this populating will be how you know you got it right)

Mission

Build out the pipeline to generate the following metrics:

• bytes transferred by AWS Region (field:aws_region)
• bytes transferred by AWS Account ID (field: aws_account)
• bytes transferred by Destination Port (field: dstport)

You'll want to publish the bytes_sum as the metrics field flowlogs.bytes

If done correctly, the Flowlog Metrics dashboard should refresh with actual data instead of displaying No Results in all three cells, like this:

So go ahead and try it out. On the next page, there are screenshots of the completed Pipeline, Functions, Routes, etc. to review your work. Also, feel free to play with other dimensions, aggregate functions, etc.