unifying events logs into the cloud
play

Unifying Events & Logs into the Cloud Eduardo Silva August 17, - PowerPoint PPT Presentation

Unifying Events & Logs into the Cloud Eduardo Silva August 17, 2015 eduardo@treasuredata.com CloudOpen/LinuxCon, Seattle @ edsiper About Me Eduardo Silva Github & Twitter @edsiper Personal Blog


  1. Unifying Events & Logs into the Cloud Eduardo Silva August 17, 2015 eduardo@treasuredata.com CloudOpen/LinuxCon, Seattle @ edsiper

  2. About Me Eduardo Silva ● Github & Twitter @edsiper ● Personal Blog http://edsiper.linuxchile.cl Treasure Data ● Open Source Engineer ● Fluentd / Fluent Bit http://github.com/fmuent Projects ● Monkey HTTP Server http://monkey-project.com ● Duda I/O http://duda.io

  3. Logging

  4. Logging Matters Pros ● Application status ● Debugging ● General information about anomalies: errors ● Troubleshooting / Support ● Local or Remote (network)

  5. Logging Matters From a business point of view ● Input data Analytics → ● User interaction / behaviors ● Improvements

  6. Assumptions

  7. Logging Matters Assumptions ● I have enough disk space ● I/O operations will not block ● Log messages are human readable ● My logging mechanism scale

  8. Logging Matters Assumptions Basically, yeah.. it should work.

  9. Concerns

  10. Logging Matters Concerns ● Logs increase = data increase ● Message format get more complex ● Did the Kernel fmush the bufgers ? (sync(2)) ● Multi-thread application ?, locking ? ● M ultiple Applications = M ultiple Logs

  11. Logging Matters Concerns If M ultiple Applications = M ultiple logs M ultiple Hosts x M ultiple Applications = ???

  12. OK, so: 1. Logging matters 2. It's really benefjcial 3. but...

  13. It needs to be done right.

  14. Logging Common sources & inputs ● Application Logs ● Apache ● NginX ● Syslog (-ng) ● Custom applications / Languages ● C, Ruby, Python, PHP, Perl, NodeJS, Java, etc.

  15. In a galaxy not so far away...

  16. How to parse/store multiple data sources ? note: performance matters!

  17. Fluentd is an open source data collector It let's you unify the data collection for a better use and understanding of data.

  18. before

  19. after

  20. Fluentd Highlights ● High Performance ● Built-in Reliability ● Structured Logs ● Plug gable Architecture ● More than 300 plugins! (input/fjltering/output)

  21. Fluentd Architecture

  22. Fluentd Internals simplifjed

  23. Fluentd Input plugins

  24. Fluentd Output plugins

  25. Fluentd Buffer plugins

  26. Fluentd Buffer plugins

  27. M x N → M + N

  28. Fluentd Simple Forwarding

  29. Fluentd Simple Forwarding: confjguration # logs from a fjle # store logs to MongoDB <source> <match backend.*> type tail type mongo path /var/log/httpd.log database fmuent format apache2 collection test tag backend.apache </match> </source> # logs from client libraries <source> type forward port 24224 </source>

  30. Fluentd Less Simple Forwarding

  31. Fluentd Lambda Architecture

  32. Fluentd # logs from a fjle # store logs to MongoDB <source> <match *.*> type tail type copy path /var/log/httpd.log <store> format apache2 type elasticsearch tag backend.apache logstash_format true </source> </store> # logs from client libraries <store> <source> type webhdfs type forward host 192.x.y.z port 24224 port 50070 </source> path /path/to/hdfs </store> </match>

  33. Who uses Fluentd in production ?

  34. We collect 800k events per second !

  35. Internet of Things

  36. Internet of Things Facts ● IoT will grow to many billions of devices over the next decade. ● Now it's about device to device connectivity. ● Difgerent frameworks and protocols are emerging. ● It needs Logging .

  37. Internet of Things Alliances Vendors formed alliances to join forces and develop generic software layers for their products:

  38. Internet of Things Solutions provided Alliance Framework → →

  39. IoT & Big Data Analytics IoT requires a generic solution to collect events and data from difgerent sources for further analysis. Data can come from a specifjc framework, radio device, sensor or other. How do we collect and unify data properly ?

  40. @fluentbit

  41. Fluent Bit is an open source data collector It let's you collect data from IoT/Embedded devices and transport It to third party services.

  42. Fluent Bit Targets ● Services ● Sensors / Signals / Radios ● Operating System information ● Automotive / Telematics

  43. Fluent Bit Requirements IoT and Embedded environment requires special handling, specifjcally on performance and resource utilization: ● Lightweight ● Written in C Language ● Customizable, pluggable architecture ● Full integration with Fluentd

  44. Fluent Bit Integration

  45. Fluent Bit Direct Output

  46. Containers

  47. Docker Logging driver ● Docker v1.6 released the concept of logging drivers ● Route container output ● Fluentd ?

  48. Docker

  49. Docker v1.8 Fluentd Logging driver!

  50. We Love Data! ● http://fmuentd.org ● http://fmuentbit.io ● https://docs.docker.com/reference/logging/fmuentd/ ● http://github.com/fmuent/fmuentd Thank you!

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend