Send logs from AWS Kinesis Firehose to Azure Monitor logs

A simple guide to send logs from AWS Kinesis Firehose to Azure Monitor logs in just a few minutes.
type: tutorialdomain: sourcesdomain: sinkssource: aws_kinesis_firehosesink: azure_monitor_logs

Logs are an essential part of observing any service; without them you'll have significant blind spots. But collecting and analyzing them can be a real challenge -- especially at scale. Not only do you need to solve the basic task of collecting your logs, but you must do it in a reliable, performant, and robust manner. Nothing is more frustrating than having your logs pipeline fall on it's face during an outage, or even worse, cause the outage!

Fear not! In this guide we'll build an observability pipeline that will send logs from AWS Kinesis Firehose to Azure Monitor logs.

Background

What is AWS Kinesis Firehose?

Amazon Kinesis Data Firehose is a fully managed service for delivering real-time streaming data to destinations such as Amazon Simple Storage Service (Amazon S3), Amazon Redshift, Amazon Elasticsearch Service (Amazon ES), and Splunk.

What is Azure Monitor logs?

Azure Monitor is a service in Azure that provides performance and availability monitoring for applications and services in Azure, other cloud environments, or on-premises. Azure Monitor collects data from multiple sources into a common data platform where it can be analyzed for trends and anomalies.

Strategy

How This Guide Works

We'll be using Vector to accomplish this task. Vector is a popular open-source observability data platform. It's written in Rust, making it lightweight, ultra-fast and highly reliable. And we'll be deploying Vector as a agent.

Vector daemon deployment strategyVector daemon deployment strategy
1. Your service logs to STDOUT
STDOUT follows the 12 factor principles.
2. STDOUT is captured
STDOUT is captured and sent to a AWS Kinesis Firehose stream.
3. Vector collects & fans-out data
Vector will sends logs to [Azure Monitor logs](https://azure.microsoft.com/en-us/services/monitor/).

What We'll Accomplish

We'll build an observability data platform that:

  • Receives logs from AWS Kinesis Firehose.
    • Enriches data with useful AWS Kinesis Firehose context.
    • Securely receives data via Transport Layer Security (TLS).
  • Sends logs to Azure Monitor logs.
    • Buffers data in-memory or on-disk for performance and durability.
    • Compresses data to optimize bandwidth.
    • Automatically retries failed requests, with backoff.
    • Securely transmits data via Transport Layer Security (TLS).
    • Batches data to maximize throughput.

All in just a few minutes!

Tutorial

  1. Install Vector

    curl --proto '=https' --tlsv1.2 -sSf https://sh.vector.dev | sh
  2. Configure Vector

    cat <<-'VECTORCFG' > ./vector.toml
    [sources.aws_kinesis_firehose]
    type = "aws_kinesis_firehose"
    address = "0.0.0.0:443"
    region = "us-east-1"
    [sinks.out]
    type = "azure_monitor_logs"
    inputs = [ "aws_kinesis_firehose" ]
    customer_id = "5ce893d9-2c32-4b6c-91a9-b0887c2de2d6"
    log_type = "MyTableName"
    shared_key = "${AZURE_MONITOR_SHARED_KEY_ENV_VAR}"
    VECTORCFG
  3. Start Vector

    vector --config ./vector.toml
  4. Observe Vector

    vector top
    explain this command

Next Steps

Vector is powerful tool and we're just scratching the surface in this guide. Here are a few pages we recommend that demonstrate the power and flexibility of Vector:

Vector Github repo 4k
Vector is free and open-source!
Vector getting started series
Get setup in just a few minutes
Vector documentation
Everything you need to know about Vector