Merge pull request #2769 from nateynateynate/opensearchcon/2024/europ…

…e/sessions/how-opensearch-helped-us-build-choreos-live-logs-feature

Nilushan Costa's session

_community_members/ncosta.md

@@ -0,0 +1,78 @@
+---
+#
+# Sample data for community members.
+#
+
+# The short name is used to identify related pieces of content in the site. For example it is used in the "authors" array of blog posts, and it is used in the "presenters" array for OpenSearch Conference sessions to identify who is speaking.
+# The format for existing values is not normalized. In some cases it is "first-initial-of-first-name" + "last-name", or matching a GitHub username, or something all together random. What is important is that it is unique within the system.
+short_name: "ncosta"
+
+# The member's full name, or otherwise meaningful preferred name. It is used in the templates for presenting content authors as well as the name of conference speakers.
+name: "Nilushan Costa"
+
+# The path to the community member's photo.
+photo: "/assets/media/community/members/ncosta.jpeg"
+
+# Used as the level 1 page header text.
+primary_title: 'Nilushan Costa'
+
+# Used as the document title displayed in the browser title bar.
+title: 'OpenSearch Project Community Member: Nilushan Costa'
+
+# Breadcrumbs specification.
+# The community icon is expected.
+# The breadcrumbs path structure is Communit -> Members -> Nilushan Costa's Profile.
+breadcrumbs:
+  icon: community
+  items:
+    - title: Community
+      url: /community/index.html
+    - title: Members
+      url: /community/members/index.html
+    - title: "Nilushan Costa's Profile"
+      url: '/community/members/first-last.html'
+
+# Community member job title and company where they work.
+job_title_and_company: 'Choreo'
+
+# Array of conference IDs for which the community member is a keynote speaker, if any, or boolean false otherwise.
+# This value is only relevant for member's with the "conference_speaker" user persona.
+#keynote_speaker:
+#  - '2023-north-america'
+# keynote_speaker: false
+
+# The conference topic track for the conference sessions that the user is a speaker. These are shaped as an array of value pairs mapping conference ID and name. 
+# For example for the North American conference for the year 2023, and the "Community" track:
+session_track: 
+  - conference_id: "2024-europe"
+    name: "Analytics, Observability, and Security"
+
+# URL for the community member profile.
+permalink: '/community/members/nilushan-costa.html'
+
+# Array of community member user personas.
+# At this time, only conference_speaker, and author are defined.
+personas:
+  - conference_speaker
+
+# Array of conference IDs that the member is a speaker.
+conference_id:
+  - "2024-europe"
+
+
+# Optional GitHub username
+#github: githubusername
+
+# Optional LinkedIn username
+#linkedin: linkedinusername
+
+# Optional Twitter username
+#twitter: twitterusername
+
+# Optional Mastodon server url, and username / handle.
+#mastodon:
+#  url: https://mastodon.social/@mastodonusername
+#  name: mastodonusername
+---
+
+Nilushan is a part of the Choreo team at WSO2 and works on Observability features. When not working, he can be found flying planes or going on adrenaline-fuelled adventures

_opensearchcon_sessions/2024-europe-how-opensearch-helped-us-build-choreos-live-logs-feature.md

@@ -0,0 +1,65 @@
+---
+#
+# The expected filename format is ${conference_id}-${url-encoded-session-title}.md
+# For example the "Community Inclusion" session from the 2023 conference in North America the title is "2023-north-america-community-inclusion.html"
+#
+
+# Conference session speaker short name that maps to a short_name value
+# in the community members collection.
+primary_presenter: 'ncosta'
+
+# Conference session speaker full name.
+speaker_name_full: 'Nilushan Costa'
+
+# Conference session title.
+speaker_talk_title: 'How OpenSearch helped us to build Choreo’s live logs feature'
+
+# Page level 1 header title.
+primary_title: 'How OpenSearch helped us to build Choreo’s live logs feature'
+
+# Page document title displayed in the browser title bar.
+title: 'OpenSearchCon 2024 Session: How OpenSearch helped us to build Choreo’s live logs feature'
+
+breadcrumbs:
+  icon: community
+  items:
+    - title: OpenSearchCon
+      url: /events/opensearchcon/index.html
+    - title: 2024
+      url: /events/opensearchcon/2024/index.html
+    - title: North America
+      url: /events/opensearchcon/2024/europe/index.html
+    - title: Session Summaries
+      url: /events/opensearchcon/2024/europe/sessions/index.html
+# Session date / time
+# The template logic expects the following format: YYYY-MM-DD - h:m(am|pm)-(h:m(am|pm))
+session_time: "time TBD"
+
+session_room: "a room yet to be determined."
+
+
+# Session topic track.
+session_track: "Analytics, Observability, and Security"
+
+# URL permalink for the session.
+permalink: '/events/opensearchcon/sessions/how-opensearch-helped-us-build-choreos-live-logs-feature.html'
+
+# ID of the YouTube video of the session to embed in the page.
+# This is to be added after the conference and after the session recordings
+# are uploaded to YouTube.
+#youtube_video_id: 'SOME_YOUTUBE_VIDEO_ID'
+
+# Conference ID.
+# It is normative to use the format of 'YYYY-location-name', eg. '2023-north-america'.
+conference_id: '2024-europe'
+
+# Array of short_name values for the Community Members with the conference_speaker persona whom are presenting the session. This includes the primary_speaker indicated above and any other presenters (if any).
+presenters:
+  - ncosta
+
+---
+Logs generated by containerized applications are used to observe what is going on within an application. This can be used effectively, especially when debugging, if the logs are made available without any significant delays.
+
+When Choreo was built, it used the cloud provider’s native logging service. However this had a high log ingestion latency averaging between 20 seconds and 3 minutes. It was necessary to reduce this latency to improve the user experience. Furthermore, in order to ensure compliance, logs needed to remain within the cluster where they were generated. To address these requirements and provide a “tail -f” like experience for users in Choreo, this live logs feature was built by utilizing OpenSearch.
+
+In this talk, I will explain how OpenSearch was utilized to implement this feature and our experience running it in multiple Kubernetes clusters.