Elastic{ON} 2018 - Visualizing Content Performance with Elastic at Canadian Broadcasting Corporation (CBC)

Transcript

1. Canadian Broadcasting Corporation
   February 28th, 2018
   Visualizing Content
   Performance with Elastic
   Sean Bennett & Stefan Piruzevski
   

   View Slide

2. In brief
   We are going to talk about…
   - Some history
   - What brought us here
   - Our challenge
   

   View Slide

3. Who we are
   Stefan Piruzevski Sean Bennett
   

   View Slide

4. A little history
   

   View Slide

5. Our mandate
   ● Distinctly Canadian
   ● Contribute to cultural expression
   ● Shared national consciousness and identity
   ● Meet Canadians where they consume
   content
   ● Reflect the cultural of Canada
   

   View Slide

6. We’re local.
   

   View Slide

7. Like, really local
   ENGINEERING PHOTO FROM
   RESOLUTE BAY
   

   View Slide

8. Which is big!
   

   View Slide

9. Getting our house in order
   

   View Slide

10. What we deliver
    Vertical focused content (News, Comedy, Lifestyle, Sports)
    

    View Slide

11. How do we deliver it?
    

    View Slide

12. We’re a Broadcaster
    

    View Slide

13. The Ask - Where it all started (SP)
    Number of stories updated per day, per location, per particular time of day
    

    View Slide

14. Educated guess with rudimentary numbers
    

    View Slide

15. mvn exec:java
    -Dexec.mainClass="ca.cbc.INTERNAL.PATH.util.ReferringContent"
    -Dexec.args="http://:/connection-properties/conn
    ection.properties sysadmin sysadmin output.csv 'inputTemplate:Image
    AND (text:Flickr OR text:Flicker)'"
    Done.
    Documents found: 421 Success: 421 Failed: 0 Referring content ids: 533
    Sample Report!
    

    View Slide

16. CBC’s Infrastructure
    

    View Slide

17. Content Management System
    

    View Slide

18. Owned and Operated
    

    View Slide

19. Owned and Operated
    

    View Slide

20. Owned and Operated
    

    View Slide

21. Owned and Operated
    

    View Slide

22. System map
    

    View Slide

23. System map
    CDN (Cache)
    Internal (Cache)
    CMS (Cache)
    CMS (Disk)
    CMS (DB)
    

    View Slide

24. We looked at:
    

    View Slide

25. We looked at: building a custom solution
    

    View Slide

26. We looked at: logging tools used by our network teams
    

    View Slide

27. We looked at: other vendors and CMS platforms
    

    View Slide

28. We looked at: existing internal tools
    

    View Slide

29. We looked at: creating more JAVA classes
    

    View Slide

30. We looked at:
    The possibility of creating a mirrored
    environment with real-time replication of
    our data so we could query the db in a
    non-audience facing environment.
    

    View Slide

31. We looked at: EVERYTHING
    

    View Slide

32. You said “Banana”!
    

    View Slide

33. BANANAS!
    Query existing Solr indexes
    Graphical UI!!!
    No more manual Solr queries
    We loved it
    Performance vs Flexibility
    

    View Slide

34. View Slide

35. Dynamic provisioning
    Not complicated
    Easily incorporate into our CMS
    

    View Slide

36. View Slide

37. What are we using
    

    View Slide

38. What are we using
    To Logstash or not to Logstash
    Real-time data with Beats
    Easily add Filebeat into our CMS
    

    View Slide

39. What are we using
    Easy to learn
    Already used in by some teams
    Not directly connected to Production
    

    View Slide

40. What are we using
    Bad Data
    Wiping Everything
    Duplicate Data
    

    View Slide

41. What are we using
    

    View Slide

42. What are we using
    Apply Banana Lessons
    Real-time Dashboards
    Don’t judge us.
    

    View Slide

43. What are we using
    

    View Slide

44. Let’s Assemble!
    ?
    

    View Slide

45. The players
    !
    

    View Slide

46. View Slide

47. The Ask - Where it all started (SP)
    Number of stories updated per day, per location, per particular time of day
    

    View Slide

48. Number of stories updated per day, per location, per particular time of day
    

    View Slide

49. Now what?
    ?
    

    View Slide

50. Capture all the things!
    

    View Slide

51. Number of stories updated per day, per location, per particular time of day
    

    View Slide

52. Number of stories updated per day, per location, per particular time of day
    

    View Slide

53. Number of stories updated per day, per location, per particular time of day
    

    View Slide

54. Number of stories updated per day, per location, per particular time of day
    

    View Slide

55. View Slide

56. View Slide

57. View Slide

58. View Slide

59. View Slide

60. View Slide

61. View Slide

62. View Slide

63. View Slide

64. View Slide

65. Rinse, Repeat
    

    View Slide

66. Next level data-driven decision making
    ●Workflow/Process improvements
    ●Identifying opportunities
    ●Giving more accurate performance measurement
    

    View Slide

67. Let’s loop in the audience!
    

    View Slide

68. Thanks!
    Catch us at the AMA booth!
    Stefan Piruzevski Sean Bennett
    

    View Slide