Bip Thelin

Emilio Nyaray

Twitter:@KivraLabs@nyaray@bipthelin

(Brief) History

visionmissionTHE

RIAKPractices

Logging

1. MetricsAnything you'd want to plot on a graph

2. (Un)structured loggingLog data

you'd want to process

3. Applicationlogging Error,

Notice,Warning, etc

Requirements○ Search○ Archive○ Aggregate logs○ Slice logs by arbitrary

dimensions○ Alerting

Lager Logglygithub.com/kivra/lager_loggly.git

Lager Sysloggithub.com/basho/lager_syslog

~197 SLOC~23 SLOC

Lager{lager, [

{handlers, [ {lager_console_backend, info}, {lager_loggly_backend, [<<"Riak">>,

info, 5, 3, "https://<Loggly URI>"]},

{lager_loggly_backend, [<<"Riak">>, error, 5, 3, "https://<Loggly URI>"]},

{lager_file_backend, [ {"/path/error.log", error, 10485760, "$D0", 5}, {"/path/console.log", info, 10485760, "$D0", 5} ]}

]}, ...]},

Lazy Upgrade

It's fun to useupgrademanagediscuss

also, hard to resist

Riak <3

Riak <3, really!Bu-bu-but... MySQL

PostgreSQLMSSQLOldSQL

No... same as before

SQLNoNo

ScaleOps

Screw that!

Schema

but,

STRUCTUREDTypo, it's JSON

Schema-less...

-record(user, {

password = <<"l0ln00b">,

name = <<"noname">>,

i_primary_email = <<"ih@ck.se">,

i_primary_phone = <<"461337">>,

i_ssn = <<"0123456789">>,

l_tenant = {<<"B">>, <<"K">>}

}).

Schema-less...Or is it?

IntermediateRecords

Concerns?Add/Rename Field

BeforeStore

+ Search

Be flexible,stay focused,

know your data

What does that even mean?!

Embrace Change

schema_upgrade(?CURR_VSN, Props) ->

Props;

schema_upgrade(1, Props) ->

% Awesome upgrade,

% also defines NewProps

schema_upgrade(Vsn+1, NewProps).

Upgrade Path(tm)

Save po-TAY-to...Read po-TAH-to!

SimplifiedEverything is fun

access

Thank You!You've been great.

Go away now, drink some beer!