1. Emilio
Nyaray
Twitter: Bip
@KivraLabs Thelin
@nyaray
@bipthelin

2. (Brief) History

3. mission
THE vision

4. RIAK
Practices

5. Logging

6. 1. Metrics
Anything you'd want to
plot on a graph

7. 2. (Un)structured
Log data logging
you'd want
to process

8. 3. Application
logging Error,
Notice,
Warning,
etc

9. Requirements
○ Search
○ Archive
○ Aggregate logs
○ Slice logs by arbitrary
dimensions
○ Alerting

11. Lager Loggly
github.com/kivra/lager_loggly.git

12. Lager Syslog
github.com/basho/lager_syslog

13. ~197 SLOC
~23 SLOC

14. 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}
]}
]},
...
]},

16. Lazy
Upgrade

17. Riak <3
It's fun to use
upgrade
manage
discuss
also, hard to resist

18. Riak <3, really!
Bu-bu-but... MySQL
PostgreSQL
MSSQL
OldSQL ... same as before
NoScale
NoOps
NoSQL

19. Schema
that!
Scr ew

20. Schema-less...
but,
STRUCTURED
Typo, it's JSON

21. Schema-less...
Or is it?
Intermediate -record(user, {
Records password = <<"l0ln00b">,
Before name = <<"noname">>,
Store i_primary_email = <<"ih@ck.se">,
i_primary_phone = <<"461337">>,
i_ssn = <<"0123456789">>,
l_tenant = {<<"B">>, <<"K">>}
}).
Concerns?
Add/Rename Field
+ Search

22. Embrace Change
Be flexible,
stay focused,
know your data
What does that even mean?!

23. Upgrade Path(tm)
schema_upgrade(?CURR_VSN, Props) ->
Props;
schema_upgrade(1, Props) ->
% Awesome upgrade,
% also defines NewProps
schema_upgrade(Vsn+1, NewProps).

24. Simplified
access
Everything is fun
Save po-TAY-to...
Read po-TAH-to!

25. Thank You!
You've been great.
Go away now,
drink some beer!