1.
Streamline and Scale Out Data
Pipelines with Kubernetes,
Telegraf, and InfluxDB

2.
What is RudderStack?

3.
RudderStack architecture diagram
TRANSFORMATIONS
IDENTITY RESOLUTION
DATA GOVERNANCE

4.
Rudderstack
Key Differences
4
WAREHOUSE FIRST
DEVELOPER FOCUSED
NO PERSISTENT DATA /
FUTURE-PROOF YOUR DATA STACK
4

5.
Rudderstack
Key Differences
5
WAREHOUSE FIRST
DEVELOPER FOCUSED
NO PERSISTENT DATA /
FUTURE-PROOF YOUR DATA STACK
5

6.
How do we use InfluxDB?

7.
To change or remove footer go to View Tab > Master
Kubernetes Deployment
7

8.
To change or remove footer go to View Tab > Master
Kubernetes Deployment
8

9.
To change or remove footer go to View Tab > Master
What do we need?
● Fast
● Reliable
● Gets out of the way
Not our actual
business (but very
important to it)
9

10.
To change or remove footer go to View Tab > Master
Why InfluxDB?
We constantly evaluate the best tools for our customers
In some deployments we run prometheus in parallel for comparison
We knew we needed a fast, efficient time series database
We have been using InfluxDB since we started storing metrics
10

11.
To change or remove footer go to View Tab > Master
How do we use it?
11

12.
To change or remove footer go to View Tab > Master
How do we use it?
12

13.
To change or remove footer go to View Tab > Master
How do we use it?
13

14.
To change or remove footer go to View Tab > Master
Metrics metrics everywhere
14

15.
To change or remove footer go to View Tab > Master
Metrics metrics everywhere
● 100s of metrics
● High level
● Low level
● Counters, Timing, Guages
● Adding new metrics is fast
and easy
● Primary monitoring/alerting
15

16.
To change or remove footer go to View Tab > Master
What’s next?
● Determining long term storage of metrics
○ Sample?
○ Compress?
● Migration of metrics as deployment model changes
● Any change must be supported forever (open source)
● InfluxDB is limited to 200 tags
● Always evaluating more efficient options
16

17.
Questions